Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm going to be testing some software, MDT 2010 and Configuration Manager. I would like to create a virtual test environment. The Host box will be running Server 2008 R2 and the clients will be Hyper V boxes. The host will be the Domain Controller for the environment and what I'm looking to do is have one nic be the "WAN" and a virtual nic be "LAN". Is this possible, and if so, how can i set this up? Also should a Quad Core 3.0 ghz with 4gb of memory be enough resources for 2 2008 r2 boxes and 2 win 7 boxes. I have another machine a dual core 2.0 ghz with 2gb of memory, if needed.

share|improve this question
up vote 1 down vote accepted

Yes, this is doable. In Hyper-V virtual network manager you create a new virtual network, using the the virtual NIC. You'll probably want it to be External, the guests can hit the internet (if that's desired), with the radio checked for "Allow management operating system to share this network adapter."

That CPU should be good, RAM might be a little light, depending on what you're actually going to be testing on the guests - stands to reason, right? If you're going to be testing Photoshop or a render farm, then nope.

You haven't said anything about disk layout (spindle count), IO profile, etc - so that may also be a concern for performance. Again, without knowing what your real needs and expected uses are, how can we hope to tell you if you have "enough"?

/Re-reading, that you're going to be testing MDT and SCCM. I have no idea about the latter, although I'm sure it depends on SQL, which may be a concern? For the former, if you're going to be testing backup throughput, then you're definitely going to have to care about IO a lot. If you're only testing configurations and testing small jobs, you're probably OK.

share|improve this answer
This is just going to be for some testing/learning before moving it to the production network. I need to figure out how I can have the physical box connected to the production network to give internet to everyone on the virtual lan, while preventing all network traffic on the virtual lan from touching the production network. – poconnor Jan 31 '12 at 20:14
You want the VM guests to be able to go out to the internet but not anything else on the LAN - you're going to have to play with routing and/or firewall rules, outside of Hyper-V to accomplish this. You can't do that with either Internal or Private, you'll still need to do External, and then further restrict things. – mfinni Jan 31 '12 at 20:26

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.