In this situation the user was seeing multiple assets and IP's associated to one single agent in the CCS console. The user was also seeing instances where the agent registration was failing to generate the registration XML on the CCS manager.
In this case the user was deploying Linux hosts through a deployment template which already had the CCS agent installed. This caused a condition where the agentID.dat on each new agent contained the exact same Agent GUID. This caused multiple assets with varying names and IP address to be associated with one single agent in the CCS console. It also cause the creation of the XML registration file fail to be created.
If agents are already deployed with duplicate agentid.dat GUID's, on each agent go to /esm/config and delete the agentID.dat file, then re-register the agent. If the agents already exist in the CCS console, delete them prior to registration.
Once the /esm/config/agentID.dat was deleted and the agent was re-registered, we saw the registration XML file be successfully created on the manager and successfully imported into the CCS Appserver.
If you need steps to re-register the agent please look up HOWTO28557.
Subscribing will provide email updates when this Article is updated. Login is required.