Right-click the Operating Systems node, and then click New Folder. Name the new folder Windows Complete the wizard using default values and click Finish. Right-click the Windows 10 folder created in the previous step, and then click Import Operating System.
For purposes of this test lab, we will only add the prerequisite. NET Framework feature. Commerical applications ex: Microsoft Office will not be added to the deployment share. For information about adding applications, see the Add applications section of the Create a Windows 10 reference image topic in the TechNet library.
The next step is to create a task sequence to reference the operating system that was imported. Use the following settings for the New Task Sequence Wizard:.
To edit the task sequence, double-click Windows 10 Enterprise x64 Default Image that was created in the previous step. Click the Task Sequence tab. Click another location in the window to see the name change. Under Select the roles and features that should be installed , select.
NET Framework 3. NET 2. Enable Windows Update in the task sequence by clicking the Windows Update Post-Application Installation step, clicking the Options tab, and clearing the Disable this step checkbox. Since we are not installing applications in this test lab, there is no need to enable the Windows Update Pre-Application Installation step.
However, you should enable this step if you are also installing applications. The next step is to configure the MDT deployment share rules. Click Apply and then click Edit Bootstrap. Replace the contents of the Bootstrap. The update process will take 5 to 10 minutes. When it has completed, click Finish.
Accept the default values on the Capture Image page, and click Next. Operating system installation will complete after 5 to 10 minutes, and then the VM will reboot automatically. Allow the system to boot normally do not press a key. The process is fully automated. Additional system restarts will occur to complete updating and preparing the operating system.
Setup will complete the following procedures:. This step requires from 30 minutes to 2 hours, depending on the speed of the Hyper-V host. After some time, you will have a Windows 10 Enterprise x64 image that is fully patched and has run through Sysprep. Use the following values in the New Deployment Share Wizard:. Click Next , verify the new deployment share was added successfully, then click Finish. Click Start , and then point to All Programs. When you have prepared the MDT environment, create the reference computer.
The reference computer is the template for deploying new images to the target computers. Configure this computer exactly as the target computers will be configured. You will deploy Windows 8. Creating a task sequence for the reference computer as described in Step Create a Task Sequence for the Reference Computer.
Updating the deployment share as described in Step Update the Deployment Share. This deployment share is the repository for the operating system images, language packs, applications, device drivers, and other software deployed to the target computers.
The Import Operating System Wizard finishes. Windows 8. After you have added Windows 8. These device drivers will be added to Windows PE and deployed with Windows 8. To add the device drivers for the reference and target computers to the distribution share. The Import Driver Wizard finishes.
Complete the New Task Sequence Wizard using the following information. You monitor the LTI deployment process in the Monitoring node in the deployment share. You enable monitoring on the Monitoring tab on the deployment share properties sheet. Later in the process, you will monitor the LTI deployment process. After configuring the deployment share, update it. Updating the deployment share updates all the MDT configuration files and generates a customized version of Windows PE.
Complete the Update Deployment Share Wizard using the following information. After creating the task sequence to deploy Windows 8. You need to provide a method for starting the computer with the customized version of Windows PE you created when you updated the deployment share. Create the appropriate LTI bootable media from one of these images. At the end of the MDT deployment process, Windows 8. You can use a bit boot image to deploy both bit and bit operating systems; however, a bit boot image can only be used to deploy bit operating systems.
You could also initiate the process by starting the target computer from Windows Deployment Services. Complete the Windows Deployment Wizard using the following information. In the WDG-REF Properties dialog box, on the Identity tab, view the monitoring information provided about the deployment process as described in the following table.
Therefore, your best bet would be to download one of these software packages and use one of them to open your file. Zipped files tend to require special handling and may require password access. Contact the file owner or the person who gave you the file for the password and unzip the file before attempting to open the contents. On a Mac, select "More info" and "Kind". Because many programs packages utilize Database Files, you might be able to find a program on your computer that handles those types of files.
You can control whether packages are available to other wizards and dialog boxes in the Deployment Workbench by selecting the Enable approve this package check box on the General tab of the package Properties dialog box. If you want to configure a package so that it can only be installed during a task sequence step, disable the application.
Doing so allows the package to be installed during the task sequence but prevents the application from appearing in the list of available package.
For more information on enabling or disabling packages in the Deployment Workbench, see Configuring Packages in the Deployment Workbench. You can prevent a package from being visible in the Deployment Wizard by selecting the Hide this application in the Deployment Wizard check box on the General tab of the application Properties dialog box.
For more information on preventing packages from appearing in the Deployment Wizard, see Configuring Packages in the Deployment Workbench. Adding packages in a deployment share's Packages node through the Deployment Workbench is the simplest method for deploying most packages. The Install Updates Offline task sequence type allows you to install one or more packages in a single task sequence step using selection profiles, which allow one or more packages to be selected and deployed as a unit.
For more information managing selection profiles, see Manage Selection Profiles. You configure an existing Apply Patches task sequence step by modifying the configuration settings on the Properties tab of the task sequence step.
On the Properties tab, configure the settings listed in Table 48 based on the requirements of your organization, and then click OK. In most instances, the existing Apply Patches task sequence step is sufficient for installing packages to target computers. However, there are instances in which the existing Apply Patches task sequence step may not be sufficient for your requirements or you may need to install a package at a different place in the task sequence.
For example, the packages may need to be installed in a specific order or may have dependencies, such as installing a service pack before installing hotfixes.
First, create folders and selection profiles for each grouping of packages that you wanted to install separately. Then, install the groups of packages by creating a new task sequence step for each group based on the Install Updates Offline —type task sequence step. You can disable the existing Apply Patches step in the task sequence and add all packages manually using the task sequence controls.
The benefit of this approach is that you easily select and insert packages into the task sequence in any order necessary. This simplifies management of a large number of packages. Create a new task sequences step based on the Install Updates Offline type at the appropriate place in the task sequence hierarchy as described in Configure the Task Sequence Properties Task Sequence Tab.
Configure the new task sequence step to deploy one or more packages by selecting the appropriate selection profile containing the packages to be installed as described in Configure an Existing Install Applications Task Sequence Step. Language packs are one of the types of packages available in MDT and enable a multilingual Windows environment.
Windows is now language neutral, and all language and locale resources are added to Windows through language packs Lp. By adding one or more language packs to Windows those languages can be enabled when installing the operating system. As a result, the same Windows image can be deployed to regions with different language and locale settings, reducing development and deployment time.
For instructions on installing language packs during deployment, see Running the Deployment Wizard. For the configuration properties for installing language packs automatically, see the MDT document Toolkit Reference. Integrate device drivers for the reference and target computers into Windows PE and the target operating system unless these components are included in Windows PE or the target operating system.
The Deployment Workbench helps centralize and automate device driver management and integration for LTI by providing a centralized repository of device drivers, ensuring that the proper device drivers are deployed.
The Deployment Workbench also automates the injection of the appropriate device drivers into Windows PE images that the Deployment Workbench generates. MDT supports different strategies for device driver management. For more information about device driver management strategies, see Managing Device Drivers. Start the Import Drivers Wizard using one of the following methods:. Then, in the Actions pane, click Import Drivers. Then, from the Action menu, click Import Drivers.
The Import Drivers Wizard finishes. The device drivers are added to the list of device drivers in the details pane of the Deployment Workbench. Configure device drivers in the Deployment Workbench by performing the following steps in the device driver Properties dialog box:. The device driver properties stored on the General tab are mostly configured when you run the Import Device Drivers Wizard.
On the General tab, configure the settings listed in Table 50 based on the requirements of your organization, and then click OK. The device driver configuration settings are saved, and the modifications are displayed in the details pane of the Deployment Workbench. The device driver properties stored on the Details tab are configured when you run the Import Device Drivers Wizard.
All the information on the Details tab is read only and cannot be modified. On the Details tab, view the settings listed in Table 51, and then click OK.
The configuration settings on the Details tab are automatically determined by the Deployment Workbench and cannot be modified. You can copy and paste device drivers and folders beneath the Out-of-Box Drivers node in the Deployment Workbench using the Copy and Paste actions as described in Copy Items in the Deployment Workbench.
You can rename device drivers and folders beneath the Out-of-Box Drivers node in the Deployment Workbench using the Rename action as described in Rename Items in the Deployment Workbench.
The Delete Selected Items Wizard allows you to delete individual packages or entire folder structures. You can manage folders beneath the Out-of-Box Drivers node in the Deployment Workbench to create hierarchical groupings of device drivers.
You can control whether device drivers are available to other wizards and dialog boxes in the Deployment Workbench by selecting the Enable this driver check box on the General tab of the device driver Properties dialog box.
For more information on enabling or disabling device drivers in the Deployment Workbench, see Modify Existing Device Drivers in the Deployment Workbench. Then, the target operating system uses Plug-and-Play IDs to identify the device drivers that are needed for the devices on the target computers. For more information about strategies for device driver management, see Select the Device Driver Management Strategy. Use the Deployment Workbench to manage the task sequences used to perform deployments to the reference and target computers in your organization.
Modifying the unattended setup answer file for a task sequence as described in Modify the Unattended Setup Answer File Associated with the Task Sequence. Start the New task Sequence Wizard using one of the following methods:. In the console tree, click the Task Sequences node or a folder beneath the Task Sequences node, and then, in the Actions pane, click New Task Sequence. In the console tree, click the Task Sequences node or a folder beneath the Task Sequences node, and then, from the Action menu, click New Task Sequence.
MDT includes task sequence templates that you can use for common deployment scenarios. In many instances, you can use the templates without any modification to the task sequence. However, you can modify task sequences created from the templates to meet the requirements of your organization.
Select the Litetouch OEM task sequence only when performing deployments using removable media—based deployments you create in the Media node in the Deployment Workbench. Although you can select the Litetouch OEM Task Sequence template from other deployment shares, the task sequence will not finish successfully. The New Task Sequence Wizard finishes. Configure task sequences in the Deployment Workbench by performing the following steps in the task sequence Properties dialog box:.
The task sequence properties stored on the General tab are mostly configured when you run the New Task Sequence Wizard. On the General tab, configure the settings listed in Table 54 based on the requirements of your organization, and then click OK.
The task sequence configuration settings are saved, and the modifications are displayed in the details pane of the Deployment Workbench. The task sequence properties stored on the Task Sequence tab are mostly configured when you run the New Task Sequence Wizard. The Task Sequence tab contains a hierarchical representation of the task sequence steps and their sequence. Task sequence steps are organized into a hierarchical folder structure based on deployment phases.
You can organize one or more task sequence steps by creating a group. You can organize multiple groups and task sequence steps to create a hierarchy of groups and task sequence steps. You use task sequence step groups to control the processing of one or more task sequence steps as a unit.
Configure the task sequence steps and step sequence by selecting one of the following options from the menu bar at the top of the hierarchical representation:. Select to add a task sequence step group or step to the task sequence. The categories of task sequence steps that you can add are listed in Table 56 along with the task sequence step types in each category. For more information about each of the task sequence step types listed in Table 55, see the corresponding section in the MDT document Toolkit Reference.
Select to configure a task sequence step to be processed earlier in the deployment process. The move is reflected in the task sequence hierarchy. If you move the first task sequence step in a task sequence group up, the task sequence step will be performed before the entire group and will be removed from the group. If another task sequence group immediately precedes the group, the task sequence step will become the last step in the preceding group.
If you move the last task sequence step in a task sequence group down, the task sequence step will be performed after the entire group and will be removed from the group. If another task sequence group immediately follows the group, the task sequence step will become the first step in the following group. On the Task Sequence tab, in the task sequence hierarchy, configure the task sequence steps and step sequences based on the requirements of your organization, and then click OK.
On the Properties tab, you configure the properties for task sequence groups or individual task sequence steps. The configuration settings for:. Table 56 lists the properties common to task sequence groups and steps. In addition to these properties, most task sequence steps have properties that are specific to the task sequence type. Configuring specific task sequence step types, see the corresponding section in Configuring Task Sequences in the Deployment Workbench.
The properties for each task sequence type, see the section for corresponding task sequence steps in the MDT document Toolkit Reference.
On the Task Sequence tab, in the task sequence hierarchy, click the Properties tab. On the Properties tab, configure the task sequence group or individual step based on the requirements of your organization, and then click OK. On the Options tab, you configure settings that control how the task sequence step runs. These settings allow you to disable the step, specify the return codes for the step that indicate success, determine whether the step should continue in the event of an error, and any conditions for running the step.
For example, if you configure a condition for a task sequence group, that condition affects all the task sequence steps within the group. On the Task Sequence tab, in the task sequence hierarchy, click the Options tab. On the Options tab, configure the task sequence group or individual step sequences based on the requirements of your organization, and then click OK. On the Task Sequence tab, configure the settings listed in Table 57 based on the requirements of your organization, and then click OK.
On the OS Info tab, configure the settings listed in Table 58 based on the requirements of your organization, and then click OK. You can copy and paste task sequences and folders beneath the Task Sequences node in the Deployment Workbench using the Copy and Paste actions as described in Copy Items in the Deployment Workbench. Rename task sequences and folders beneath the Task Sequences node in the Deployment Workbench by using the Rename action as described in Rename Items in the Deployment Workbench.
The Delete Selected Items Wizard allows you to delete individual task sequences or entire folder structures. You can manage folders beneath the Task Sequences node in the Deployment Workbench to create hierarchical groupings of task sequences.
You can control whether task sequences are available to other wizards and dialog boxes in the Deployment Workbench using the Enable this task sequence check box on the General tab of the package Properties dialog box, as described in Configuring Task Sequences in the Deployment Workbench.
You can prevent a task sequence from being visible in the Deployment Wizard using the Hide this task sequence in the Deployment Wizard check box on the General tab of the application Properties dialog box, as described in Configuring Task Sequences in the Deployment Workbench. MDT automatically updates the unattended setup answer file Unattend. However, there are instances in which you may need to modify the unattended setup answer file for a task sequence directly, such as when you modify a configuration parameter that is not exposed in the Deployment Workbench or in the Deployment Wizard.
Directly modify the unattended setup answer file for a task sequence by clicking Edit Unattend. You use the Deployment Workbench to perform many of the common management tasks.
Although some management is unique to each type of item, the following tasks are common to all items in the Deployment Workbench:.
Managing folders as described in Manage Folders in the Deployment Workbench. Copying items as described in Copy Items in the Deployment Workbench.
Moving items as described in Move Items in the Deployment Workbench. Renaming items as described in Rename Items in the Deployment Workbench. Deleting items as described in Delete Items from the Deployment Workbench. You use folders to organize applications, operating systems, device drivers, and other items in the Deployment Workbench.
Folders allow you to create hierarchies for organizing items as well as subsets of items that you can include in selection profiles. Folders are similar in concept to the groups that existed in previous versions of MDT, such as device driver groups. Copying a folder as described in Copy a Folder in the Deployment Workbench. Moving a folder as described in Move a Folder in the Deployment Workbench. Renaming a folder as described in Rename a Folder in the Deployment Workbench.
Deleting a folder as described in Delete a Folder from the Deployment Workbench. Enabling or disabling a folder as described in Enable or Disable a Folder in the Deployment Workbench. Start the New Folder Wizard using one of the following methods:. In the console tree, click a node or a folder. Then, in the Actions pane, click New Folder. Then, from the Action menu, click New Folder. After the New Folder Wizard finishes, the new folder appears in the deployment share in the Deployment Workbench.
The folder properties are mostly configured when you run the New Folder Wizard. On the General tab, configure the settings listed in Table 60 based on the requirements of your organization, and then click OK. The folder configuration settings are saved, and the modifications are displayed in the details pane of the Deployment Workbench. The Delete Selected Items Wizard allows you to delete individual folders or an entire hierarchy of folders. You can control whether folders are available to other wizards and dialog boxes in the Deployment Workbench using the Enable this folder check box on the General tab of the folder Properties dialog box.
For more information on enabling or disabling folders in the Deployment Workbench, see Modify an Existing Folder in the Deployment Workbench. You can view the properties of operating systems, device drivers, and other items from the Deployment Workbench using one of the following methods:. In the details pane, click an item.
Then, in the Actions pane, click Properties. Then, from the Action menu, click Properties. In the details pane, click item where item is the name of the item to be renamed.
The item Properties dialog box is displayed where item is the name of the item you selected. Use the Deployment Workbench to copy operating systems, device drivers, and other items within a deployment share or between two deployments shares.
When you copy an item, the Deployment Workbench creates a link to the original item instead of creating a separate copy of the item. This reduces the size of the deployment share. If you want to create a duplicate of an item, import the item again in the target folder. GUID already exists in the target deployment share, the configuration settings for the source item will be applied to the target item, including the name if the items do not already have the same name.
Name already exists in the target deployment share, an error is generated, because two items of the same type cannot have the same name. You can copy an item using the Cut and Paste actions in the Deployment Workbench. Copy the item from the source location using one of the following methods:.
Then, from the Action menu, click Copy. In the details pane, click the target location. Then, in the Actions pane, click Paste. Then, from the Action menu, click Paste. In the details pane, click item where item is the name of the item to be copied. In the details pane, drag item where item is the name of the item to be copied to the target location, press CTRL, and then release the mouse button.
Use the Deployment Workbench to move operating systems, device drivers, and other items within a deployment share or between two deployments shares. You can move items by using:. You can move an item using the Cut and Paste in the Deployment Workbench. Cut the item from the source location using one of the following methods:. In the details pane, drag item where item is the name of the item to be moved to the target location. You can rename operating systems, device drivers, and other items in the Deployment Workbench by using one of the following methods:.
Then, from the Action menu, click Rename. Because the Copy and Paste actions in the Deployment Workbench create a link to the original item rather than a separate copy.
So, when you rename an item, the Deployment Workbench automatically renames any copies of an item in other folders. Then, in the Actions pane, click Rename. You can delete operating systems, device drivers, and other items from the Deployment Workbench using the Delete Selected Items Wizard. Start the Delete Selected Items Wizard using one of the following methods:. Then, from the Action menu, click Delete. You can delete individual items or folders that contain one or more items or subfolders.
You can also delete items that have copies in multiple folders. In the details pane, click item where item is the name of the item to be deleted, such as a folder, an operating system, or a device driver. After the Delete Selected Items Wizard finishes, the item and other affected items are removed from the Deployment Workbench and from the deployment share.
The Deployment Workbench includes advanced configuration options that extend the features provided in basic LTI deployments. These configuration options provide more granular selection of the content you want to include in the deployment, support deployments in larger organizations, and support deployments from stand-alone media without the need to connect to a deployment share.
Managing selection profiles as described in Manage Selection Profiles. Managing linked deployment shares as described in Manage Linked Deployment Shares. Selection profiles allow you to select one or more folders in the Deployment Workbench that contain one or more items in the Deployment Workbench, including applications, device drivers, operating systems, operating system packages, and task sequences.
To include the appropriate device drivers for the target operating system in the Inject Drivers task sequence step type. To identify the operating system packages to deploy in the Install Updates Offline task sequence step type. Modify an existing selection profile as described in Modify an Existing Selection Profile in the Deployment Workbench.
Identify the differences between selection provides and groups as described in Identify the Relationship Between Selection Profiles and Groups. Start the New Selection Profile Wizard using one of the following methods:.
In the console tree, click the Selection Profiles node. Then, in the Actions pane, click New Selection Profile. Then, from the Action menu, click New Selection Profile. The New Selection Profile Wizard finishes. The selection profile is added to the list of selection profiles in the details pane of the Deployment Workbench. The selection profile properties are mostly configured when you run the New Selection Profile Wizard. On the General tab, configure the settings listed in Table 65 based on the requirements of your organization, and then click OK.
You can copy and paste selection profiles in the Deployment Workbench using the Copy and Paste actions as described in Copy Items in the Deployment Workbench. You can rename selection profiles in the Deployment Workbench using the Rename action as described in Rename Items in the Deployment Workbench. The Delete Selected Items Wizard allows you to delete individual selection profiles. Use selection profiles to create groups of Deployment Workbench items, such as operating systems, device drivers, or applications.
Use the selection profiles to specify device drivers, define content to include in a linked deployment share, define the content to include for media deployments, and other tasks. The following code is an excerpt from the DriverGroups. This file contains the definitions for all the selection profiles defined for the deployment share. The following code is an excerpt from the SelectionProfile.
By default, if you do not specify a selection profile or group in the CustomSettings. If you specify both selection profiles and groups in the CustomSettings. For example, if you specify a selection profile and use the default group which includes all items , the end result is that LTI uses all items, because the default group includes all items, regardless of what you specify in the selection profile. To restrict the items to a selection profile, specify a group that contains no items that is, is empty.
The reverse is true if you want to use a group. Because of the introduction of folders in MDT, groups include all folders and subfolders by default. You can override this behavior using the SkipGroupSubFolders property. For more information on this property, see the corresponding section in the MDT document Toolkit Reference.
In most instances, you can use selection profiles and groups to perform most deployments. However, the following properties are available for more advanced scenarios—such as if you want to exclude a parent folder but include a child folder:. For more information on these properties, see the corresponding sections in the MDT document Toolkit Reference. Linked deployment shares in MDT allow you to provide a logical connection between two deployment shares: a source and a target deployment share.
A selection profile determines the items to be linked. When creating the link between the deployment shares, you can choose whether to merge or replace content in the target deployment share. Using linked deployment shares, you can easily replicate an entire deployment share or portions of a deployment share to another deployment share.
In this way, you can make changes to one deployment share, and then easily update other deployment shares based on the selection profiles you chose when creating the linked deployment shares.
In addtion to managing linked deployement shares in the Deployment Workbench, you can manage linked deployment shares using the MDT Windows PowerShell cmdlets.
In the console tree, click the Linked Deployment Share node. The New Linked Deployment Share Wizard finishes, and the linked deployment share is added to the list of linked deployments shares in the details pane of the Deployment Workbench.
0コメント