VMware took security to a whole new level in VMware View 5.1 Certificates are here and they are configured in a completely different way than previous versions of View. Have fun!
All connection, security, transfer, composer, and vCenter servers must have SSL certs signed by a Certificate Authority (CA) or you will receive warnings about untrusted connections. Please pay close attention to the VMware View 5.1 Installation and Administration guides.
Being a small IT shop, I have little experience with certificates. After a lot of trial, error, reading, and a support call to VMware, I finally figured out how to do it. I recorded a brief video capturing part of the process: http://www.youtube.com/watch?v=JCWkZj1EgBI
Stay tuned to more posts in this series about VMware View 5.1 “Lessons Learned” by following along with the tag: VMware View 5.1
Phillip Reynolds is a guest blogger. You can also follow him on twitter: @philvirtual
If you are using VMware View and dual displays, DO NOT upgrade your Virtual Machine hardware to Version 8! There are major graphics issues with this version. The biggest issues are seen when moving windows between displays. And the performance was AWFUL.
Already upgraded to HW 8 like I did? VMware’s KB article provides a work around by editing the VMX file of the VM (or parent VM) in question: Poor performance when moving windows between multiple displays in View 5.0 session VMware Support says that they are working on a patch and there is no ETA.
This issue is limited to this configuration:
- Windows 7 View virtual machines (both 32bit and 64bit)
- Virtual machine hardware version 8
- View Agent 5.0 or higher
- Client desktop utilizing multiple displays
Stay tuned to more posts in this series about VMware View 5.1 “Lessons Learned” by following along with the tag: VMware View 5.1
Phillip Reynolds is a guest blogger. You can also follow him on twitter: @philvirtual
I’ve had some issues with the transition to VMware View 5.1 in regards to performance and display problems. Through KB Articles and the VMware support engineer, I’ve learned some valuable information about the VMware View Agent.
- Install the View Agent LAST after you setup your vm, install applications, do windows updates, and get the VM the way you want it.
- If you are running Windows Updates on your View desktop, you should make it a habit to reinstall the View Agent each time — you never know what the updates might have screwed up. And NEVER have Windows Updates set to automatic on View!
- Need to clone your parent VM for some reason? Uninstall the View Agent before making the clone.
- If you’re uninstalling the View Agent, check the registry after you reboot to make sure it is completely gone before you reinstall the View Agent: HKLM\Software\VMware Inc. You should not have a View Composer or VMware VDM folder anymore. *BE CAREFUL!*
**These are just my own personal suggestions. Be very careful and make sure you have backups before editing the registry! YMMV (Your mileage may vary!)**
Stay tuned to more posts in this series about VMware View 5.1 “Lessons Learned” by following along with the tag: VMware View 5.1
Phillip Reynolds is a guest blogger. You can also follow him on twitter: @philvirtual
Having strange issues with your Win 7 linked clones or manual desktops? I was! Apparently there is a small bug in the VMXNET3 setup with Windows 7 and Windows 2008.
According to VMware, “This issue occurs due to the way the VMXNET 3 adapter is added. The Windows 7 guest operating system identifies the adapter as a new device and does not properly install the driver during the cloning process.”
#Fail
There is a special patch available for download directly from Microsoft and the full links to the information are available on this VMware KB article from April 25, 2012: http://kb.vmware.com/kb/2007319
Stay tuned to more posts in this series about VMware View 5.1 “Lessons Learned” by following along with the tag: VMware View 5.1
Phillip Reynolds is a guest blogger. You can also follow him on twitter: @philvirtual
