I had the same problem as Quch: the Hyper-V root partition also happened to be the domain controller. You can’t create “local users” in a domain controller because there’s no such thing as a local users database.

What worked for me though is the following: make sure the username and/or password of the domain user you want to be authenticated as is not the same as on your non-domain local machine. If you use a different password, for example, try to browse to the computer (start->run->”\\servername”) and it will show you a password dialog in which you can then type in the corrent username (including the correct domain name!) with which you want to connect.

Check the box “save password” and it’ll save your credentials in your managed passwords. Next time, the Hyper-V manager will use those credentials to connect, and it’ll work. At least it worked with me.

Now I used to know where you could manage these “saved passwords” in 2000 and XP, but I can’t seem to find the same dialog in Vista.

Dave

You’re way beyond my level of HyperV experience. I’ve never laid eyes on SCVMM, and you say “HVRemote script doesn’t work”. As far as I can tell, the steps outlined by John Howard and echoed here with variations don’t require any scripting.

The main hazard in my scenario is getting a machine that is a member of a domain to allow access from a machine or user that is not part of the domain. The trick for that is to create a normal local user account on the target server and set up your remote connection to authenticate using that local user account instead of a domain user account.

-Danny

Very nice – this is my scenario but with slightly differences – my Hyper-V server is also a domain controller (no local groups :) and is managed by SCVMM (HVRemote script doesn’t work). Any suggestions?? :)