When you try to connect to the console session of a virtual machine (VM) that is running in Windows Server 2012 by using Microsoft System Center 2012 R2 Virtual Machine Manager (VMM 2012 R2) or Microsoft System Center 2012 Virtual Machine Manager Service Pack 1 (VMM 2012 SP1), the connection fails and you receive the following error message:
Virtual Machine Manager lost the connection to the virtual machine for one of the following reasons.Another connection was established to the console of this machineThe virtual machine has been shut down or put into the saved stateThe user credentials provided do not have the necessary privilege to connect(0x0003, 0x0000)
This problem occurs because connection access to Windows Server 2012 R2 hosts is controlled through a new method that uses the Grant-VMConnectAccess command. In some cases, invalid user accounts in the member list for the Virtual Machine Manager user role can prevent the list from being populated.
For all the details and a resolution, please see the following:
KB2986796 - VMM 2012 Self-Service users cannot open a console session to a virtual machine (http://support.microsoft.com/kb/2986796)
J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division
Get the latest System Center news on Facebook and Twitter:
System Center All Up: http://blogs.technet.com/b/systemcenter/ System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/ System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/ System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
Windows Intune: http://blogs.technet.com/b/windowsintune/ WSUS Support Team blog: http://blogs.technet.com/sus/ The AD RMS blog: http://blogs.technet.com/b/rmssupp/
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
I have to add, that this will also happen, if you use a German Windows for VMM and an English Windows for the hosts, as there will be user accounts "NT Autorität\xxx" which are invalid on the English VM-Hosts.