Sign up ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have Hyper-V Server 2012 (free version) running on a box that is not on any domain.

My Windows 8.1 laptop is on our domain. Both machines are on the same physical network.

On my laptop, when I run Hyper-V Manager and attempt to CONNECT TO SERVER I get:

An error occurred while attempting to connect to server "". Check that the Virtual Machine Management Service is running and that you are authorized to connect to the server.

You do not have the required permission to complete this task. Contact the administrator of the authorization policy for the computer ''

What can I do? There is no option to specify alternate credentials. I tried to create a local user on the Hyper-V Server with the same name as the domain user on the laptop, but couldn't since the domain userid is in the format

share|improve this question

4 Answers 4

Add the target account credentials to the Windows Credential Manager from the command line and try reconnecting:

cmdkey /add:TARGET /user:TARGET\USER /pass

Where TARGET is the remote Hyper-V host name and USER is the username added as an Administrator to the Hyper-V server.

As an aside, after having struggled with this configuration myself, I highly recommend running HVRemote on the client and server to aide in troubleshooting potential issues.

share|improve this answer

You can launch mmc with runas and then select the snap in e.g.

runas /user:AlternativeUsername mmc

It's worth reading this complete guide which will get you a nice shortcut too:

Running the Hyper-V Management Tools with Alternate Credentials

share|improve this answer
I have created a local user on the domain laptop with the same name as an administrator account on the server. Running the above in a Command Prompt as Administrator gives: 740 The requested operation requires elevation. – finisterre Jan 15 '14 at 15:06
you might need runas /user:SERVER\Administrator mmc where SERVER is your target Hyper-V server hostname – Colin Pickard Jan 15 '14 at 15:09

Hold Shift while you right-click "Hyper-V Manager", select "Run as different user", and enter credentials that have rights to manage Hyper-V.

Runas would also work if you use this syntax:

runas /user:domain\username /netonly "mmc virtmgmt.msc"

share|improve this answer

Not sure if this relates, but I have two Hyper v servers, they couldn't talk as one came up before the Domain server booted and the network was public, you have to Make sure that both machines are on a private network, if one is public then the connection cannot be made.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.