Choosing LTI, ZTI, or UDI Deployments

LTI, ZTI, and UDI deployments use the same common set of scripts and configuration files (such as CustomSettings.ini) for deploying target computers. Table 6 compares LTI, ZTI, and UDI deployments.

Table 6. Comparison of LTI, ZTI, and UDI Deployments

At some point in the MDT process, you must provide all the information necessary to install Windows and the applications on target computers. The question is, when do you provide this information? The more information you provide in advance, the less interaction is required during deployment.

Table 7lists the advantages and disadvantages of performing fully automated deployments (using LTI, ZTI, or UDI) and partially automated deployments (using LTI or UDI).

Table 7. Advantages and Disadvantages of Fully and Partially Automated Deployments

Method	Advantages	Disadvantages
Fully	· No interaction with the user or deployment technician is required. · The risk of introducing configuration errors is decreased. · Users or deployment technicians do not need to know any configuration information prior to initiating the MDT deployment process.	· More time is needed to provide configuration information required for fully automated deployment. · Credentials to access network resources and that have elevated permissions are stored in configuration files that must be protected.
Partially	· Less time is required to prepare for deployment, because configuration information can be provided interactively.	· Interaction with the user or deployment technician is required. · The risk of introducing configuration errors is increased. · Users or deployment technicians must have credentials that require elevated permissions. · Users or deployment technicians must know some configuration information prior to initiating the MDT deployment process.

Method

Advantages

Disadvantages

Fully

· No interaction with the user or deployment technician is required.

· The risk of introducing configuration errors is decreased.

· Users or deployment technicians do not need to know any configuration information prior to initiating the MDT deployment process.

· More time is needed to provide configuration information required for fully automated deployment.

· Credentials to access network resources and that have elevated permissions are stored in configuration files that must be protected.

Partially

· Less time is required to prepare for deployment, because configuration information can be provided interactively.

· Interaction with the user or deployment technician is required.

· The risk of introducing configuration errors is increased.

· Users or deployment technicians must have credentials that require elevated permissions.

· Users or deployment technicians must know some configuration information prior to initiating the MDT deployment process.

Related Topics

Planning MDT Deployments

LTI deployment	ZTI deployment	UDI deployment
Allows selection of the level of automation	Supports only fully automated deployments	Allows selection of the level of automation
Has minimal infrastructure requirements	Requires Configuration Manager 2012 or Configuration Manager 2007 R3	Requires Configuration Manager 2012 or Configuration Manager 2007 R3
Supports deployments over a network using a shared folder or locally using removable storage such as a CD, DVD, or UFD	Supports deployments over a network using Configuration Manager 2012 or Configuration Manager 2007 R3 distribution points or locally using removable storage such as a CD, DVD, or UFD	Supports deployments over a network using Configuration Manager 2012 or Configuration Manager 2007 R3 distribution points or locally using removable storage such as a CD, DVD, or UFD
The deployment process can be initiated manually or automatically using Windows Deployment Services	The installation process can be initiated by Configuration Manager 2012, Configuration Manager 2007 R3, or Windows Deployment Services	The installation process can be initiated by Configuration Manager 2012, Configuration Manager 2007 R3, or Windows Deployment Services
The deployment process is configured using the Deployment Workbench	The deployment process is configured using the Configuration Manager console in Configuration Manager 2012 or Configuration Manager 2007 R3	The deployment process is configured using the Configuration Manager console in Configuration Manager 2012 or Configuration Manager 2007 R3 and the UDI Wizard Designer.
Can require less initial IT administration configuration time	Requires more initial IT administration configuration time	Requires more initial IT administration configuration time
Can require interaction by the user or deployment technician	Requires no interaction by the user or deployment technician	Can require interaction by the user or deployment technician
Increases the risk of introducing configuration errors	Reduces the risk of introducing configuration errors	Increases the risk of introducing configuration errors
Requires users or deployment technicians to have credentials with elevated permissions	Users and deployment technicians are not required to have credentials with elevated permissions	Requires users or deployment technicians to have credentials with elevated permissions
Requires that users or deployment technicians know some configuration settings prior to initiating the MDT deployment process	Users and deployment technicians do not need to know configuration settings prior to initiating the MDT deployment process	Requires that users or deployment technicians know some configuration settings prior to initiating the MDT deployment process
Can be used with slow connections or in instances where no network connectivity exists	Requires a high-speed, persistent connection	Requires a high-speed, persistent connection
Requires little or no infrastructure to support deployment	Requires an infrastructure sufficient to deploy operating system images	Requires an infrastructure sufficient to deploy operating system images
Supports deployment over the network or local to the computer from media	Supports deployment over the network or local to the computer from media	Supports deployment over the network or local to the computer from media
Does not require management of target computers using Configuration Manager 2012 or Configuration Manager 2007 R3	Requires that target computers be managed using Configuration Manager 2012 or Configuration Manager 2007 R3	Requires that target computers be managed using Configuration Manager 2012 or Configuration Manager 2007 R3
Supports security policies in which automatic software installation is prohibited	Supports only security in which automatic software installation is allowed.	Supports only security in which automatic software installation is allowed.
Supports deployment to target computers isolated by firewalls	Requires remote procedure call (RPC) communication with target computers	Requires RPC communication with target computers