Hyper-V for Developers – Part 1 – Internal Networks

Over the last year, we’ve been working with Microsoft to build training and demo content for the next version of Office Communications Server – code-named Microsoft Communications Server “14”.

This involved building multi-server demo environments in Hyper-V, getting them running on demo servers which we took to TechEd, PDC, and other training events, and sometimes connecting the demo servers to the show networks at those events.  ITPro stuff that should scare the hell out of a developer!

It can get ugly when I occasionally have to venture into ITPro land.  Let’s leave it at that.

Having gone through this process about 10 to 15 times in the last year, I finally have it down.  This blog series is my attempt to put all that knowledge in one place – if anything, so I can find it somewhere when I need it again.

I’ll start with the most simple scenario and then build on top of it in future blog posts.

If you’re an ITPro, please resist the urge to laugh at how trivial this is.

Internal Hyper-V Networks

Let’s start simple.  An internal network is one that intended only for the virtual machines that are going to be on that network – it enables them to communicate with each other.

Create an Internal Network

On your host machine, fire up the Hyper-V Manager and click the Virtual Network Manager in the Actions panel.

Read more: Clarity Consulting

Posted via email from jasper22's posterous