MDT 2012 Update 1 no longer uses SETUP.EXE to install Windows 7 and above. One side effect of this is that $OEM$ folders are no longer going to be copied, since that was something that SETUP.EXE did that the MDT LTIApply.wsf script doesn’t handle.
I’ve never been a big fan of using the $OEM$ folder structure, as it’s just as easy to add explicit XCOPY steps into the task sequence. But for those of you out there that are using them, you can leverage the attached script (CopyOEM.zip) in your task sequence to do that.
To set this up, first copy the script into your deployment share. Then, add a new step to the task sequence right after the “Install Operating System” step to run the script. It should look like this:
Now, it will follow the original MDT logic for locating the appropriate $OEM$ folder to use, checking in this order:
where %DeployRoot% is the path to the deployment share, %TaskSequenceID% is the ID of the running task sequence (e.g. WIN8), %SourcePath% is the path within the deployment share for the operating system being used, and %Architecture% is either X86 or X64, depending on the boot image being used.
Once it finds a folder, it will look for two folders in that $OEM$ folder and copy them to the appropriate place for the new OS:
$1 will be copied to the root of the volume that the new OS image was applied to.
$$ will be copied to the Windows folder on the volume that the new OS image was applied to.
The script doesn’t deal with any other folders because it’s too messy to do that from within Windows PE – drive letters aren’t the same as what they would end up being in the full OS
When you configure MDT you could specify an organization name To specify these, you can configure them in CustomSettings.ini:
_SMSTSOrgName=WardVissers _SMSTSPackageName=My Package Name
That’s great if you want to hard-code the values, but what I wanted was that _SMSTSPackageName is set to the name of the task sequence that is being executed. That’s a little harder to do, because the task sequence hasn’t yet been selected when CustomSettings.ini is being processed, and you can’t set these read-only variables once the task sequence has started.
So this is one of those cases where you have to modify one of the MDT scripts, in this case LiteTouch.wsf. Fortunately, it’s a really trivial change. Look for this line:
Microsoft Deployment Toolkit (MDT) 2012 Update 1 is the newest version of MDT, a Solution Accelerator for operating system and application deployment. MDT 2012 Update 1 supports deployment of Windows 8, Windows 7, Office 2010 and 365, Windows Server 2012, and Windows Server 2008 R2 in addition to deployment of Windows Vista, Windows Server 2008, Windows Server 2003, and Windows XP.
Some of the key changes in MDT 2012 Update 1 are:
Added support for Windows 8 and Windows Server 2012.
Support for System Center 2012 Configuration Manager SP1 CTP: Added support in MDT for deploying Windows 8 and Windows Server 2012 with Configuration Manager 2012 SP1 CTP, while supporting all new Configuration Manager functionality (offline BitLocker, UEFI, and Assessment and Deployment Kit).
Support for DaRT 8 Beta: Updated MDT to support DaRT 8 for Windows 8 deployments, while continuing to support DaRT 7 for Windows 7 deployments. Added DaRT support for Configuration Manager scenarios.
New “Build Your Own Pages” User-Driven Installation (UDI) feature: Enhanced the UDI wizard and designer to enable IT pros to design their own wizard pages with little effort.
New System Center 2012 – Orchestrator support: Provided the ability to add steps into an OS deployment task sequence to execute Orchestrator runbooks as part of the deployment process.
Other improvements: Added support for Windows PowerShell 3.0, reworked Roles and Features installation logic for Windows 8, improved “boot from VHD” deployment scenarios, and added support for Configuration Manager monitoring.
Download the latest release to stay up-to-date on your deployment needs. New features and enhancements make large-scale desktop and server deployments smoother than ever!
This release expands your deployment capabilities with support for the latest software releases, including Windows 8 Release Preview, Windows Server 2012 Release Candidate, and System Center 2012 Configuration Manager SP1 Community Technology Preview. Other notable new features include:
[HP6560B] = TaskSequenceID in my Case MachineObjectOU=ou=laptops,ou=ward,dc=wardvissers,dc=local BdeInstallSuppress=NO BDEDriveLetter=S: BDEDriveSize=300 SkipBitLocker=NO BDEInstall=TPM BDERecoveryKey=AD OSDBitLockerWaitForEncryption=TRUE BDEKeyLocation=\\ward-bh01.wardvissers.local\Bitlocker$
And change the following SkipBitLocker=YES under [DEFAULT]
In my case on the OU Laptops I created the following Bitlocker Group Policy
MDT includes the following improvements for LTI deployments:
Support for Windows 8 Consumer Preview and Windows Server 8 Beta. Note: The deployment of Windows Server 8 Beta roles and features using the Install Roles and Features task sequence action is not supported.
Support for the Windows Assessment and Deployment Kit (Windows ADK). Note: Currently, the Windows ADK is only supported for deploying Windows 8 Consumer Preview or Windows 7 in lab environments, not in production environments.
Monitoring of LTI deployment process. MDT includes the new LTI monitoring feature that allows you to perform centralized monitoring of LTI deployments in the Monitoring node in the Deployment Workbench.
Deployment of Windows Recovery Environment (Windows RE). Windows RE helps users troubleshoot and recover from startup-related problems on their computers.
Deployment of Microsoft Diagnostics and Recovery Toolkit (DaRT).
Deployment to computers that use the Unified Extensible Firmware Interface (UEFI).
Deployment to computers that require the new globally unique identifier (GUID) Partition Table (GPT) format.
Deployment to virtual hard disks (VHDs) for native boot.
There is a new feature in MDT 2012 RC1. It will keep the list of items (applications, drivers OS packages, task sequences) in alphabetical order.
Now when you first install MDT 2012 RC1, you might notice that the items aren’t sorted right away – you have to change something in the folder first. As soon as you do (e.g. add an item, rename an item), the items in that folder will be sorted.
Keeping the list of folders sorted is a much bigger challenge, so at this point they will still show up in the order that they were added.
Support for Configuration Manager 2012 RC2: This update provides support for Configuration Manager 2012 RC2 releases. MDT 2012 fully leverages the capabilities provided by Configuration Manager 2012 for OS deployment. The latest version of MDT offers new User-Driven Installation components and extensibility for Configuration Manager 2007 and 2012. Users now also have the ability to migrate MDT 2012 task sequences from Configuration Manager 2007 to Configuration Manager 2012.
Customize deployment questions: For System Center Configuration Manager customers, MDT 2012 provides an improved, extensible wizard and designer for customizing deployment questions.
Ease Lite Touch installation: The Microsoft Diagnostics and Recovery Toolkit (DaRT) is now integrated with Lite Touch Installation, providing remote control and diagnostics. New monitoring capabilities are available to check on the status of currently running deployments. LTI now has an improved deployment wizard user experience. Enhanced partitioning support ensures that deployments work regardless of the current structure.
Secure Deployments: MDT 2012 offers integration with the Microsoft Security Compliance Manager (SCM) tool to ensure a secure Windows deployment from the start.
Reliability and flexibility: Existing MDT users will find more reliability and flexibility with the many small enhancements and bug fixes and a smooth and simple upgrade process.
Support for Windows 8: The RC1 release of MDT 2012 provides support for deploying Windows 8 Consumer Preview in a lab environment.
Full use of the capabilities provided by System Center Configuration Manager 2012 for OS deployment.
Improved Lite Touch user experience and functionality.
A smooth and simple upgrade process for all existing MDT users.
For System Center Configuration Manager customers:
Support for Configuration Manager 2012 (while still supporting Configuration Manager 2007)
New User-Driven Installation components for Configuration Manager 2007 and Configuration Manager 2012
Extensible wizard and designer, additional integration with Configuration Manager to deliver a more customized OS experience, support for more imaging scenarios, and an enhanced end-user deployment experience
Ability to migrate MDT 2012 task sequences from Configuration Manager 2007 to Configuration Manager 2012
For Lite Touch Installation:
Integration with the Microsoft Diagnostics and Recovery Toolkit (DaRT) for remote control and diagnostics
New monitoring capabilities to see the progress of currently running deployments
Support for deploying Windows to computers using UEFIAbility to deploy Windows 7 so that the computer will start from a new VHD file, "Deploy to VHD"
Improved deployment wizard user experience
For all customers:
Integration with configuration templates from the Security Compliance Manager Solution Accelerator, ensuring Windows is secure from the start
A simple mechanism for running Windows PowerShell scripts during a deployment, with task sequence environment and logging integration
Better partitioning support, creating the recommended partitioning structures on new computers and ensuring deployments work regardless of the current structure
A smooth and simple upgrade process for all existing MDT users
Here is a common scenario. You are deploying an operating system using MDT Lite Touch, during the deployment you install some user specific applications. However the users think that the deployment is completed an they close the application installs or perhaps start messing with the machine while it is still logged in as the local administrator. Now you could simply inform the user that they should not touch the computer until the deployment is completed. However in my experience this “don’t touch” approach has not always been 100% successful.
Well now we have a better way, you can hide explorer shell while MDT is “doing it’s thing”!
So how do we do this? It is simple, just add the following line to the customsettings.ini file: