Before we begin, let’s cover some basics. In short, there are three possible ways for Windows 8 deployment:
- Manual deployment
- Semi-automated deployment, aka Light Touch Installation or LTI
- Fully-automated deployment, aka Zero Touch Installation or ZTI
Manual Deployment: A manual deployment is something that could happen in homes and really small-to-medium business environments. This approach involves taking a backup of the data, reinstalling the PC by starting a manual setup of Windows 8 (DVD, ISO, etc.), and restoring the user data. This is rather time-consuming, and I personally think it is a bit outdated. Even so, this is still a very good solution for all PC environments with less than ten machines.
Light Touch Installation (LTI): Light Touch Installation means you will use a semi-automated approach for Windows 8 deployment. In short, this involves using a deployment tool, creating an image, and reproducing/deploying the same image to multiple clients by booting from a deployment medium (typically a bootable USB-stick).
Zero Touch Installation (ZTI): By using a Zero Touch deployment mechanism, you basically give the option to the end-user to (re)deploy the machine completely by himself or herself. In short, this starts with the configuration of the deployment tool, creating an image, and automatically
What is the Microsoft Deployment Toolkit 2012 (MDT 2012)?
MDT 2012 is the newest version of the Microsoft Deployment Toolkit (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.
Let Us Start
Configuring MDT 2012 Update 1 to deploy Windows 8 for the 8650w machines is done in nine easy steps:
The Windows Assessment and Deployment Kit (Windows ADK) is a collection of tools and documentation that you can use to customize, assess, and deploy Windows operating systems to new computers.
The Windows ADK is new for Windows 8. Tools that were previously available in the Windows OEM Preinstallation Kit and Windows Automated Installation Kit are now available in the Windows ADK.
Features included in the Windows ADK
The following tools are available in the Windows ADK:
Application Compatibility Toolkit
The Application Compatibility Toolkit (ACT) helps customers understand their application compatibility situation by identifying which applications are compatible with the new versions of the Windows operating system and which require further testing. ACT helps customers lower their costs for application compatibility testing, prioritize their applications, and deploy Windows more quickly.
By using ACT, you can become involved in the ACT Community, including sharing your risk assessment with other ACT users. You can also test your Web applications and Web sites for compatibility with new releases and security updates to Internet Explorer.
Deployment tools enable you to customize, manage, and deploy Windows images. Deployment tools can be used to automate Windows deployments, removing the need for user interaction during Windows setup. Includes:
Windows Preinstallation Environment (Windows PE)
Minimal operating system designed to prepare a computer for installation and servicing of Windows.
User State Migration Tool (USMT)
USMT is a scriptable command line tool that IT Professionals can use to migrate user data from a previous Windows installation to a new Windows installation. By using USMT, you can create a customized migration framework that copies the user data you select and excludes any data that does not need to be migrated. Includes:
Volume Activation Management Tool (VAMT)
The Volume Activation Management Tool (VAMT) enables IT professionals to automate and centrally manage the activation of Windows, Windows Server, Windows ThinPC, Windows POSReady 7, select add-on product keys, and Office for computers in their organization. The VAMT can manage volume activation using retail keys (or single activation keys), multiple activation keys (MAKs), or Windows Key Management Service (KMS) keys.
Windows Performance Toolkit (WPT)
Tools to record system events by using Event Tracing for Windows, and a tool to analyze performance data in a graphical user interface. Includes:
Windows Assessment Toolkit
Tools to discover and run assessments on a single computer.Assessments are tasks that simulate user activity and examine the state of the computer. Assessments produce metrics for various aspects of the system, and provide recommendations for making improvements. Includes:
Windows Assessment Services
Application to remotely manage settings, computers, images, and assessments in a lab environment where Windows Assessment Services is installed.This application can run on any computer with access to the server that is running Windows Assessment Services.
You can install the Windows® Assessment and Deployment Kit (Windows ADK) directly from the Internet. You can also download the installer and copy it to an offline computer.
On a computer that has Internet access, run Windows ADK Setup from this Microsoft website.
Installing MDT 2012 UP1
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.
Create a deployment share
Import the Windows 8 operating system
Import the drivers
Add the sample application
From the properties of the Deployment Share.
We will needed to add two DHCP options
I found this support article http://support.microsoft.com/kb/2797676 , Sysprep and Capture task sequence in Microsoft Deployment Toolkit (MDT) 2012 Update 1 fails when trying to capture a Windows 8 image that was installed from the media. Additionally you may receive the following errors:
This problem occurs because the LTIApply.wsf script fails to check for the existence of the boot folder on the system partition before running the command takeown.exe to change ownership on the folder. The takeown.exe command fails with a “Not Found” error if the boot folder doesn’t exist and causes the Sysprep and Capture task sequence to fail.
To workaround this problem you must edit the following files:
Locate the “Copy bootmgr” section in LTIApply.wsf and add the following code above the existing code under the section:
Now after we modified the two LTIApply.wsf scripts we update the deployment share
We will completely regenerate the boot image this time
WDS is the PXE Responsible so MDT relay on WDS to offer PXE requests
Setup a location for the WDS files
Select Respond to all Client computers
To add the Boot image
We select the boot image we generated from the deployment share
Now we are ready to capture
From the template machine we are going to capture access the MDT distribution share scripts and run the litetouch.vbs script
Select the image location
We now have our template J
Preparing For Windows 8 Template Mass Deployment
First thing we are going to do is to import the Template .WIM file we just captured
From the MDT Workbench
Create Windows8 Deployment task sequence
Fully Automate the Deployment
We now are going to edit the customseting.ini and boot strab.ini to fully automate the migration process
TimeZoneName=Egypt Standard Time
Update the deployment share
We will completely regenerate the boot image again
Also updating the WIM boot file in WDS
We select the boot image we generated from the deployment share
There is our data back from the XP