Adding GPO Pack support in MDT 2013 for Windows 8.1 & 2012 R2

If you ever tried to use GPO Packs in MDT 2013 or ConfigMgr 012 R2, you quickly find out they will fail for Windows 8.1 or 2012 R2. The reason?  Microsoft forgot to add support for Windows 8.1 in the ZTIApplyGPOPack.wsf script.
Luckily it’s easy to fix, and while you’re at it, why not also add support for Windows Server 2012 R2.

Fix the bug

Find the following section in ZTIApplyGPOPack.wsf (line 86 – 92):

sOSVersion = oEnvironment.Item(“OSCurrentVersion”)
If (Left(sOSVersion,3) = “6.2”) and oEnvironment.Item(“IsServerOS”) then
    sOS = “WS2012RTM”
    oLogging.CreateEntry “Using Default Windows Server 2012 RTM GPO Pack”, LogTypeInfo
ElseIf (Left(sOSVersion,3) = “6.2”) and Not(oEnvironment.Item(“IsServerOS”)) then
    sOS = “Win8RTM”
    oLogging.CreateEntry “Using Default Windows 8 RTM GPO Pack”, LogTypeInfoAnd change to:

If (Left(sOSVersion,3) = “6.3”) and oEnvironment.Item(“IsServerOS”) then
    sOS = “WS2012R2”
    oLogging.CreateEntry “Using Windows Server 2012 SP1 PO Pack”, LogTypeInfo
ElseIf (Left(sOSVersion,3) = “6.3”) and Not(oEnvironment.Item(“IsServerOS”)) then
    sOS = “Win81”
    oLogging.CreateEntry “Using Windows 8.1 GPO Pack”, LogTypeInfo
ElseIf (Left(sOSVersion,3) = “6.2”) and oEnvironment.Item(“IsServerOS”) then
    sOS = “WS2012RTM”
    oLogging.CreateEntry “Using Default Windows Server 2012 RTM GPO Pack”, LogTypeInfo
ElseIf (Left(sOSVersion,3) = “6.2”) and Not(oEnvironment.Item(“IsServerOS”)) then
    sOS = “Win8RTM”
    oLogging.CreateEntry “Using Default Windows 8 RTM GPO Pack”, LogTypeInfo

Or download the file Winking smile

ZTIApplyGPOPack.7z

PXE booting fails with "PXE-T04: Access Violation" and "PXE-E36: Error Received from TFTP Server

I had a very strange issue. After updating to MDT 2013 and ADK 8.1 wen a client response getting error PXE-T04: Access Violation” and “PXE-E36: Error Received.

Solution:

Uninstalling WDS role
Reboot
Installing WDS role

Configuring WDS

Add MDT boot Images.

It works again.

WDS was corrupted Great Sad smile

Microsoft Deployment Toolkit 2013 Final

Download from http://www.microsoft.com/en-us/download/details.aspx?id=40796

Microsoft Deployment Toolkit (MDT) 2013 is a Solution Accelerator for operating system and application deployment. MDT 2013 supports deployment of Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2.
Feature Summary

  • Deploy Windows and Office with Microsoft Deployment Toolkit 2013. MDT is the recommended process and toolset for automating desktop and server deployment. MDT provides you with the following benefits:
  • Unified tools and processes, including a set of guidance, for deploying desktops and servers in a common deployment console.
  • Reduced deployment time and standardized desktop and server images

Some of the key changes in MDT 2013 are:

  • Support for the Windows Assessment and Deployment Kit (ADK) for Windows 8.1. Download final release here 
  • Support for deployment of Windows 8.1 and Windows Server 2012 R2.
  • Support for System Center 2012 R2 Configuration Manager.
  • Improved support x86-based Unified Extensible Firmware Interface (UEFI) systems.

Microsoft Deployment Toolkit 2013 Preview

The Client Management team is happy to announce the availability of the Microsoft Deployment Toolkit (MDT) 2013 Preview. Download the installer file and release notes from the Client Management program on Connect in the MDT group.

New members must first join the MDT group of the Client Management program on Connect.

MDT 2013 Preview includes:

  • Support for the Windows Assessment and Deployment Kit (ADK) for Windows 8.1 Preview. (The Windows ADK for Windows 8.1 Preview is available on the Microsoft Download Center.)
  • Support for deployment of Windows 8.1 Preview and Windows Server 2012 R2 Preview, as well as Windows 7 and Windows 8 families of operating systems.
  • Support for zero-touch integration (ZTI) with System Center 2012 R2 Configuration Manager Preview.

We encourage you to download and use MDT 2013 Preview, and then submit suggestions, bugs and feedback via the Connect site

ADK for Windows 8.1 Preview Available

Here is a quick summary of the changes in ADK for Windows 8.1. MDT 2013  and ConfigMgr 2012 R2 requires ADK for Windows 8.1.

Windows 8.1 Image Size (Preview)
  • Windows 8.1 Preview Code Image (x86), 2.13 GB (WIM), 7.65 GB expanded on disk.
WinPE 5.0
  • Profiling in WinPE 5.0 is removed
  • WinPE 5.0 x64 supports 4 TB of RAM (still 64 GB for x86)
  • Scratchspace set automatically to 512 MB when having more than 1 GB of RAM, otherwise 32 MB
USMT 6.3
  • Support for Windows 8.1
  • You cannot use USMT 6.3 to migrate settings from Windows XP to Windows 8.1
  • Supports Office 2013 (hotfix available for USMT 5.0).
Windows 8.1 Upgrade / Update
  • You are likely to have more free space available on the disk after upgrading Windows 8 to Windows 8.1
  • Windows 8.1 upgrade time, less than 20 minutes
Misc. Updates
  • Export compressed recovery image (/Export-Image)
  • Cleanup base components when superseded. (/StartComponentCleanup /ResetBase)

 Download

ADK for Windows 8.1.

News. Teched is coming… New version of ADK & MDT 2013

Here is a quick summary of the changes in ADK for Windows 8.1. MDT 2013 and ConfigMgr 2012 R2 requires ADK for Windows 8.1.

Windows 8.1 Image Size (Preview)

  • Windows 8.1 Preview Code Image (x86), 2.13 GB (WIM), 7.65 GB expanded on disk.

WinPE 5.0

  • Profiling in WinPE 5.0 is removed
  • WinPE 5.0 x64 supports 4 TB of RAM (still 64 GB for x86)
  • Scratchspace set automatically to 512 MB when having more than 1 GB of RAM, otherwise 32 MB

USMT 6.3

  • Support for Windows 8.1
  • You cannot use USMT 6.3 to migrate settings from Windows XP to Windows 8.1
  • Supports Office 2013 (hotfix available for USMT 5.0).

Windows 8.1 Upgrade / Update

  • You are likely to have more free space available on the disk after upgrading Windows 8 to Windows 8.1
  • Windows 8.1 upgrade time, less than 20 minutes

Misc. Updates

  • Export compressed recovery image (/Export-Image)
  • Cleanup base components when superseded. (/StartComponentCleanup /ResetBase)