Traps VDI license validation failed

[JokinLete]

Hi,

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?

Regards.

[DavidHood]

We are in the process of rolling out a new VDI environment with the latest TAC version. The current environment is 4.0.1 however we could potentially roll out a new version if this will fix the issue.

The agent logs don't seem to be showing anything of interest - agent logs are just showing agent status changing and content updates etc, however the ESM logs do have one error which is agent license validation failed.