Windows Deployment Tools
Applies To: Windows 8.1
When you deploy Windows 8.1 to PCs in education there are many tools you can use to customize and automate deployments, migrate user accounts and data, create scripts, and more.
Microsoft provides numerous tools to assist in Windows deployment. Like the deployment strategies already discussed, the tools range in complexity, with certain tools being more appropriate for different deployment scenarios and environments. For example, using a tool like Deployment Image Servicing and Management (DISM) means learning its syntax and also being comfortable with Windows PowerShell scripting. By contrast, the Microsoft Deployment Toolkit (MDT) provides as easy method for automating deployments without requiring you to create scripts or learn cmdlet syntax. This section looks at some of the tools available for Windows deployment.
Windows Assessment and Deployment Kit
The Windows Assessment and Deployment Kit (Windows ADK) is a collection of tools that’s new for Windows 8 and Windows 8.1. The Windows ADK includes the tools previously found in the Windows OEM Preinstallation Kit and the Windows Automated Installation Kit. The Windows ADK includes the following tools:
Application Compatibility Toolkit (ACT)
Windows System Image Manager
Windows Preinstallation Environment (Windows PE)
Windows User State Migration Tool (USMT)
Volume Activation Management Tool (VAMT)
Windows Performance Toolkit
Windows Assessment Toolkit
Windows Assessment Services
Various other tools, such as the Oscdimg command-line tool
Using the Windows ADK requires using the right tools in the right order. For example, the first step when designing a deployment with the Windows ADK is to create and optionally customize a Windows PE image. You create an answer file to interact with Windows Setup, then generalize the image by using the System Preparation Tool (Sysprep) and capture it by using the DISM tool.
Although the Windows ADK contains all of the tools you need for deployment, using it requires a certain level of expertise and prior experience creating and managing images. For this reason, Microsoft recommends a more automated means, such as MDT or Microsoft System Center 2012 R2 Configuration Manager for most deployments.
The Application Compatibility Toolkit
You use the ACT to verify that applications are compatible with the version of Windows you are deploying. Although this step is optional, it can help to reduce the number of problems you may encounter during later steps or after deployment. For example, some educational applications that work with the Windows XP operating system may not work with Windows 8.1. It will require less effort to correct any application compatibility problems now rather than after the image has been deployed throughout the school.
Using ACT has three steps:
Collect inventory. Create an inventory collector package, and deploy it to client computers. The package gathers system inventory, device inventory, and software inventory from the client computers on which you install the package. You can deploy the inventory collector package by using Group Policy Software Installation, a logon script, System Center Configuration Manager, or manually.
Test and analyze. Perform tests using a runtime analysis package, and then analyze the compatibility results through compatibility reports.
Mitigate compatibility issues. Decide how to resolve any compatibility issues, including whether to fix an application or deploy a workaround.
Windows Preinstallation Environment
Windows PE is an important tool in the imaging process. Using Windows PE, you can capture and deploy Windows images and start Windows Setup as well as perform other tasks, such as partitioning a hard disk and creating recovery images.
When preparing a computer for deployment, you create a Windows PE image by copying the Windows PE files into a folder on the technician’s computer. If necessary, you can use DISM to add drivers and other packages to the Windows PE image. You then install the Windows PE image on a USB flash drive or other media. Finally, test the reference computer by using the Windows PE image.
The System Preparation Tool
Sysprep is a tool that generalizes an image so that it can be used for deployment on other computers. Sysprep configures the computer to request a new security identifier (SID) and removes other customizations, causing the operating system to start the Out of Box Experience the next time it starts.
Sysprep prepares an image, after which you use DISM to capture the image appropriate for deployment. However, using Sysprep and DISM requires IT pro–level expertise and therefore isn’t appropriate for all environments.
Deployment Image Servicing and Management
DISM is a program that runs from the command line. Using DISM, you can capture an image of a hard disk partition, then customize the image in various ways, including adding or removing drivers and software packages and enabling or disabling Windows features.
Using DISM requires some experience in creating and managing images. If your organization doesn’t have prior deployment or image management experience, a tool like MDT will be more appropriate.
User State Migration Tool
The USMT helps with the migration of user accounts, data, and settings during an operating system upgrade. Using the USMT, an administrator migrates user state to an intermediary migration store. After the new operating system has been deployed, the administrator migrates the user state to the new operating system. The USMT migrates application settings, user documents, and the user profile and data by using XML-based rules that can be customized.
The Microsoft Deployment Toolkit
MDT is the recommended tool for automating Windows deployments. MDT provides a wizard-driven interface and requires little previous deployment experience. MDT also has low infrastructure-related requirements. A file server, typically already present in most organizations, is the only requirement for an MDT-based deployment. The file server can even be the same as the IT pro’s computer.
By itself, MDT can help you with Lite Touch Installation (LTI), discussed above. When combined with System Center Configuration Manager, MDT can also facilitate Zero Touch Installation (ZTI) deployments and User-Driven Installation (UDI). IT pros with little prior deployment experience can use MDT.
Behind the scenes, MDT uses command-line tools like DISM and Sysprep, which you learned about earlier. The obvious advantage to MDT is that it provides a graphical interface into those processes. Beyond the obvious, however, MDT places the extensive deployment experience built over years into a framework that IT can leverage for their projects.
System Center Configuration Manager
System Center 2012 R2 Configuration Manager is a powerful software package that helps IT deliver advanced management of infrastructure. When used with MDT, System Center 2012 R2 Configuration Manager provides a fully automated deployment environment (ZTI), including not only Windows but other software, as well. System Center 2012 R2 Configuration Manager enables Windows image capture and deployment onto computers through task sequences. Using task sequences, IT can fully customize the deployment process.
Using System Center 2012 R2 Configuration Manager and MDT together for deployments is appropriate for environments that have prior experience with deployments and need to perform ZTI or UDI deployments. Ideally, the environment would already have System Center Configuration Manager running within the infrastructure.