When you open a session, the VUEM agent does not automatically start.
Cause and Resolution
There are a number of possible causes for this issue.
1. The Run at Startup entry for the Agent does not exist
By default, the agent creates a registry entry under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run that launches VUEMDesktopInitMsg.exe in the agent install directory. If this isn't present, the agent will not be launched.
2. The agent configuration GPO is not being pushed to the agent machine fast enough, and so is not present at logon
This can happen when the Active Directory server is slow to respond. To resolve this, you can install the agent with the following switches (see page 18 of the VUEM v2.6 Installation Guide):
WaitForNetwork=1 SyncForegroundPolicy=1 GpNetworkStartTimeoutPolicyValue=60
If this does not resolve the issue, increase the GpNetworkStartTimeoutPolicyValue value in increments of 30 until it does.
3. The desktop network is not fully initialised until after logon, thereby preventing the agent from connecting to the broker at logon
To resolve this, you can install the agent with the following switches:
WaitForNetwork=1 SyncForegroundPolicy=1 ServicesPipeTimeout=120000
If this does not resolve the issue, increase the ServicesPipeTimeout value in increments of 30000 until it does.
NB: if you are not sure whether the agent configuration GPO is present at logon or not in this scenario, you may want to also use the GpNetworkStartTimeoutPolicyValue=60 switch.
4. The user session ID is not being detected correctly due to a bug in Windows Server 2003 x64
To resolve this, please install the following hotfix: http://support.microsoft.com/kb/967587/en-us