Link to home
Start Free TrialLog in
Avatar of NytroZ
NytroZFlag for United States of America

asked on

Cannot connect console session in vCenter

I receive the following error when I try to create a console session to one the virtual machines from vCenter

"Unable to connect to the MKS: Permission to perform the operation was denied."

If I log into the host directly and do not have this error and am able to create the console session.
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Have you tried a different vCenter user account ?

when you say logged into host, what server is this vCenter Server ?
Avatar of NytroZ

ASKER

A different vCenter user account provides the same error.

I can log into the single host ESX server(192.168.50.5) directly through the vSphere client then create a console session to the vm on the host without error.  If I log into vCenter(192.168.50.100) then access the vm on the host ESX server I receive the error.
When you login to the host, you will be using root credentials.

when you login to vCenter Server, you will be using user credentials which have been defined by vCenter Server, and the Role may have permissions to stop you looking at the console.

Did you setup the roles and permissions?

Are you logged in with the Super User - Administrator Account via vCenter Server...
Avatar of NytroZ

ASKER

All other vm's in vCenter are ok.  The vm that is having this problem does not have VM tools installed.  Could this be the reason?
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of NytroZ

ASKER

No permissions have been changed.  I will schedule some time this weekend so I can remove the vm from inventory and identify if the issue exists if the vm is off.