Tag Archives: vsphere

ESXi 5.5 update 3b (build 3248547) host fails to connect to vCenter 5.5 U2 after patching…


To cut this long story short – if you have vCenter Server 5.5 update 2 you will have issues if you patch your hosts to the latest available patch level for ESXi. VMware disabled SSLv3 (POODLE and all that..) in update 3b for ESXi meaning if your vCenter Server is running update 2 you won’t be able to connect until the vCenter is patched to update 3b as well. Running ESXi hosts on update 3b and having vCenter Server on update 2 is normally a perfectly valid configuration but because SSLv3 got disabled as part of this process the connectivity is broken.

Example error messages in vpxd log file when patched host in being added to vCenter Server include:

Continue reading

Renaming Local Site on VMware SRM 5.8 from its default value


Pretty silly thing to do really – I have left the default site name when installing SRM 5.8 so it has FQDN of my vCenter box instead of a proper name:


From vSphere Web Client point of view having FQDN in there is not ideal as well as introducing confusion which site is which (live vs. recovery):


To get the site name changed we need to edit vmware-dr.xml which lives (by default) in the following location:

Continue reading

vCenter Multi-Hypervisor Manager connection fails with “A problem occurred while connecting to the vCenter Multi-Hypervisor Manager service. The server fault ‘NoPermission’ had no message.”


I thought that it would be a good idea to finally install vCenter Multi-Hypervisor Manager to manage my 3rd party hosts i.e. Hyper-V – at least that was the initial idea anyway since I don’t have enough time to mess around with SCVMM for now. Multi-Hypervisor Manager server installation was pretty straight forward and so was the client. With plugin enabled in vSphere C# client I was able to see the relevant icon in my client:


but the next screen was not so pretty:


Basically ‘NoPermission’ but I can access vCenter server just fine since I have all the relevant rights! It turns out Multi-Hypervisor Manager assigns the default ‘Admin’ role only to the user specified during the installation of MHM and no one else. During the installation of MHM you have to specify the account that will be made administrator of the third-party hosts inventory:

Continue reading

Virtual machine customisation fails with error “A specified parameter was not correct. spec.identity.userData.computerName”.


Today I was testing some new Windows Server 2012 templates and noticed something rather odd. Basically my costomisations would cause the deployments from template to fail for no real reason. Error message that came up was:


Continue reading

VMware vSphere 5.0 VM Console Shows “Unable to connect to the MKS: Console access to the virtual machine cannot be granted since the connection limit of 0 has been reached.”


Lets dive straight into this error message which happens to be affecting two of my VMs:


As you can see I’m unable to get the console window working! Exact message displayed across the top sheds some light into why this is happening – “Unable to connect to the MKS: Console access to the virtual machine cannot be granted since the connection limit of 0 has been reached.”

I know of at least three different ways to make this error message go away and get to the console window again.
Continue reading