Archive for the ‘View Agent’ tag
VMware just released the Version 3.1.1, a new maintenance release of VMware View. You’ll find the details on the VMware View web site.
VMware View already came with USB redirection in his early stages but now with View 3.1, released last week it becomes more flexible. By default HID (Human interface devices) are filtered out because it wouldn’t be good to have the local keyboard, mouse or other device which is needed local, redirected to the virtual desktop session.
The VMware View Client delivers useful information to the VMware View Agent which can be found in the virtual desktops Windows registry. This information can be used by scripts i.e. for mapping the right network printer based on the location of the View Client device.
Contrary to popular belief, you don’t actually need vCenter and ESX(i) to use View. If you want to utilize VMs from other platforms as your desktops you need to change one thing when installing the agent onto those VMs.
Make sure to start with a fresh and current image. As of this writing that is 5.1.606 revA. Load the image and confirm that the green lock in the systray comes up green after all the rebooting. If you get a red “x” do it again.
There are several reasons why you might need several GINA’s using View. Problem is it’s not well documented on how to actually chain them together and make it work. So here is a quick post on how to do that.
Running Novell eDirectory with view is problematic and not supported. However here is how you do it if you feel so inclined. I would like to thank a very good customer of mine, Carl Hooker for helping me solve this riddle in his environment.
When browsing the file system on the View connection server you’ll find four ADM files in the server’s program files directory: C:\Program Files\VMware View\Server\Extras\GroupPolicyFiles. With those files you can easily manage the View Server, View Client and View agent configuration settings.
Since Virtual Desktop Manager 2.1 the VMware Virtual Desktop Infrastructure got a default setting which blocks direct RDP connections to the virtual desktops. When a user tries to connect to the desktop with a standard Microsoft RDP client he will get a message stating: Access denied. In case that there was a requirement for connections from non-View/VDM clients the administartor needed to change a registry parameter to enable the access.
With VMware View and RDP the administrator can redirect the client drives to the virtual desktop through a standard RDP function. The client drives are connected as network drives. Without any additional configuration all local client drives will be redirected to the virtual desktop.