Skip to main content This browser is no longer supported. Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
In this articleTo successfully deploy the Windows 10 operating system and applications for your organization, understand the available tools to help with the process. In this article, you'll learn about the most commonly used tools for Windows 10 deployment. Microsoft provides many tools, services, and solutions. These tools include Windows Deployment Services (WDS), the Volume Activation Management Tool (VAMT), the User State Migration Tool (USMT), Windows System Image Manager (Windows SIM), Windows Preinstallation Environment (Windows PE), and Windows Recovery Environment (Windows RE). These tools aren't a complete solution on their own. Combine these tools with solutions like Configuration Manager to get a complete deployment solution. In this article, you also learn about different types of reference images that you can build, and why reference images are beneficial for most organizations Windows Assessment and Deployment KitWindows ADK contains core assessment and deployment tools and technologies, including Deployment Image Servicing and Management (DISM), Windows Imaging and Configuration Designer (Windows ICD), Windows System Image Manager (Windows SIM), User State Migration Tool (USMT), Volume Activation Management Tool (VAMT), Windows Preinstallation Environment (Windows PE), Windows Assessment Services, Windows Performance Toolkit (WPT), Application Compatibility Toolkit (ACT), and Microsoft SQL Server 2012 Express. For more information, see Windows ADK for Windows 10 or Windows ADK for Windows 10 scenarios for IT Pros. The Windows 10 ADK feature selection page. Deployment Image Servicing and Management (DISM)DISM is one of the deployment tools included in the Windows ADK and is used for capturing, servicing, and deploying boot images and operating system images. DISM services online and offline images. For example, with DISM you can install the Microsoft .NET Framework 3.5.1 in Windows 10 online, which means that you can start the installation in the running operating system, not that you get the software online. The /LimitAccess switch configures DISM to get the files only from a local source:
In Windows 10, you can use Windows PowerShell for many of the functions done by DISM.exe. The equivalent command in Windows 10 using PowerShell is:
Using DISM functions in PowerShell. For more information on DISM, see DISM technical reference. User State Migration Tool (USMT)USMT is a backup and restore tool that allows you to migrate user state, data, and settings from one installation to another. Microsoft Deployment Toolkit (MDT) and Configuration Manager use USMT as part of the operating system deployment process. USMT includes several command-line tools, the most important of which are ScanState and LoadState:
In addition to these tools, there are also XML templates that manage which data is migrated. You can customize the templates, or create new ones, to manage the backup process at a high level of detail. USMT uses the following terms for its templates:
A sample USMT migration file that will exclude .MP3 files on all local drives and include the folder C:\Data and all its files, including its subdirectories and their files. USMT supports capturing data and settings from Windows Vista and later, and restoring the data and settings to Windows 7 and later (including Windows 10 in both cases). It also supports migrating from a 32-bit operating system to a 64-bit operating system, but not the other way around. For example, you can use USMT to migrate from Windows 7 x86 to Windows 10 x64. By default USMT migrates many settings, most of which are related to the user profile but also to Control Panel configurations, file types, and more. The default templates that are used in Windows 10 deployments are MigUser.xml and MigApp.xml. These two default templates migrate the following data and settings:
These settings are migrated by the default MigUser.xml and MigApp.xml templates. For more information, see What does USMT migrate? For more general information on USMT, see USMT technical reference. Windows Imaging and Configuration DesignerWindows Imaging and Configuration Designer (Windows ICD) is a tool designed to assist with the creation of provisioning packages that can be used to dynamically configure a Windows device (PCs, tablets, and phones). This tool is useful for setting up new devices, without the need for reimaging the device with a custom image. Windows Imaging and Configuration Designer. For more information, see Windows Imaging and Configuration Designer. Windows System Image Manager (Windows SIM)Windows SIM is an authoring tool for Unattend.xml files. When using MDT and/or Configuration Manager, you don't need Windows SIM often because those systems automatically update the Unattend.xml file during the deployment, greatly simplifying the process overall. Windows answer file opened in Windows SIM. For more information, see Windows System Image Manager Technical Reference. Volume Activation Management Tool (VAMT)If you don't use KMS, manage your MAKs centrally with the Volume Activation Management Tool (VAMT). Use this tool to install and manage product keys throughout the organization. VAMT can also activate on behalf of clients without internet access, acting as a MAK proxy. The updated Volume Activation Management Tool. VAMT also can be used to create reports, switch from MAK to KMS, manage Active Directory-based activation, and manage Office 2010 and Office 2013 volume activation. VAMT also supports PowerShell (instead of the old command-line tool). For example, if you want to get information from the VAMT database, you can type:
For more information on the VAMT, see VAMT technical reference. Windows Preinstallation Environment (Windows PE)Windows PE is a "Lite" version of Windows 10 and was created to act as a deployment platform. Windows PE replaces the DOS or Linux boot disks that ruled the deployment solutions of the last decade. The key thing to know about Windows PE is that, like the operating system, it needs drivers for at least network and storage devices in each PC. Luckily Windows PE includes the same drivers as the full Windows 10 operating system, which means much of your hardware will work out of the box. A machine booted with the Windows ADK default Windows PE boot image. For more information on Windows PE, see Windows PE (WinPE). Windows Recovery EnvironmentWindows Recovery Environment (Windows RE) is a diagnostics and recovery toolset included in Windows Vista and later operating systems. The latest version of Windows RE is based on Windows PE. You can also extend Windows RE and add your own tools if needed. If a Windows installation fails to start and Windows RE is installed, you'll see an automatic failover into Windows RE. A Windows 10 client booted into Windows RE, showing Advanced options. For more information on Windows RE, see Windows Recovery Environment. Windows Deployment ServicesWindows Deployment Services (WDS) has been updated and improved in several ways starting with Windows 8. Remember that the two main functions you'll use are the PXE boot support and multicast. Most of the changes are related to management and increased performance. In Windows Server 2012 R2, WDS also can be used for the Network Unlock feature in BitLocker. Windows Deployment Services using multicast to deploy three machines. In Windows Server 2012 R2, Windows Deployment Services can be configured for stand-alone mode or for Active Directory integration. The Active Directory integration mode is the best option, in most scenarios. WDS also has the capability to manage drivers; however, driver management through MDT and Configuration Manager is more suitable for deployment due to the flexibility offered by both solutions, so you'll use them instead. In WDS, it's possible to pre-stage devices in Active Directory, but here, too, Configuration Manager has that capability built in, and MDT has the ability to use a SQL Server database for pre-staging. In most scenarios, those solutions are better than the built-in pre-staging function as they allow greater control and management. Trivial File Transfer Protocol (TFTP) configurationIn some cases, you need to modify TFTP Maximum Block Size settings for performance tuning reasons, especially when PXE traffic travels through routers and such. In the previous version of WDS, it was possible to change that, but the method of do so—editing the registry—wasn't user friendly. In Windows Server 2012, this modification in settings has become much easier to do as it can be configured as a setting. Also, there are a few new features related to TFTP performance:
TFTP changes are now easy to perform. MDT is a free deployment solution from Microsoft. It provides end-to-end guidance, best practices, and tools for planning, building, and deploying Windows operating systems. MDT builds on top of the core deployment tools in the Windows ADK by contributing guidance, reducing complexity, and adding critical features for an enterprise-ready deployment solution. MDT has two main parts: the first is Lite Touch, which is a stand-alone deployment solution; the second is Zero Touch, which is an extension to Configuration Manager. Note The Deployment Workbench in, showing a task sequence. For more information on MDT, see the Microsoft Deployment Toolkit resource center. Microsoft Security Compliance Manager 2013Microsoft SCM is a free utility used to create baseline security settings for the Windows client and server environment. The baselines can be exported and then deployed via Group Policy, local policies, MDT, or Configuration Manager. The current version of Security Compliance Manager includes baselines for Windows 8.1 and several earlier versions of Windows, Windows Server, and Internet Explorer. The SCM console showing a baseline configuration for a fictional client's computer security compliance. Microsoft Desktop Optimization PackMDOP is a suite of technologies available to Software Assurance customers through another subscription. The following components are included in the MDOP suite:
For more information on the benefits of an MDOP subscription, see Microsoft Desktop Optimization Pack. Windows Server Update ServicesWSUS is a server role in Windows Server 2012 R2 that enables you to maintain a local repository of Microsoft updates and then distribute them to machines on your network. WSUS offers approval control and reporting of update status in your environment. The Windows Server Update Services console. For more information on WSUS, see the Windows Server Update Services Overview. Unified Extensible Firmware InterfaceFor many years, BIOS has been the industry standard for booting a PC. BIOS has served us well, but it's time to replace it with something better. UEFI is the replacement for BIOS, so it's important to understand the differences between BIOS and UEFI. In this section, you learn the major differences between the two and how they affect operating system deployment. Introduction to UEFIBIOS has been in use for approximately 30 years. Even though it clearly has proven to work, it has some limitations, including:
As the replacement to BIOS, UEFI has many features that Windows can and will use. With UEFI, you can benefit from:
UEFI versionsUEFI Version 2.3.1B is the version required for Windows 8 and later logo compliance. Later versions have been released to address issues; a few machines may need to upgrade their firmware to fully support the UEFI implementation in Windows 8 and later. Hardware support for UEFIIn regard to UEFI, hardware is divided into four device classes:
Windows support for UEFIMicrosoft started with support for EFI 1.10 on servers and then added support for UEFI on both clients and servers. With UEFI 2.3.1, there are both x86 and x64 versions of UEFI. Windows 10 supports both. However, UEFI doesn't support cross-platform boot. This limitation means that a computer that has UEFI x64 can run only a 64-bit operating system, and a computer that has UEFI x86 can run only a 32-bit operating system. How UEFI is changing operating system deploymentThere are many things that affect operating system deployment as soon as you run on UEFI/EFI-based hardware. Here are considerations to keep in mind when working with UEFI devices:
For more information on UEFI, see the UEFI firmware overview and related resources. Related articlesSideload apps in Windows 10 FeedbackSubmit and view feedback for Additional resourcesWhat is the name of the area of the desktop that contains shortcuts of apps and services?The Quick Launch bar--contains shortcuts to commonly used applications. Use this to avoid cluttering up your desktop with application shortcuts. If you don't use it, you can remove it (see #2 below). The main Taskbar--displays icons for all open applications and files.
What is the term used for a set of programs that acts as an interface between an applications running on a computer and computer hardware?Operating System (OS) - a set of programs that manage computer hardware resources and provide common services for application software. The operating system acts as an interface between the hardware and the programs requesting I/O. It is the most fundamental of all system software programs.
What is the process of setting up the software to work with the computer and other hardware components?Installing software is the process of setting up software to work with a computer, printer, and other hardware. A computer is an electronic device that can accept data and process it according to specified rules, but that cannot produce information.
Which of the following refers to when you start your computer by turning the power on?This process is called booting up, and it can take anywhere from 15 seconds to several minutes. Once the computer has booted up, it may be ready to use, or it may require you to log in. This means identifying yourself by typing your user name or selecting your profile, then typing your password.
|