Whilst discussing a different problem with a client, they mentioned to me that they had been unable to use AppSense Environment Manager successfully on endpoints with Quest vWorkspace installed. If you are unfamilar with it, vWorkspace uses proprietary agents installed on existing servers and virtual machines to create a unified view of an organization’s desktop virtualization environment. The software uses an enhanced version of Microsoft’s Remote Desktop client to deliver a user environment with a rich media and graphics experience, with applications delivered seamlessly from any number of sources, such as Microsoft Application Virtualization (App-V) or Remote Desktop Services (RDS) servers. This user experience is consistent across multiple platforms, including non-Windows platforms such as Linux and Apple iOS, and is managed from a central vWorkspace administration console. It seemed unusual that Environment Manager wouldn’t play nicely with a particular product, so I did a bit of digging.
It turns out the issue they were experiencing is caused by a bug in the Quest vWorkspace installer, but will only manifest itself if EM is installed after vWorkspace. If EM is installed first, you won’t get any problems. The issue is caused by the vWorkspace installer appending an additional comma to the following Registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
Value: Order
Data (example): RDPNP,LanmanWorkstation,webclient,,EmLogon
Note the erroneous value, the double comma prior to the EmLogon entry. Removing this extra comma will rectify the issue, although you may need a bit of scripting or GPP if you have a lot of endpoints to make the change on. Alternatively, you can simply install EM prior to vWorkspace, which means the extra comma will still exist – it just won’t affect anything.
Share
