April 22, 2013 - Sven Huisman
VMware View Desktop plugin for vSphere Web Client
Today I installed the VMware View Desktops Plug-in on the vSphere Web Client. This plugin is a Technical Preview included with Horizon View 5.2. After installing this plugin you can use the vSphere Web Client to search for a View Desktop user and the Web Client will show the virtual desktop(s) that the user is logged on to. You can use this tool to troubleshoot issues that may arise with an end user’s virtual desktop. If a user calls in with a problem, you can immediately jump to the user’s VM and troubleshoot from there.
The installation is well described in the README.txt file which is located in the following path:
The View Desktops plug-in works with vSphere 5.1 and later versions only. Make sure system clocks are synchronized and valid SSL server certificates are issued with the correct hostnames on all servers.
Before you register the Plugin, VMware recommends to snapshot the vSphere SSO server system, vSphere Web Client system, and vCenter Server system. It’s called a Tech Preview, so when something goes terrible wrong, you can revert to snapshot.
First, you need to configure View to recognize the vCenter Lookup Service. You perform this configuration task once for all View Connection Server instances in a replicated group:
- Open a command prompt on View Connection Server to run the regtool.cmd utility.
- cd C:\<VIEW-installed-directory>\Server\TechPreview\ViewAdminPlugin
- (Optional) set JAVA_HOME to <jre-folder> (set JAVA_HOME=c:\Program Files\VMware\VMware View\Server\jre)
- Configure the Lookup Service: regtool.cmd configureLookupService -u @ -ld https://:7444/lookupservice/sdk
- If the command fails because the certificate is not trusted, accept the certificate thumbprint: regtool.cmd configureLookupService -u @ -ld https://:7444/lookupservice/sdk -lt
When you type the password, the following warning message might appear. You can ignore this message:
log4j: WARN No appenders could be found for logger <com.vmware.vim.vmomi.core.types.impl.VmodlContextImpl>. log4j: WARN Please initialize the log4j system properly
Next, you register the View Desktops plug-in. You need to perform these steps on every View Connection Server in a replicated group:
- Register View Desktops plug-in: regtool.cmd register -u @ -lu @ (@System-Domain for local user)
- Show registration details: regtool.cmd showDetails -u @
The functionality of the View Desktops Plugin is very basic at the moment. What you can do with it is search a user and the Web Client will match the VM-object the user is logged on to.
Log in to the vSphere Web Client as a user with the View Administrators role or View Administrators (read-only) role:
Select the username from the search results:
Then, you select the desktop and use the Virtual Machine page to see details about the desktop virtual machine.
In the Technical Preview you can see where the management interface of View is heading to. I expect that the View Admin console will be more integrated in the vSphere Web Client in a future release. But that is just my speculation.