Wednesday, August 7, 2013

14 # Comparison between LTI, ZTI, and UDI Deployments strategies:


Comparison between LTI, ZTI, and UDI Deployments strategies:
 
This post is for you to get to know the different types of OS deployment strategies, their requirements and will help you understand which strategy suits the best with the resources available with you.
 
SCCM 2007/2012 supports the following types Operating System deployment strategies,

  1. LTI – Light Touch Installation
  2. ZTI – Zero Touch Installation
  3. UDI – User Driven Installation

There is one more type called HTI – High Touch Installation which is carried out by using Retail Media (Installation DVD) and/or Standard Image. The way we used to install Operating System earlier, carrying CD/DVDs around.
 

 

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 only from Configuration Manager 2012 or Configuration Manager 2007 R3 distribution points

Supports deployments only from Configuration Manager 2012 or Configuration Manager 2007 R3 distribution points

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 only network deployments

Supports only network deployments

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
 

 
 
At some point in the process of Operating System Deployment, 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.