Create a Virtual Server in Hyper-V Server 2008 without a domain?

I'm trying to create a new Virtual Server on a Hyper-V Server 2008 in an environment without a domain.  One of the Virtual Servers that I create will be an Active Directory server.  I am trying to connect to the Hyper-V server from a Vista client.  When I add the server to the Hyper-V Manager I get an error saying "Cannot connect to the RPC service on computer 'XXX.XXX.XXX.XXX'.  Make sure RPC service is running."
LVL 1
BuchananHaulingAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AdoBeeboCommented:
I understand this as:
Hyper-V Host Server (workgroup)
Hyper-V Guest/VM Server (AD Domain Controller)
Vista Client (workgroup) with the Hyper-V Remote Management Update installed
There's a fair bit of configuration to be walked through before you can get a workgroup client talking to a workgroup Hyper-V Server. John Howard's blog is the only comprehensive source of advice for your configuration that I've found, although I'd be interested to see other resources.
http://blogs.technet.com/jhoward/archive/2008/03/28/part-1-hyper-v-remote-management-you-do-not-have-the-requested-permission-to-complete-this-task-contact-the-administrator-of-the-authorization-policy-for-the-computer-computername.aspx
He has published a script called HVRemote which will perform most of the configuration steps you need to get your Vista client  talking to your Hyper-V Server. If I have understood your setup correctly then you should use this blog to get yourself going as I have had two workgroup setups and on one occasion used the steps in his blog and the second time used the HVRemote script to setup Hyper-V remote management. Why it isn't easier than this completely escapes me, but if every machine is domain joined it's a cinch.
Pay particular attention to his comments about having identical usernames and passwords on each machine, and using those accounts you will create when specified, otherwise you'll spend hours scratching your head like I did. Good luck!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
plimpiasCommented:
THe easiet way to do this is make sure you are logged into an account on the vista machine that exists locally on the hype-v server. If both user accounts name are the same and the passwords are the same it will work.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.