We have detected that the agents are not registering in the ESM console. If we check the agent's console, it shows that it's connecting correctly to the Server, but in the console the agent does not appear.
If we force the heartbeat, the agent changes the status to unlincesed, and it appears in the console like unlicensed too. There are more than 6000 licenses free so we do not understand why it changes to unlicensed status.
If we force once more the heartbeat, the status changes to correct, and it appears correctly in the ESM console. But after 5 minutes it disappears again from the console.
After reviewing the configuration, we have disabled the check of the ESM of automatic license revocation. After we have changed this configuration, the agents have started connecting correctly. Also we have checked that some agents that are connected to the ESM have the last heartbeat from last week, and they are still running. So we do not kn ow if there is a reporting issue too.
After disabling the check of the license revocation, we have checked that some VDI pools are not connecting to the ESM. They are having the same issue with the automatic license revocation disabled.
Why can be this happen?
We have deployed a new installation with same infrastructure using the latest version of Traps ESM.With the new version is seems that it is solved, but we have not change the VDI Endpoints to the new infrastructure.
What version are you using?How is the license revocation configured?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!