Hi,
I think we can deduce that the user that you are using to run the Multi-Hypervisor Manager service (dhaval) does not have enought privileges to issue WinRM commands. The reasons for that can be different and so far I haven't found a complete list of requirements for a user to be able to issue WinRM commands, but here are some that I know:
- the user should have non-empty password
- the user should not be denied to log-on (e.g. 'Deny access to this computer from the network' from User Rights Assignment policies)
I am pretty sure that if you log-on on the system with the dhaval user and start a command prompt with it and issue a command like 'winm g winrm/config' you will get 'Access is denied'.
If the situation with this user during the Multi-Hypervisor Manager product installation was the same, the installer should have normally displayed an error and not let you to proceed.
You can also check your Windows Event Logs for any errors / warning that might give you a clue about what the root cause is.
That's all that I can guess for now. Another suggestion that I have is that if you reinstall the Multi-Hypervisor Manager and set the "administrator" user to run the service, it should work.
Hope that helps,