Error

Guest customization runs on every boot

by

In our vSphere 5.1 update 2 environment we found that some of our Windows virtual machines were running guest customization every time they boot. This was causing them to loose their static IP address and take an additional 5 minutes to boot. To fix this issue, boot to Windows and open regedit. Navigate to to the following location: HKLM\System\CurrentControlSet\Control\Session Manager\ Edit the BootExecute key and remove all sysprepDecrypter.exe lines. We had some VMs with up to 10 entries! Your key should now look like this: Click OK. Now the VM will not perform the guest customization on every boot. To prevent future VMs you deploy from gaining this issue update your vSphere environment to at least 5.1 Update 5.

Authorize Exception Error when logging into vCenter

by

If you get the following error when logging into vCenter(5.1U5): “A general system error occurred: Authorize Exception”   Restarting the Single Sign On service on your vCenter should resolve the issue. In my case the cause of this was due to the LDAP connection pool being exhausted. To confirm this check the ssoAdminServer.log found here: C:\Program Files\VMware\Infrastructure\SSOServer\log Do a search for the following error: No ManagedConnections available within configured blocking timeout If you find that around the time when you was logging in then your LDAP connection pool was exhausted. This issue is resolved in vSphere 5.5. The VMware KB article for this issue 2055448: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2055448  

The VMRC console has disconnected…attempting to reconnect

by

This morning I received an error I haven’t seen before when trying to open the console of a VM in our ESXi 5.5 environment….  “The VMRC console has disconnected…attempting to reconnect.” There are two ways to fix this. The easy way is to reboot your computer 🙂 If you would want to avoid a reboot you can do the following: Close out all of your VMware vSphere Clients and open Task Manager. You will want to make sure all processes named “vmware-vmrc.exe“, “vmware-remotemks.exe“, and “vpxclient.exe” are not running. If they are go ahead and end all those processes.   Now open up the vSphere Client, console should now work:   Comment below and let me know what worked for you!