Skip to main content

Creating a lab environment

Personal Labs

Microsoft have created lots of test lab for us geeks to try out different Microsoft stuff easy.

The range of product and technologies are wide, we will find basic things like “Step-by-Step Guide for Setting Up IPv6 in a Test Lab” to learn more about IPv6, and more sophisticated guides that also might be more product focused like the “Test Lab Extension: System Center 2012 Endpoint Protection”.

So you will find lots of guides covering different technologies in Windows Server 2008 R2, 2012 and product related like Sharepoint, System Center, SQL and Exchange.

In most cases the guides will be based on the same baseline configuration, so you can actually create a virtual environment that you can export and have ready for the next time you want to try a different lab (or if you messed up the one you have and forgot snapshot/backup)

The Base labs are:

Test Lab Guide: Windows Server 2012 Base Configuration
Test Lab Guide: Base Configuration (Windows Server 2008 R2)

Some of the guides will setup from scratch but in most cases you can just use the base setting and modify them a bit.


Hydration Kits

You can also download different hydration kits to automate the creation of your lab environment. Hydration Kits are a sets of scripts that automate the creation of environments, most commonly using Microsoft Deployment Toolkit (MDT)

There are different types of Hydration kits available. Microsoft Proof of Concept Jumpstart are now out in version 6 and based on System Center Configuration Manager 2012 with service pack 1. It will create a total setup for you like the test lab guide for Windows Server 2012 base configuration. It contains great guides and are an excellent tools to learn Windows deployment 

Microsoft Hydration Kit
There are lots of Hydration Kits that can create lab or production environment from your own fully licensed software (or trial version if you want to). These kits can create a new domain and lots of servers to generate a fitting lab environment for your needs.

The Deployment Bunny

Johan Arwidmark’s

Andrew Barnes

Virtual Labs

If you don’t want to setup an own lab environment you can use Microsoft “Virtual Labs”. The labs will give you a virtual lab environment and a lab manual to work out from.

Windows Server 2012 Virtual Labs

Windows Server 2008 R2 Virtual Labs

Technet Virtual Labs (Different Technologies)

TechNet Virtual Labs: Express (SQL 2008 & R2)

Technet Virtual Labs: System Center

Microsoft Private Cloud Guided Labs

Popular posts from this blog

Changing Windows product key (license) for a MDT OS deployment task

Creating a new OS deployment task in MDT you will be asked to specify product key

That’s easy enough, but what if you type in the wrong key or just want to change it (add it) later? You might even have gotten a new MAK.

That is not as easy, you cannot do it from the graphical interface, you have to do it from one of the configuration files. Well you might to it from graphical interface by typing it in every time deploying a computer gets deployed but that is not a great solution.

MDT - The task sequence has been suspended. LiteTouch is trying to install applications

Every now and then I get this error message when fuelling a computer with MDT:
"The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."

How to get and use the Windows key from UEFI/BIOS

I found myself in the situation that I needed to get the Windows key out from the ACPI in the UEFI bios and preferable get to use it in a task sequence in MDT.

There are different ways of doing this, but I wanted to do this with little code and easy to understand.
There is a nice tool created to get the key on github, created by Christian Korneck, called get_win81key. This tool gives you the key in plane text. You can get it

If I were supposed to do this manually, I now would just take that key and type it in with slmgr command or in the GUI. But I want to do this within a task in MDT.
Testing a couple of solutions without using the get_win8key with my great scripting guru colleague HÃ¥vard ( and figuring out that it cannot be done with default powershell stuff, it needs more code. Therefore, we quickly figured out that some use of the “get_win8key” files is the easiest way, but we need a way of setting the output fro…