STEPSInstall WAIKRun the .MSI setup file to install WAIK. From an Internet-connected computer, you can download WAIK from the following Microsoft website:The Window Automated Installation Kit (WAIK) for Windows 7Although you do not interact directly with WAIK, the configurations and actions you make in MDT (Deployment Workbench) are automatically converted and run as WAIK commands.1.    Locate the WAIK setup file that you downloaded.2.    Copy it to the virtual deployment server.3.    Logon to the virtual deployment server.4.    Locate the WAIK setup file that you copied from step 2 above.5.    Double-click the wAIKX86.msi file (or the wAIKAMD64.msi file for 64-bit computers).6.    On the Welcome to the Windows AIK Setup Wizard page, click Next.7.    On the License Agreement page, select I accept and then click Next.8.    On the Select Installation Folder page, click Next to install to the default installation folder for anyone who uses the computer.9.    On the Confirm Installation page, click Next to begin installation.10.    Click Close to finish installation. 2.    Install Microsoft Deployment Toolkit 2010The Microsoft Deployment Toolkit (MDT) 2010 is the recommended process and toolset for automating desktop and server deployments. Specifically, it includes the Deployment Workbench for defining new deployment projects (or shares), adding custom applications, and generating remote image installation boot files for client computers. Since this PoC Jumpstart is already configured for you (MDT is installed), just review the information below and move to the next section.NOTE: The MDT steps below are necessary only if you are testing deployment outside the PoC environment. MDT has already been installed and included in the PoC Jumpstart.  STEPSInstall MDT 2010Run the .MSI setup file to install MDT. From an Internet-connected computer. You can download MDT from the following Microsoft Web site:Download MDT 2010You can install and run MDT 2010 on the following Windows versions:•    Windows Vista SP1 and SP2•    Windows 7•    Windows Server 2003 R2•    Windows Server 2008 and R21.    Locate the MDT setup file that you downloaded.2.    Copy it to the virtual deployment server.3.    Logon to the virtual deployment server.4.    Locate the MDT setup file that you copied from step 2 above.5.    Double-click the MicrosoftDeploymentToolkit2010_x86.msi file (or the MicrosoftDeploymentToolkit2010_x64.msi file for 64-bit computers).6.    On the Welcome to the Microsoft Deployment Toolkit 2010 Setup Wizard page, click Next.7.    On the End-User License Agreement page, select I accept and then click Next.8.    On the Custom Setup page, click Next.9.    On the Ready to Install page, click Install.10.    On the Completing the Microsoft Deployment Toolkit 2010 Setup Wizard page, click Finish.STEPSEXAMPLESStart the Deployment Workbench Start the Deployment Workbench.1.    Click Start, click All Programs, click Microsoft Deployment Toolkit and then click Deployment Workbench.      3.    Import an Operating SystemAfter installing Microsoft Deployment Toolkit (MDT) 2010 and starting the Deployment Workbench, one of the first steps in customizing your image deployment is to import an operating system. This PoC Jumpstart includes an Evaluation edition of Windows 7 Enterprise, which has already been imported as the operating system for the base image. In the steps below, you explore the properties and parameters of the imported operating system.STEPS    EXAMPLESCreate a Deployment Share  NOTE: This step is necessary only if you are testing deployment outside the PoC environment. The PoC Jumpstart has already been configured for a deployment share named MDT drive. In subsequent steps, you can simply refer to the preconfigured deployment share instead of creating and configuring your own.You can create a deployment share in Deployment Workbench without affecting the preconfigured deployment share. These steps help you become familiar with the various options, properties, and features available in Deployment Workbench.To simplify and speed up share creation, the default selections in the wizard apply to most computing scenarios. You just need to review the information and click Next.1.    In Deployment Workbench, in the left pane (treeview), right-click Deployment Shares and then click New Deployment Share.The New Deployment Share Wizard starts.2.    On the Path page, accept the default network location for the deployment share and then click Next.3.    On the Share page, accept the default name for the share and then click Next.4.    On the Descriptive Name page, type a description for the share and then click Next.5.    On the Allow Image Capture page, click Next.6.    On the Allow Admin Password page, click Next.7.    On the Allow Product Key page, click Next.8.    On the Summary page, review the deployment share details and then click Next.The Progress page displays the deployment share creation status.9.    On the Confirmation page, click Finish.       STEPS    EXAMPLESStart the Import Operating System Wizard MDT Deployment Workbench includes the Import Operating System Wizard to simplify the complexities behind the operating system import process.1.    In Deployment Workbench, expand Deployment Shares, expand MDT drive, right-click Operating Systems and then click Import Operating System.The Import Operating System Wizard starts. STEPS    EXAMPLESAdd an Operating SystemYou can add an operating system by browsing to a CD/DVD drive that contains the installation media, or to a local folder containing the installation files. For this PoC Jumpstart, you reference the Windows 7 Evaluation .ISO file that is included in the Jumpstart VHD.After the wizard completes, the operating system is imported into Deployment Workbench and is available as an image component. You repeat similar steps in the next section(s) to import and add applications, drivers, updates, and components to Deployment Workbench. Once imported, these software applications become image building blocks. You create and configure task sequences to specify how these blocks will be installed (installation parameters) and in what order during image deployment.1.    On the OS Type page, select Full set of source files and then click Next.2.    On the Source page, click Browse.3.    In the Browse For Folder dialog box, navigate to the location of the installation files (for example, the CD/DVD drive) and then click OK.This PoC Jumpstart includes an Evaluation edition of Windows 7 Enterprise in the following folder:C:\Win7Dep\Operating Systems\Windows 7 Enterprise 86 - Eval4.    On the Source page, click Next.5.    On the Destination page, type a name for the destination directory (such as Windows 7 x86 Eval) and then click Next.6.    On the Summary page, review the operating system import details and then click Next.The Progress page displays the operating system import status.7.    On the Confirmation page, click Finish.    4.    Create a New ApplicationBefore you can add application installation sequences to the image deployment process, you must first import the application(s) into the Deployment Workbench in Microsoft Deployment Toolkit (MDT) 2010.STEPS    EXAMPLES Start the New Application Wizard In this section, you create a new sample application in MDT. For this example, we add the Microsoft XML Notepad application.Later, you will create a task sequence that includes this application in image deployment.1.    Click Start > All Programs > Microsoft Deployment Toolkit > Deployment Workbench.2.    In Deployment Workbench, expand Deployment Shares, expand MDT drive, right-click Applications and then click New Application.      STEPS    EXAMPLESSpecify Application ParametersThis PoC Jumpstart includes the Microsoft XML Notepad sample application in the C:\DemoAPPs\XMLnotepad folder. To import and add the application to Deployment Workbench, specify the application source file location.As the New Application Wizard completes, the XML Notepad application is imported into Deployment Workbench. It is now available for inclusion in image deployment.1.    On the Application Type page, select Application with source files and then click Next.2.    On the Details page, type a name for the application (and complete the other fields as appropriate) and then click Next.3.    On the Source page, click Browse.4.    In the Browse For Folder dialog box, navigate to the C:\DemoAPPs\XMLnotepad folder and then click OK.5.    On the Source page, click Next.6.    On the Destination page, type a name for the application directory and then click Next. For the PoC, enter Microsoft XML Notepad.7.    On the Command Details page, in the Command line box, type the following command:msiexec /i XmlNotepad.msi /qb8.    Accept the default entry in the Working directory box and then click Next.9.    On the Summary page, review the application details and then click Next.10.    On the Confirmation page, click Finish.    STEPS    EXAMPLESValidate Application Creation After the New Application Wizard completes, open Deployment Workbench and make sure that XML Notepad appears properly in Applications.1.    In Deployment Workbench, expand Deployment Shares, expand MDT drive and then click Applications.2.    In the right pane, verify Microsoft XML Notepad appears in the list of applications.     Review PoC Core Applications The PoC deployment server has been delivered with a standard set of applications already configured for standard core image deployment.  The following highlightes these applications which will be included in the core image.3.    In Deployment Workbench, expand Deployment Shares, expand MDT drive, expand Applications, select Core Image. In the right pane, review the preconfigured core applications:•    Microsoft Security Essentials•    Microsoft Silver Light•    Microsoft Word Interactive GuideThese applications will be offered for deployment during deployment.     Review Task Sequence Applications The PoC deployment server has been delivered with a standard set of applications already configured for deployment based on the selected task sequence.  The following highlightes these applications which will be offered in the task sequences4.    In Deployment Workbench, expand Deployment Shares, expand MDT drive, expand Applications, expand Core Image, select Installation. In the right pane, review the preconfigured installation applications:•    Microsoft App-V Client•    Microsoft Office 2010 App-V Kit•    Microsoft Office 2010 Pro Plus•    Microsoft Office 2010 Pro Plus VirtualizedThese applications will be offered for deployment during deployment based on the selected task sequence.      5.    Customize the Office InstallationThe PoC has pre-configured Office 2010 for installation in the MDT.  We can leverage the integration of the MDT toolkit with the Office Customization Tool to fine tune the settings for the Office applications.  Note that this customization can only be applied to the on metal installation, the pre-sequenced Office 2010 application can’t be changed with the OCT tool as we have capture the installation details into the App-V package.STEPSEXAMPLESCustomizing an Office InstallationThis PoC Jumpstart includes the installation package for Office Professional Plus 2010. The Office application suite provides its own installation customization options which are the Office Customization Tool (OCT) and Config.xml tools.MDT offers tight integration with the Office setup once it is defined as an application for installation. In this lab we review the steps to customize the Office installation and link from MDT to the OCT tool.1.    In Deployment Workbench, expand Deployment Shares, expand MDT drive, expand Applications, expand Core Image and then click Installation.2.    In the right pane, select INSTALL - Microsoft Office 2010.3.    In Actions pane INSTALL – Microsoft Office 2010 section click Properties.4.    Select the Office Products tab in the properties window.5.    Click the Office Customization Tool button launching the Office tool. Note: The Office config.xml file can be directly launched from this same location for further customization (not covered in this lab).6.    Note the location indicated in the information dialog box indicating the location to save the MSP file generated by OCT.  Click OK to continue and launch OCT.7.    We have already generated an initial customization package to define the evaluation key.  In the select product dialog, select the option to Open an existing Setup customization file. Select the PoCJumpstart.msp file from c:\win7dep\applications\install – Microsoft office 2010\updates.The product customization data is loaded and click OK.  Note that a new installation would not have an existing customization file to edit.8.    In the Microsoft Office Customization Tool navigation window, select Install location and organization name.Enter the field Organization name and enter your company name.9.    In the Microsoft Office Customization Tool navigation window, select Licensing and user interface.10.    Review the following configurations: Enter another product keyProduct key has been entered (do not change – eval key has been provisioned for the PoC Jumpstart kit)Selected I accept the terms in the License Agreement.11.    In the same dialog box, select the display level as Basic, and select Completion notice and No Cancel check boxes.     STEPSEXAMPLES12.    In the Microsoft Office Customization Tool navigation window, select Office security settings.13.    Click the Add button next the Trusted Locations list.14.    Select the application Microsoft Word, enter the path \\POCServer\content, select the Subfolders of this location are also trusted checkbox and enter a description of PoC Jumpstart example. Click OK to enter your changes.15.    In the Microsoft Office Customization Tool navigation window, select Modify user settings.16.    Expand the following path in the application tree: Microsoft Excel 2010  Excel Options  Save. Double-click Save AutoRecover info.17.    Select the Enabled option for the Save AutoRecover info setting and then click OK.18.    Double-click the AutoRecover time setting.19.    Select the Enabled option and adjust the time to 5 minutes.  Click OK.20.    In the Microsoft Office Customization Tool navigation window, select Set feature installation states.21.    Navigate in the feature tree to Microsoft Office  Office Tools  Equation Editor. Click the selection options and select Installed on First Use.22.    Complete the customization by selecting the File Save.  This saves the existing MSP package in the updates folder.23.    You are now finished with the custom Office installation. Close the OCT by selecting FileExit, acknowledging the exit prompt.6.    Import Drivers, Updates, and Package a New ApplicationNow that you have imported an operating system and application into the Deployment Workbench, you can add other drivers, updates and packages to Deployment Workbench in preparation for image deployment. The drivers, updates and packages that you import in this section become available as building blocks for configuring task sequences and image deployment.In the next module, you run the Windows Deployment Wizard to deploy the image. This wizard provides several pages where you specify the applications, drivers, updates, packages and other components that you want to install after the base image. The components that you import in this section populate the options in the wizard.STEPS    EXAMPLESImport DriversMany organizations issue standard hardware and devices to employees. Therefore, it makes sense to install only the standard device drivers with the image deployment.In this section, you import into Deployment Workbench the drivers, updates and packages that you want to include with the image deployment.You can view the drivers that were imported and preconfigured for this PoC Jumpstart in the Deployment Workbench under the \Deployment Shares\MDT drive\Out-of-Box Drivers node.1.    In Deployment Workbench, expand Deployment Shares, expand MDT drive, right-click Out-of-Box Drivers and then click Import Drivers.The Import Driver Wizard starts.2.    On the Specify Directory page, click Browse.3.    In the Browse For Folder dialog box, navigate to the C:\Win7Dep\Out-of-Box Drivers\SCSIAdapter folder, click any folder under SCSIAdapter and then click OK.4.    On the Specify Directory page, click Next.5.    On the Summary page, review the driver import details and then click Next.6.    On the Confirmation page, click Finish.      STEPS    EXAMPLESValidate Driver AdditionFollow these steps to verify that the driver was imported properly into Deployment Workbench.1.    In Deployment Workbench, expand Deployment Shares, expand MDT drive and then click Out-of-Box Drivers.2.    In the right pane, verify that an entry appears in the list for the SCSIAdapter that you imported in the previous section.     Import UpdatesIn many cases, image deployment can be streamlined significantly by including Windows updates with image deployment (instead of having each user or client install each update manually).You can view the updates that were imported and preconfigured for this PoC Jumpstart in the \Deployment Shares\MDT drive\Packages\OS Patches folder.1.    In Deployment Workbench, expand Deployment Shares, expand MDT drive, right-click Packages and then click Import OS Packages.The Import Package Wizard starts.2.    On the Specify Directory page, click Browse.3.    In the Browse For Folder dialog box, select the following folder:C:\Win7Dep\Packages\Update\amd64_Package_for_KB974431_6.1.1.5_*4.    Click OK.5.    On the Specify Directory page, click Next.6.    On the Summary page, review the import update details and then click Next.7.    On the Confirmation page, click Finish.    STEPSEXAMPLESValidate Update AdditionFollow these steps to verify that the update was imported properly into Deployment Workbench.1.    In Deployment Workbench, expand Deployment Shares, expand MDT drive, expand Packages, expand OS Patches and then click Windows 7 – x32.In the right pane, verify that an entry appears in the list for the KB974431 Update that you imported in the previous section.     Import  PackagesYou can import other operating system-related packages into Deployment Workbench for later inclusion in the image deployment. These packages typically include language packs, custom components and other software packages.1.    Repeat the steps in the previous section to import packages.Important: You must provide the location of the package and specify a destination directory for Deployment Workbench.    7.    Configure Task Sequences for DeploymentAfter you import the image components (operating system, applications, drivers, updates, packages and other components) into Deployment Workbench, you are ready to configure task sequences for image deployment. You specify the sequence and parameters in which to install the image components when you configure a task sequence, which references the image components that you imported in the previous section(s).STEPS    EXAMPLESOpen a Preconfigured Task SequenceBecause the process of creating and configuring task sequences can be complicated and time-consuming, this PoC Jumpstart comes preconfigured with two task sequences:•    One task sequence that deploys an image of Windows 7 plus Virtual Office 2010•    One task sequence that deploys an image of Windows 7 plus a standard installation Office 2010In this exercise, you open a preconfigured task sequence and explore its properties.1.    In Deployment Workbench, expand Deployment Shares, expand MDT drive and then click Task Sequences.2.    In the right pane, right-click Deploy – Windows 7 – Master Image plus Office 2010 x86 and then click Properties.3.    In the Deploy – Windows 7 – Master Image plus Office 2010 x86 Properties dialog box, on the Task Sequence tab, click through the treeview to see the various options and properties for this task sequence.4.    Most notably, click and view the options for the following task sequence nodes:•    Install > Install Operating System•    State Restore > Windows Update•    State Restore > Install Application•    State Restore > Install Applications•    State Restore > Enable BitLocker     8.    Configure Deployment Share PropertiesThe Microsoft Deployment Toolkit (MDT) 2010 configures client computers based on properties, settings, parameters and rules that you specify. These deployment share properties give you more granular control over image deployment, where you can specify boot options and rules.STEPS    EXAMPLESExplore Deployment Share PropertiesOn the General tab of the MDT drive Properties dialog box, note how the folder specified in the Local path box resembles the folder structure in Deployment Workbench (open C:\Win7Dep in Windows Explorer). This design was configured for the PoC Jumpstart.1.    In Deployment Workbench, expand Deployment Shares, right-click MDT drive and then click Properties.2.    In the MDT drive Properties dialog box, on the General tab, review the general options for this deployment share.3.    Note the Local path box and the check box for Enable multicast for this deployment share.Multicast enables image deployment to multiple client computers simultaneously. Otherwise, in unicast mode (if the option is not selected), only one client at a time can stream image installation remotely from the server.     Explore the Windows PE SettingsThe Windows Pre-installation Environment (PE) settings let you specify the boot options for client computers. All of the component import and task sequence configurations are summarized in this output (.WIM and/or .ISO) file.Client computers use this output to boot up and install the image and components remotely from the server.1.    In the MDT drive Properties dialog box, on the Windows PE x86 Settings tab, review the Windows PE x86 settings options.Note that the Lite Touch Boot Image Settings are configured to generate a .WIM file and an .ISO file.2.    Repeat the previous step to view the Windows PE x64 Settings tab.     STEPS    EXAMPLESExplore the Windows PE ComponentsThe properties for Windows Pre-installation Environment (PE) components provide options to include and exclude certain drivers and packages based on various categories such as the driver type (network, storage, video, and system) and language fonts.1.    In the MDT drive Properties dialog box, on the Windows PE x86 Components tab, review the Windows PE x86 components options.Note that you can include and exclude drivers and packages based on specific profiles and categories.2.    Repeat the previous step to view the Windows PE x64 Components tab.     Explore Deployment Share RulesRules let you configure global or group-based settings such as the time zone, domain name, Administrator account and administrative password to be set on each client computer.1.    In the MDT drive Properties dialog box, on the Rules tab, review the deployment share settings and rules.These settings and rules were preconfigured for this PoC Jumpstart.          9.    Update the Deployment Share The final step before creating the startup disk (and/or .WIM file for a network/PXE boot) is to update the deployment share. This step can effectively generate both a .WIM file and an .ISO file for bootable CD/DVD or USB flash drive. Client computers boot up from the network or startup disk and retrieve image installation information from the server.STEPS    EXAMPLESStart the Update Deployment Share Wizard The Update Deployment Share Wizard helps you summarize all the component import and task sequence configurations into an output: the boot images (a .WIM and/or an .ISO file).1.    In Deployment Workbench, expand Deployment Shares, right-click MDT drive and then click Update Deployment Share.The Update Deployment Share Wizard starts.     Select Update OptionsOn this wizard page, you can choose to completely regenerate the boot images, or optimize (and/or compress the image) to include any updates that you made.1.    On the Options page, select Completely regenerate the boot images and then click Next STEPS    EXAMPLESComplete Deployment Share UpdateWhen you update the deployment share, MDT either creates a new boot images or rebuilds existing images. This step may take a few minutes to complete because all of the image configurations are being enumerated and written to the boot images.1.    On the Summary page, review the deployment share update details and then click Next.The Progress page displays information about the deployment share update status.2.    On the Confirmation page, click Finish.     Verify Deployment Share Update After the wizard completes, use Windows Explorer to locate the generated boot images.1.    Open Windows Explorer (Start > Run > explorer).2.    Navigate to the C:\Win7Dep\Boot folder.3.    Verify that the .WIM and/or .ISO file that you generated appears in the folder.