Deploying Windows Server 2008 R2 (non-VL) with MDT 2012 & Windows ADK

Just a few weeks ago Microsoft has released MDT 2012 Update 1, with full support for Windows Server 2012 and Windows 8. Microsoft did also release the Windows Assessment and Deployment Kit (ADK) for Windows 8, the replacement for the good old WAIK. With the RTM of Window Server 2012 I decided to upgrade my Deployment environment to the latest version. When I did some initial deployments of Windows 8 and Windows Server 2012 everything worked just fine, but when I tried to deploy Windows Server 2008 R2 (non-VL version) or Windows 7, I ran into a small problem.

The Issue
Just after the deployment I had to enter the Product Key.

image

At first I thought I made a mistake during the built proces, but after I asked a question at the Microsoft Deployment Toolkit Forum. Because the first responses suggested that there was something wrong with my Deployment Share. After some suggestions and a start from scratch (the first time I imported and upgraded the ‘old’ deployment shares), also not importing the ‘old’ deployment shares, the answer came from Michael Niehaus:

“MDT 2012 Update 1 switched from using SETUP.EXE to instead use ImageX to apply the image.  As a result, if you use retail or OEM media, you’ll get a prompt because the product.ini file isn’t being read any more (SETUP.EXE did that, ImageX doesn’t).

Fortunately the fix is pretty simple:  Look up the correct setup (generic) key in the product.ini file on your media and specify it in the unattend.xml (second location).  After you do that, it won’t prompt any more.

This won’t happen with volume license media.”

So that’s probably why the people who responded earlier didn’t have the same issue, they were (probably) using volume license media!

 

The Solution
So, to fix the issue had to specify the (generic) product key (from the product.ini in the Sources folder)

image

image

Open the unattend.xml (in the correct Control  Task Sequence folder) and enter the product key at the second   start-tag.

image

Now you can just restart the Task Sequence and you won’t be asked for a product key during the deployment!

Just a few weeks ago Microsoft has released MDT 2012 Update 1, with full support for Windows Server 2012 and Windows 8. Microsoft did also release the Windows Assessment and Deployment Kit (ADK) for Windows 8, the replacement for the good old WAIK. With the RTM of Window Server 2012 I decided to upgrade my Deployment environment to the latest version. When I did some initial deployments of Windows 8 and Windows Server 2012 everything worked just fine, but when I tried to deploy Windows Server 2008 R2 (non-VL version) or Windows 7, I ran into a small problem.

The Issue
Just after the deployment I had to enter the Product Key.

image

At first I thought I made a mistake during the built proces, but after I asked a question at the Microsoft Deployment Toolkit Forum. Because the first responses suggested that there was something wrong with my Deployment Share. After some suggestions and a start from scratch (the first time I imported and upgraded the ‘old’ deployment shares), also not importing the ‘old’ deployment shares, the answer came from Michael Niehaus:

“MDT 2012 Update 1 switched from using SETUP.EXE to instead use ImageX to apply the image.  As a result, if you use retail or OEM media, you’ll get a prompt because the product.ini file isn’t being read any more (SETUP.EXE did that, ImageX doesn’t).

Fortunately the fix is pretty simple:  Look up the correct setup (generic) key in the product.ini file on your media and specify it in the unattend.xml (second location).  After you do that, it won’t prompt any more.

This won’t happen with volume license media.”

So that’s probably also the people who responded earlier didn’t have the same issue, they were using volume license media!

 

The Solution
So, to fix the issue had to specify the (generic) product key (from the product.ini in the Sources folder)

image

image

Open the unattend.xml (in the correct Control  Task Sequence folder) and enter the product key at the second   start-tag.

image

Now you can just restart the Task Sequence and you won’t be asked for a product key during the deployment!

  • theStorm

    i hope you have changed the keys before posting them online 😉

    • Nope I didn’t, but it’s a general product key which you can find on your Windows Server 2008 R2 ISO. 🙂

  • Stefan

    They way you’re doing it is not legal.According to Microsoft you must enter the OEM key manually from that specific machine after install and then activate via KMS or the internet.Unless you have VL keys