Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
programming4us
Windows 7

Understanding the Windows 7 Deployment Process (part 3) - Using Microsoft Deployment Toolkit 2010

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
9/19/2011 6:29:09 PM

6.2.4. Using Microsoft Deployment Toolkit 2010

Compared to Windows 7 AIK, which is a set of individual tools, MDT 2010 is more of a unified deployment environment. However, MDT 2010 is also a superset of Windows 7 AIK. You must install Windows 7 AIK along with MDT 2010, and the MDT procedures utilize the AIK tools.

At the highest level, the MDT deployment procedure is essentially the same as that with Windows 7 AIK. You create and configure a reference computer, capture an image from it, and then deploy the image to your target workstations. However, MDT 2010 streamlines the method by which you perform these tasks, thanks to the capabilities of the Deployment Workbench tool.

MDT 2010 supports two deployment models, the Lite-Touch Installation (LTI) and the Zero-Touch Installation (ZTI). As the names imply, an LTI deployment requires a minimal amount of user intervention at the workstation, while the ZTI requires none.

The basic steps in an MDT 2010 LTI workstation deployment are as follows:

  1. Create a build computer.

    As with Windows 7 AIK, you need a computer on which to install MDT 2010 and the other software it requires, including Windows 7 AIK.

  2. Create a deployment share.

    Using Deployment Workbench, you create a share, using the New Deployment Share Wizard shown in Figure 8. Unlike the distribution share created by Windows SIM, workstations can actually access image files from the MDT deployment share.

    Figure 8. The New Deployment Share Wizard in Deployment Workbench


  3. Populate the deployment share.

    Deployment Workbench enables you to add operating systems, applications, device drivers, and other software packages, which you can integrate into your installations. For a reference computer installation, you typically use the Install.wim image from a Windows 7 installation disk.

  4. Create a task sequence for the reference computer installation.

    The MDT task sequencer is responsible for performing the various steps in a Windows installation. When you create a task sequence in Deployment Workbench using the New Task Sequence Wizard shown in Figure 9, the wizard automatically creates an answer file that the Windows setup program uses to install the operating system. However, task sequences can also perform additional operations outside of the installation, including automatically capturing an image of the newly installed workstation.

    Figure 9. The New Task Sequence Wizard in Deployment Workbench

  5. Update the deployment share.

    When you update the deployment share in Deployment Workbench, using the Update Deployment Share Wizard shown in Figure 10, the wizard creates a boot image using the Windows PE files from the Windows 7 AIK. Unlike the Copype.cmd script from Windows 7 AIK, however, the wizard creates a customized boot image that enables the workstation to access the deployment share over the network.

    Figure 10. The Update Deployment Share Wizard in Deployment Workbench


  6. Deploy the boot image to the reference computer.

    MDT 2010 creates a customized boot image, but it cannot deploy this image to a workstation. However, because the Update Deployment Share Wizard creates the boot image in both file-based (with a .wim extension) and sector-based (with an .iso extension) formats, you can deploy the image to the reference computer by using WDS or by creating a boot disk.

  7. Install the reference computer.

    Starting the reference computer by using the boot image automatically connects the system to the deployment share and launches the Windows Deployment Wizard, as shown in Figure 11, from which you can select the task sequence you created earlier.

    Figure 11. The Windows Deployment Wizard on the reference computer


  8. Capture an image of the reference computer.

    You can configure a task sequence to automatically capture an image of the reference computer after it completes the Windows 7 installation and save it back to the build computer.

  9. Add the captured image to the deployment share.

    After capturing an image of your reference computer, you must add it to the deployment share, so that you can deploy it to your target workstations.

  10. Create a task sequence for the target computer installation.

    In an LTI deployment, the process of deploying your captured image to your target workstations is roughly the same as the reference computer deployment. When creating the task sequence for the target computer deployment, you select your captured reference computer image. You can also configure the task sequence to perform additional installation and configuration procedures on the target workstations.

  11. Deploy the reference computer image to the target computers.

    After creating the task sequence, you update the deployment share and deploy the resulting boot image using WDS or boot disks, just as you did earlier, but this time to the target computers.

A ZTI deployment differs primarily in that it uses System Center Configuration Manager to deploy the images to the workstations. This complicates the deployment process considerably, both in the infrastructure required and in the staging of the reference computer and target computer installations, but it enables administrators to deploy large numbers of workstations without any interaction at each workstation.

Other -----------------
- Understanding the Windows 7 Deployment Process (part 1) - Windows 7 Deployment Basics & Using Windows Deployment Services
- Configuring Backups and Recovery : Safeguarding Your Computer and Recovering from Disaster & Using Advanced Boot Options
- Microsoft Word 2010 : Sharing Information Between Programs - Exporting and Importing Data
- Microsoft Word 2010 : Playing a Movie Using an ActiveX Control & Changing the Document Information Panel
- Microsoft Visio 2010 : Understanding Relative and Absolute Hyperlinks
- Microsoft Visio 2010 : Linking to Another Visio Page
- Microsoft PowerPoint 2010 : Setting Privacy Options
- Microsoft PowerPoint 2010 : Setting Macro Security Options & Changing Message Bar Security Options
- Microsoft Excel 2010 : Displaying Parts of a Table with AutoFilter & Creating Custom Searches
- Microsoft Excel 2010 : Analyzing Worksheet Data - Sorting Data in a Table
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server