Here is how to replace the SSL certificates on VMware Update Manager running under vCenter 5.1. I found the text from the following document, just reposting for future reference/ease of access: http://www.vmware.com/files/pdf/techpaper/vsp_51_vcserver_esxi_certificates.pdf
- Back up the existing Update Manager certificates.
- Copy the newly created certificate files (rui.crt, rui.key, and rui.pfx) to the Update Manager SSL directory on the system where Update Manager is installed.
- Typically, the directory is C:\Program Files\VMware\Infrastructure\Update Manager\SSL.
- Stop the VMware vSphere Update Manager service.
- Change to the Update Manager installation directory.
- Typically, the directory is C:\Program Files\VMware\Infrastructure\Update Manager\.
- Run the file VMwareUpdateManagerUtility.exe.
- Note, this might take a couple of seconds to startup, there was a delay for me.
- In the Options pane, click SSL Certificate.
- In the Configuration pane, select Followed and verified the steps and click Apply.
- You should receive the following text when it is done: "Successfully applied the configuration."
- After the operation completes, start the VMware vSphere Update Manager service.
Host sensor data is not updated. The Query Service is not available or was restarted, please retry.
I have run across this issue a couple of times now when shutting down a few of our hosts (including vCenter) and them booting them all back up at the same time in the lab. Due to the way that the VMs were booting back up, some of the VMware services were not starting properly and would result with the inability to view the Hardware status tab in vSphere.
To resolve this issue, simply go through and restart the services on your vcenter box and you should be back in business. Restarting the VMware VirtualCenter service specifically should take care of things (it might ask to restart VMware VirtualCenter Management Webservices as well... that's fine).
As a side note, I did try going through ADSI and changing some values, however I feel this is more of an issue due to the way your VMs come alive and associated dependencies (SQL backend, DCs, etc.)
Hope this helps!
Today I had an issue with a VM not wanting to power off. I found an excellent article from http://markvansintfiet.wordpress.com/2010/07/28/forcefully-kill-a-virtual-machine-in-esxi/ that I am reposting in case the website ever goes down.
One day you’ll run into a not responding virtual machine that won’t power off in the vSphere client. If you don’t want to reboot your ESXi host, here is how to forcefully kill the bastard leaving all other virtual machines peacefully running.
Method 1: Use the vmware-cmd command in the vSphere command-line interface (CLI)
- Download and install vSphere command-line interface(http://www.vmware.com/download/download.do?downloadGroup=VCLI40)
- CD to C:\Program Files (x86)\VMware\VMware vSphere CLI\bin>
- List Virtual Machines
vmware-cmd.pl -H <ESXi host name> -l
- Get state:
vmware-cmd.pl -H <ESXi hostname> “<vmx file path>” getstate
- Kill Virtual Machine:
- vmware-cmd.pl -H <ESXi hostname> ”<vmx file path>” stop hard
When method 1 fails move to method 2.
Method 2: Find the VM’s process identifier and forcibly terminate it (or use SSH if you are lazy and don't mind opening security holes)
- List active virtual machines: vm-support -x
- On the ESXi console, press Alt-F1.
- Type the word unsupported and press ENTER
- Type root password and press ENTER
- Look up the VM process pgid: ps –g | grep
(The number you are looking for is the one that is right before and after mks: and vcpu)
- Kill the process: kill -9 <pgid, the number you just found>
- Wait a minute and check if the machine is not running anymore: vm-support -x
So to do this in ESXi, see this tutorial: http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1014165
I found out that the commands from ESX are completely different, so if you are receiving the "vmware-cmd" not recognized, you are probably running ESXi and need to use the commands from the KB article above.