• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 217
  • Last Modified:

Setup VM on Hyper V

I have deployed my first VM in Hyper-V. The host server is domain controller with plenty resources. The VM is joined to the domain. The VM is a Windows 2012 R2 server. The host is a Windows 2008 R2

A few questions:
I'm not able to access the VM via remote desktop and I have done this hundreds of time on other servers. I know that it is configured correctely. I can access the internet and also another server via RPD from the VM. Is there any special to configure to allow RDP to the VM?

On the domain/host I use the Windows backup option. How does it work backing up the VM? Will it work using the Windows Backup? Say it the host where to crash and I needed to do a bare metal recovery of the host. What would happen to the VM?

Better safe than sorry.
1 Solution
Lee W, MVPTechnology and Business Process AdvisorCommented:
Re: Rdp access - Did you setup the firewall properly on the VM?  Did you enable RDP to the VM in the system Control panel?  Did you install anything on the VM that would potentially block port 3389?  Are you trying to access the RDP session from the LAN or externally from the internet?  If the latter, did you port forward?  (you shouldn't be doing the latter from a security standpoint).

It's easy for you to think you've configured networking correctly, but sometimes you can miss something and THINK you did.  Best to post screen shots - screen shots re-assure us that you did in fact setup things properly.

Re: backup - As you say, better safe than sorry - so TEST IT.  Why is your host 2008 R2 but your VM 2012R2?  Hyper-V 2012 R2 is much improved from 2008R2 - this configuration doesn't make much sense on the surface.

(Backup from 2008 R2 SHOULD backup the VM using a snapshot and allow you to restore - but to be "better safe than sorry" you should learn it through testing as well as questions and books - DO NOT DO THIS TO A PRODUCTION SYSTEM FIRST!  Setup test systems for learning and then DO IT so you learn.  That's one of the best ways to know and feel confident in your configuration - being told something is nice, SEEING IT HAPPEN IN PERSON, is FAR more reassuring.
Cliff GaliherCommented:
Your host is a domain controller??  That'll kill your networking every time. I make it a rule to never even bother attempting to troubleshoot such a configuration. It is known to be broken, it is a nightmare to maintain, and is general unsupportable. 'nuf said.

Re backup, Lee covers all the points I would have.
Another thing. Don't add the Hyper-V role to a DC. You can install a VM as a DC, that is OK, but the Hyper-V server should never be a DC.
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

GerhardpetAuthor Commented:
Thanks for the tip. I had to create a firewall rule to allow traffic on port 3389. I don't recall that from before...is that new on Windows 2012? This is my first Windows 2012 server I deploy. Perhaps I don't do this often enough.

I don't have the time to migrate the domain to a Windows 2012 right now. The Windows 2008 R2 has been in place for 3 years. Perhaps I'll consider that in the future if you say that it is much better.
GerhardpetAuthor Commented:
I'm limited by what the boss is approving for a budget so I have no choice. Will have to ask for approval of a new host.
Lee W, MVPTechnology and Business Process AdvisorCommented:
Your 2012 License grants you TWO VMs - replace the 2008 install with a 2012 Install and run 2008 and 2012 in a VM.  Depending on your license type, all three could be run in VMs.  But Hyper-V hosts should ALWAYS be Hyper-V ONLY! NEVER a DC.  There's a free Hyper-V Server 2012 you could use and use 2012 or Win8 to manage.  Licensing is not a valid excuse for using an older version of Hyper-V at this stage in my opinion.
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.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now