Deploying Windows 7 Using MDT UDI...Once you have the TS ready, you have an option to customize the...

Preview:

Citation preview

The Microsoft Deployment Toolkit (MDT) supports three types of deployments Zero Touch Installation (ZTI), Lite Touch

Installation (LTI), and User Driven Installation (UDI). However each deployment type is different. LTI deployments require

limited user interaction. ZTI is a fully automated deployment scheme in which installation requires no user interaction

whatsoever. UDI deployments require full manual intervention to respond to every installation prompt, such as machine

name, password or language setting. ZTI and UDI deployments both require a Microsoft System Center infrastructure. User

Driven Installation helps simplify the deployment of Windows client operating systems, such as Windows 7, 8.1, to

computers using the operating system deployment (OSD) feature in Microsoft System Center 2012 R2 Configuration

Manager. UDI is part of the Microsoft Deployment Toolkit (MDT). Basically UDI provides a wizard-driven interface that

allows you to provide configuration information immediately prior to performing the deployment. User Driven Installation

would provide your organization with a highly customizable deployment method that allows deployment choices to be

done by the user and also provides greater flexibility in the deployment process. In this post we will see the steps for

deploying Windows 7 using MDT UDI method. Before we do that the MDT has to be integrated with SCCM.

Deploying Windows 7 Using MDT UDIIn the Configuration Manager console, in the navigation pane, click Software Library. In the Software Library workspace,

go to Overview > Operating Systems > Task Sequences. On the Ribbon, on the Home tab, in the Task Sequences

group, click Create MDT Task Sequence.

You could choose to join the computer to workgroup or to the domain. In this case we will be joining the PC to the

domain, so provide the Domain name, User Name, Organization Name. Click Next.

Click This task sequence will never be used to capture and image. Click Next.

Click on Browse and specify the boot image. Click Next.

Click Create a new Microsoft Deployment Toolkit Files package. Provide a shared folder path where the MDT files

package should be stored. Click Next.

Click Specify an existing OS image, click Browse and select the desired OS Image. If you are unable to find OS image

then ensure that you have added the OS image in the Configuration Manager and distributed it to DP’s. Click Next.

Choose the OS edition that you want to install. Click Next.

Choose Perform a “User-driven Installation”. Click Next.

Click Browse and specify ConfigMgr client package. Click Next.

Click Browse and specify an existing USMT package. Click Next.

Click Create a new settings package. Provide a path where the settings should be stored. Click Next.

Provide some details such as name to settings package. Click Next.

To edit the TS, right-click the TS and click Edit. This will open the Task Sequence Editor. In the below screenshot, I have

added the applications to be installed after OS is installed. You can add more apps if required. Click OK.

Once you have the TS ready, you have an option to customize the UDI wizard. The UDI Wizard pages are customizable

and this can be done with a utility called UDI Wizard Designer. I have not included those steps here, check this link to

customize the UDI Wizard pages. After you do this step, you need to update the MDT files and settings package to the

distribution points.

To deploy the TS, right click on the TS and click Deploy. Click on Browse and choose the collection as All Unknown

Computers.

Set the purpose as Available and make the TS available to “Only media and PXE“. Click Next.

Now boot the machine and allow it to boot from the network. Press F12 key to start the network service boot.

Choose the OS, Target Drive and chcek the box partition and format disk 0. Click Next.

Provide few details such as Computer name, select domain, OU and domain join credentials. Click Next.

A screenshot where we see that ConfigMgr agent is being installed.

Nice to see newly imaged computer with applications installed on it :).

Recommended