All of the agents deployed to an FglAM are listed as Broken and Not Collecting Data (4265578)

All of agents deployed to a FglAM are listed as Broken and Not Collecting Data

The FglAM log shows that agents were restored after the FglAM was started, but that agents were deleted shortly after the FglAM connected to the FMS.

2017-11-29 10:53:41.112 VERBOSE [Startup Thread] com.quest.glue.core.agent.PersistAgentStatesTask - Agent Restore completed in 500 milliseconds.
...
2017-11-29 10:53:41.650 INFO    [Startup Thread] com.quest.glue.common.comms.transport.http.Connection - Connected to remote server at https://192.168.0.1:8443.
...
2017-11-29 10:54:35.932 VERBOSE [FglAM:IncomingMessage[5]-7] com.quest.glue.core.comms.handlers.DeleteAgentListener - Deleting agent instance HostAgents/WindowsAgent/monitor@hostname1 [5.8.5.6-5.8.5.6-201610140306-RELEASE-30] [id: a2bb98a7-d971-39e9-a00f-0d05e29d4b8d].
2017-11-29 10:54:35.932 VERBOSE [FglAM:IncomingMessage[5]-8] com.quest.glue.core.comms.handlers.DeleteAgentListener - Deleting agent instance HostAgents/WindowsAgent/monitor@hostname2 [5.8.5.6-5.8.5.6-201610140306-RELEASE-30] [id: 82cb6e54-6cba-3961-9b13-00f83eea6887].
...

The FMS log reports that the agents were deleted because they were deleted from the FglAM host when the FglAM was not connected:

2017-11-29 10:54:27.164 VERBOSE [FglAM:IncomingMessageResponse[4]-43] com.quest.glue.adapter.service.RemoteHosts - [Agent Sync] Deleting agent HostAgents/WindowsAgent/monitor@hostname1 on hostfglam_host [id: 1836af88-a917-4cb8-b6a8-ed322146a300]. It was previously deleted on the server when the host was not connected.
2017-11-29 10:54:27.164 VERBOSE [FglAM:IncomingMessageResponse[4]-43] com.quest.glue.adapter.service.RemoteHosts - [Agent Sync] Deleting agent HostAgents/WindowsAgent/monitor@hostname2 on host fglam_host [id: 1836af88-a917-4cb8-b6a8-ed322146a300]. It was previously deleted on the server when the host was not connected.

Set the config ID in the fglam.config.xml file back to the original value and restart the FglAM.

The fglam.config.xml file is located in the %FGLAM_HOME%\state\default\config directory.

Following is an example of the "config:id" line from the fglam.config.xml file:

    <config:id>1836af88-a917-4cb8-b6a8-ed322146a300</config:id>

If a backup of the fglam.config.xml file is not available the original FglAM config ID can be determined from the information for one of the agents in Diagnostic Snapshot in a FMS support bundle.

Following is an excerpt from the DiagnosticSnapshot file showing the ID of the FglAM associated with the monitor@hostname1 agent in the "agent home:" field:

    -- agent info --
...
      ~~~~ ~~~~
        agentId: 21
        agentON: com.quest.nitro.agent:namespace=HostAgents,agentName=a2bb98a7-d971-39e9-a00f-0d05e29d4b8d,agentId=21
        adapter: FglAM
        type: WindowsAgent
        namespace: HostAgents
        agent name: a2bb98a7-d971-39e9-a00f-0d05e29d4b8d
        munged: false
        host: fglam_name
        display name: monitor@hostname1
        agent obj: null
        obsolete: false
        hidden: false
        activated: true
        activatable: true
        deletable: false
        supports getLogs: false
        agent home: fglam_name#1cc18489-7ecc-473c-8379-44bc4e9836b5
        version: 5.8.5.6
        build: 5.8.5.6-201610140306-RELEASE-30
        lifecycle not present