If you not using VMware Update Manager but you have mulitple ESX/ESXI servers managed by vCenter server you should install and configure it, as it will save you a so much time and its so simple.
However if you have hosts that are not managed by vCenter server or the odd standalone host you need a way of installing updates from VMware as they are released to ensure security compliance and system reliability.
If you are in the unfortunate position in which you or someone else has forgotten the vCenter SSO v5.1 admin@System-Domain password, then you may have a problem. Particularly if there are no other users delegated as SSO administrators.
However the aim of this blog post is to help you in resetting the admin@System-Domain password in SSO 5.1 only (it is much easier in 5.5)!.
First and foremost it's worth pointing out this is completed unsupported by VMware. VMware's advise and supported method is to reinstall SSO.
However you do have 2 other possible options I have presented below.
So far in this Horizon View 6.0 how to series, we have installed a single View Connection Server and installed View Composer on the vCenter server.
We are now going to proceed configuring the service accounts for View to connect to vCenter and join desktops to the domain followed by the events database. Additionally we need to create an OU and delegate permissions on this OU.
After using VMware converter to P2V a physical Windows Server 2003, I have occasionally come across the "PCI standard PCI-to-PCI bridge" install loop.
This isnt actually an "install loop" it is prompting for the drivers for each of the 32 PCI bridges.
I just had an issue with vCenter 5.5 and ESXi 5.5 where I was unable to power on a VM.
The error which I was faced with was a relatively generic message based on the host connection status.
"The operation is not allowed in the current connection state of the host"
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.