Upgrading SCCM 2012 R2 to ConfigMgr 1602

image

A customer wanted to upgrade his current Windows 7 Enterprise devices to Windows 10. Right now he was running SCCM 2012 R2, so before I can start creating a Windows 10 task sequence first there some ConfigMgr upgrading has to be done. I started by downloading the SCCM 1511 bits, Windows ADK 10.0 (not the 1511 version!) and the HP WinPE 10.0 driver pack (since the customer is running HP devices only).

When all the bits were downloaded, the upgrade process can start!

Continue reading “Upgrading SCCM 2012 R2 to ConfigMgr 1602”

Microsoft Deployment Toolkit 2013 Update 1 Has Arrived!

 

We had to wait a couple of week (since the launch of Windows 10), but it’s finally there : MDT 2013 Update 1!

At the moment (August 19th) it’s not yet available at http://microsoft.com/deployment

image

 

……… but Aaron has put a nice blogpost together over at the /MSDeployment Blog.

 

“The Microsoft Deployment Toolkit (MDT) 2013 Update 1 is now available on the Microsoft Download Center. This update requires the Windows Assessment and Deployment Kit (ADK) for Windows 10, available on the Microsoft Hardware Dev Center. (Scroll to the bottom of the page to the section, “Customize, assess, and deploy Windows on your hardware.” The page also includes other Windows kits; remember for deployment you only need the Windows ADK for Windows 10.)

Significant changes in MDT 2013 Update 1:

  • Support for the Windows Assessment and Deployment Kit (ADK) for Windows 10
  • Support for deployment and upgrade of Windows 10
  • Support for integration with System Center 2012 R2 Configuration Manager SP1 with the Windows 10 ADK (see this post on the Configuration Manager Team blog for more information on using the Windows 10 ADK with Configuration Manager)

Here is a more detailed list of some specific changes in this release:

  • Support for new Enterprise LTSB and Education editions of Windows 10
  • Support for modern app (.appx) dependencies and bundles
  • Improved support for split image files (.swm)
  • Switched to using DISM for imaging processes (instead of deprecated ImageX)
  • Deployment Workbench revisions for deprecated content
  • Enhanced accessibility within the Deployment Workbench
  • Revised lists of time zones, regions and languages in the Deployment Wizard
  • Removed Start menu shortcut for “Remove PXE Filter”
  • Several MVP recommended fixes for Windows Updates, password handling, and PowerShell cmdlets
  • Added missing OOBE settings to Unattend.xml
  • Unattend.xml default screen resolution changed to allow for automatic scaling
  • Updated task sequence binaries from System Center 2012 R2 Configuration Manager SP1
  • New GetMajorMinorVersion function for integer comparison of Windows version numbers

We are still working to update the MDT documentation on TechNet, so in the short-term will use this blog to share any additional necessary information regarding this release.”

 

 

 

https://www.microsoft.com/en-us/download/details.aspx?id=48595

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!