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.”

VMware_vSphere_Logo

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:

vCenter_Multi-Hypervisor_Manager_fails_with_A_problem_occurred_while_connecting_to_the_vCenter_Multi-Hypervisor_Manager_service_The_server_fault_NoPermission_had_no_message_4

but the next screen was not so pretty:

vCenter_Multi-Hypervisor_Manager_fails_with_A_problem_occurred_while_connecting_to_the_vCenter_Multi-Hypervisor_Manager_service_The_server_fault_NoPermission_had_no_message_1

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:

vCenter_Multi-Hypervisor_Manager_fails_with_A_problem_occurred_while_connecting_to_the_vCenter_Multi-Hypervisor_Manager_service_The_server_fault_NoPermission_had_no_message_2

and that’s the account that will have enough rights to use the plugin:

vCenter_Multi-Hypervisor_Manager_fails_with_A_problem_occurred_while_connecting_to_the_vCenter_Multi-Hypervisor_Manager_service_The_server_fault_NoPermission_had_no_message_3

If you want other accounts to have access to the MHM plug-in, you must specify them under the Permissions tab – bit strange that VMware didn’t add Domain Admins by default but hey!

Important thing to note is that permissions assigned at the vCenter level do not propagate to vCenter Multi-Hypervisor Manager section of the client so you have to assign them separately.

Leave a Reply