Microsoft Deployment Toolkit
Template:Short description Script error: No such module "Unsubst". Script error: No such module "Infobox".Template:Template other Script error: No such module "Check for unknown parameters".Script error: No such module "Check for conflicting parameters".
Microsoft Deployment Toolkit (MDT; originally released as Business Desktop Deployment in August 2003[1][2]) is a free software package from Microsoft for automating the deployment of Windows 10, Server 2019 and older Windows Server and desktop operating systems.[3]
Overview
MDT can help build an automated installation source for deploying Windows operating systems from Windows 7, Windows 10 and Windows Server 2008 onwards, from either a single machine or a central server distribution tool, such as Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM).[4] Device drivers, Windows updates and software can be included with the build.[5][4]
All the software intended for installation (Operating System, drivers, updates and applications) are added to a pool of available software and packaged into deployment packages.[6] The Operating System and drivers to be included with this package are selected, and the administrator password, owner information, and product key are specified.[4][6][7] Microsoft Deployment Toolkit generates a custom Windows PE (Preinstallation Environment) image that allows client machines to install the assembled deployment packages over the network from the MDT server.[6][7] This Windows PE disk image can be burned to and booted from a CD, or booted with Windows Deployment Services. When selecting the package to deploy, software that has been included in the pool may also be selected for installation.[4]
Operation
The Microsoft Deployment Toolkit (MDT) supports three types of deployments:[4] Zero Touch Installation (ZTI), Lite Touch Installation (LTI), and User Driven Installation (UDI). ZTI is a fully automated deployment scheme in which installation requires no user interaction whatsoever.[7] UDI deployments require full manual intervention to respond to every installation prompt, such as machine name, password or language setting.[8] ZTI and UDI deployments both require a Microsoft System Center infrastructure.[4] ZTI deployments require a persistent network connection to the distribution point.[7] LTI deployments require limited user interaction. An LTI deployment needs very little infrastructure, so it can be installed from a network share, or media using either a USB flash drive or an optical disc.[6]
See also
- Remote Installation Services
- Microsoft Configuration Manager (formerly known as Microsoft Endpoint Configuration Manager (MECM), System Center Configuration Manager (SCCM) or SMS)
- User State Migration Tool
- Windows Assessment and Deployment Kit (ADK) (previously known as Windows Automated Installation Kit)
- Windows Deployment Services
- Windows Preinstallation Environment (Windows PE)
References
<templatestyles src="Reflist/styles.css" />
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ a b c d e f Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ a b c d Script error: No such module "citation/CS1".
- ↑ a b c d Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
Script error: No such module "Check for unknown parameters".
External links
- Script error: No such module "Official website".Script error: No such module "Check for unknown parameters".
Script error: No such module "Navbox".