I worked on this issue on a View 4.0 setup, where the Admin UI was not correctly showing the number of Active Sessions. There were multiple users who were logged in to the VMs on this pool, but the number of Active Sessions were shown as zero and all the VMs were in Ready Status in the View Admin UI, which was incorrect.
The session status of the VM is communicated by the process WSSM.EXE that is running on each of the individual VMs. You can check if this process is running by checking the Task Manager. Ideally, this process would be started on a user logon and is controlled by the below registry key.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit
The value of this key would be something like this.
"C:\WINDOWS\system32\userinit.exe","C:\Program Files\VMware\VMware View\Agent\bin\wssm.exe"
On this computer, the value for this key was pointing to a third party program and there was another key created with the name "UserinitReplaced" and the path for the WSSM.EXE was also missing.
Apparently this third party application had been installed after the View agent was installed. Uninstalling the View agent and reinstalling it, put the missing path under the key "UserinitReplaced" and this resolved the issue.
If doing a recompose after updating the parent VM is not an option, you can push a group policy to update the appropriate registry key ("Userinit" or "UserinitReplaced" ) to include the path for the WSSM.EXE process.
Note: Making any mistakes here might lead to issues like MyDocuments window opening continuously.
http://www.kace.com/support/kb/index.php?action=artikel&cat=2&id=662&artlang=en
If this article is of some help, please leave a comment.
Do you know if there is a way to get the 'view agent' status? I would like to have my monitoringtool reporting me when any VDI has the status 'agent unreachable'. I can't find the status in the ViewComposer database.
ReplyDeleteAny help would be appreciated.
The 'agent unreachable' status is shown when the View Connection Server is not able to communicate with the View agent. This can be due to agent service itself not running or because of network disconnect between the Connection Server and the View VM.
ReplyDeleteThis status should be stored in the ADAM database that is part of the View Connection Server and not in the Composer database.
I am not sure if your monitoring tool can read from the ADAM database.