Deploying Windows 7 - Part 6: Lite Touch using MDT 2. If you would like to read previous articles in this series, please go to: Introduction. In the previous article of this series we examined the new features of MDT 2. Microsoft Deployment Toolkit. We also looked at how to install MDT 2. Deployment Workbench. In this article we will examine how to manually perform a basic Lite Touch Installation (LTI) deployment of Windows 7 Enterprise using MDT 2. The tasks we are going to perform include: Preparing the environment. Albuquerque and New Mexico's trusted news source. Statewide weather forecasts, live streaming, investigations, entertainment, local events and living. Creating a deployment share. Configuring the deployment share. Creating a task sequence. Updating the deployment share. Performing the install. Before you continue reading, you may want to refer back to the following two articles from my previous series Deploying Vista: Preparing the Environment. To follow along through this walkthrough, make sure you have the following environment (or something similar) set up: Domain controller for the contoso. DHCP server with a scope configured for leasing addresses to client computers. Technician computer with MDT 2. Windows AIK 2. 0 installed. In my own test environment, one computer running Windows Server 2. R2 Enterprise x. 64 fulfills all of these roles. Creating a Deployment Share. Open the Deployment Workbench on your technician computer, then right- click on the Deployment Shares node and select New Deployment Share. The New Deployment Share wizard starts. Click the Browse button and create a folder named Deployment. Summary of all Single and Multifunction Printers currently available for purchase. Includes links to compare products, obtain more information about a specific model. Outlook.com is a free, personal email service from Microsoft. Keep your inbox clutter-free with powerful organizational tools, and collaborate easily with OneDrive. Home > Support > Search. How to install TrueType fonts in Windows. TrueType TTF Fonts are commonly used in Windows and Mac operating systems. TrueType barcode fonts. Share$ in the root of your disk volume as shown in Figure 1: Figure 1: Specify the name and path to the deployment share folder. Click Next and the share name will automatically be populated and the UNC path to the share will be displayed (Figure 2): Figure 2: The share name and UNC path for the deployment share are displayed Click Next and give your deployment share a descriptive name (Figure 3): Figure 3: Name the deployment share. Click Next and choose whether you want to be able to capture an image after deploying it to a computer (Figure 4). We will leave this option enabled so we can use it if we deploy a reference (master) computer and capture its image for deployment onto multiple target (end- user) computers: Figure 4: Specify whether the option to capture an image will be displayed when the Windows Deployment Wizard runs during an install. Click Next and specify whether the user should be allowed to set the password for the local Administrator account on their computer (Figure 5). We’ll leave this option unchecked: Figure 5: The Allow Admin Password option. Click Next and specify whether the user should be asked to enter a product key (Figure 6).
We will leave this unchecked because we are deploying Windows 7 Enterprise, which means that activation is typically performed using Key Management Service (KMS): Figure 6: Choose whether the user is prompted to enter a product key during the install. Now finish the wizard and review the Confirmation page to ensure everything was done as expected. Figure 7 shows the newly created deployment share and its folder structure in the Deployment Workbench: Figure 7: The newly created deployment share Configuring the Deployment Share. Once you have created your deployment share, you need to configure it as follows: Add the operating system you wish to deploy. Add any out- of- box device drivers needed for installing the operating system on the target computers. Add any applications you want to install on the target computers during the install. Add any packages such as hotfixes or security updates you want to install on the target computers during the install. For simplicity we are only going to add an operating system (Windows 7 Enterprise) to the deployment share. In future articles we will examine how to add drivers, packages and applications to deployment shares. To add an operating system, right- click on the Operating Systems node in the deployment share and select Import Operating System. This starts the Import Operating System Wizard. On the first page of the wizard, specify that you want to import a full set of source files (Figure 8): Figure 8: Importing a full set of Windows 7 operating system files into the deployment share. Insert your Windows 7 Enterprise product media into the DVD drive of your technician computer and browse to select the DVD (Figure 9): Figure 9: Importing the OS source files from the product DVDClick Next and the wizard skips ahead to the Destination page (Figure 1. Specify a descriptive name for the folder where the source files will be imported to on your technician computer (note that I have imported the x. OS in this example): Figure 1. Specify the name of the folder where the OS source files will be imported to. Finish the wizard. The import process may take several minutes to complete. Once it is done and you select the Operating Systems folder in your deployment share, the imported OS is displayed (Figure 1. Figure 1. 1: Windows 7 Enterprise source files have been imported into the deployment share. At this point you would add out- of- box drivers, packages and applications to your deployment share as needed. Creating a Task Sequence. Now let us create a task sequence. A task sequence is a series of steps that are performed during deployment. We want to create a task sequence that will install Windows 7 Enterprise onto a bare- metal target computer. To do this, right- click on the Task Sequences folder in your deployment share and select New Task Sequence. This launches the New Task Sequence Wizard. On the first page of the wizard, specify a task sequence ID (no spaces), task sequence name, and comments as desired (Figure 1. Figure 1. 2: Creating a new task sequence for deploying Windows 7. Click Next and select Standard Client Task Sequence from the list of available task sequence templates (Figure 1. Figure 1. 3: Base the new task sequence on the Standard Client template Click Next and select Windows 7 Enterprise, which is the only imported OS at this point (Figure 1. Figure 1. 4: Select an operating system to deploy using the task sequence. Click Next and select the option to not specify a product key in the task sequence (Figure 1. Figure 1. 5: Do not specify a product key in the task sequence when deploying volume- licensed media and using KMS activation. Click Next and specify the name of the user who will be using the computer and your organization name and website/internet (Figure 1. Figure 1. 6: The OS Settings wizard page Click Next and specify a password for the local Administrator account on the target computer (Figure 1. Figure 1. 7: Specify a password for the local Administrator account on the user’s computer. Finish the wizard. The new task sequence is displayed in the Task Sequences folder of your deployment point (Figure 1. Figure 1. 8: The new task sequence is displayed in the Deployment Workbench. Updating the Deployment Share. Now we need to update our deployment share. Updating a deployment share does several things, one of which being the creation of customized version of the Windows Preinstallation Environment (Windows PE) that can be used to deploy the operating system using the task sequence. Specifically, updating the deployment share in this example creates the following Windows PE images in the C: \Deployment. Share$\Boot folder on your technician computer: Lite. Touch. PE. This launches the Update Deployment Share Wizard (Figure 1. Figure 1. 9: Updating the deployment share. Leave the default options selected and finish the wizard. It may take some time to create the Windows PE images on your technician computer. Once the wizard finishes, burn the Lite. Touch. PE. Note: As shown in Figure 2. Confirmation page of this wizard (and on all MDT 2. Save Output – saves the output of the wizard to a text file (actually it’s better to save it as . View Script – displays the underlying Windows Power. Shell commands that are executed by the wizard. As an example of the second, the View Script output from the Update Deployment Share Wizard looks like this: Add- PSSnap. In Microsoft. BDD. PSSnap. In. New- PSDrive - Name “DS0. PSProvider MDTProvider - Root “C: \Deployment. Share$”update- MDTDeployment. Share - path “DS0. Verbose. Figure 2. Confirmation page of the wizard Performing the Install. At this point, you are ready to deploy Windows 7 using MDT. Turn on your bare- metal (i. After a short time the Windows Deployment Wizard will start and you can follow the prompts almost exactly as shown in my earlier article Deploying Vista Part 2. Deploying Vista Using Microsoft Deployment Toolkit. The differences between what you will see when you do this using MDT 2. MDT 2. 00. 8 are basically only cosmetic in nature. If you would like to be notified when Mitch Tulloch releases the next part of this article series please sign up to the Windows. Networking. com Real time article update newsletter. If you would like to read previous articles in this series, please go to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
October 2017
Categories |