vSphere Update Manager 5.1 is one of components of vSphere 5.1 and it's purpose is the update, upgrade and patch your ESXi servers and virtual appliances. It can also be used to update VMware Tools for the VMs.
One important thing to note, is that since Update Manager 5.0 no longer provides updates to the guest OS (Windows and Linux) as in previous releases.You will need to use mangement products such as WSUS or System Center for Windows and setup your own update repo for Linux.
It does still provide updates for hosts, including upgrading from ESX/ESXi 4 to ESXi 5.
You cannot upgrade from ESX/ESXi 3.x to ESXi 5 (as one would expect).
When trying to remove a vCenter Server from VMware Horizon View Administrator, all pools and desktops managed via that vCenter server must be deleted first.
If they are not, you will get the following warning message and the vCenter server will not be removed:
"The pools and transfer servers associated with this vCenter must be deleted before this vCenter can be removed"
By creating multiple VMKernel NICs it makes it possible to have multiple paths to iSCSI SAN storage and utilize MPIO.
However to do this and implement certain performance tweaks this has to be done partly via the GUI and partly via the service console. Hopefully in the future VMware will implement additions to the GUI to allow this.
While you may have several physical network adaptors connected to a vSwitch (in this case a distributed vSwitch - DVS), the VMkernel ports are required to make different connections/sessions to the iSCSI SAN storage device(s).
In this case it is used to configure MPIO via ESX 4 and a Dell EqualLogic PS SAN array. However the process should be similar if not the same for other vendor iSCSI SAN storage.
vSphere 5.0 saw the vSphere Web Client make it's entry but with limited functionality compared to the installed vSphere Client.
However now the tables have turned and with the release of vSphere 5.1 VMware are now pushing the vSphere Web Client as the management point.
Only the new features in vSphere 5.1 can be managed via the vSphere Web Client and the old vSphere Client will eventually disappear in future releases.
To be honest I like the idea that I don't have to install the correct version client as I work on so many different customers systems, but I do find the web client slow to respond (like View).
If you have Active Directory trusts within the domain that your VMware Horizon View Connection Server is joined to, you may have noticed these additional trusted domain within View Administrator.
You may also have seen them in the domain drop down box in the View Client and HTML Access login dialogs.
In many cases these domains are not required to logon to Horizon View virtual desktops and ideally to make this cleaner and simpler for users these domains should be excluded.
If you see the domain with a "Red" status indicator within View Administrator, this means that while the domain is trusted, the View connection server cannot reach any domain controllers in that domain to authenticate users.
Share this blog post on social media:
TweetAll advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.