Configuring Processing Rules

The scripts configure computer settings based on rules and configuration settings stored in the CustomSettings.ini file. During the Microsoft Solutions Framework (MSF) Planning Phase, you determined the appropriate processing rules to use in your organization. Now you need to configure those rules in the CustomSettings.ini or in the Deployment Workbench database (DWDB).

Figure 6 illustrates the steps in configuring processing rules.

Figure 6. Steps in configuring the processing rules

Figure 6. Steps in configuring the processing rules

To configure the processing rules

  1. Configure the rules in CustomSettings.ini.

  2. Configure the rules in the DWDB.

  3. Modify the list of incompatible BIOS versions.

  4. Modify the task sequence for a build.

  5. Modify the driver groups included in a build.

  6. Update deployment processing rules.

On This Page

Configuring the Rules in the CustomSettings.ini File Configuring the Rules in the CustomSettings.ini File
Configuring the Rules in the Deployment Workbench Database Configuring the Rules in the Deployment Workbench Database
Modifying the List of Incompatible BIOS Versions Modifying the List of Incompatible BIOS Versions
Modifying the Task Sequence for a Build Modifying the Task Sequence for a Build
Selecting the Driver Groups Included in a Build Selecting the Driver Groups Included in a Build
Updating Deployment Processing Rules Updating Deployment Processing Rules

Configuring the Rules in the CustomSettings.ini File

You configure rules in the CustomSettings.ini file. Modify the CustomSettings.ini file based on the rules you determined during the MSF Planning Phase. The template version of the CustomSettings.ini file, along with your rules, becomes your customized CustomSettings.ini. For more information about determining the appropriate rules, see “Determining the Appropriate Processing Rules” earlier in this guide.

Depending on your environment, you might need to customize the CustomSettings.ini template for LTI only. For LTI, configuring group-based settings may be sufficient. For ZTI, you must add configuration settings unique to a specific client computer. These configuration settings can be in addition to or instead of the group-based rules.

Configuring the Rules in the Deployment Workbench Database

You can configure the rules for LTI and ZTI deployments in the DWDB by using Deployment Workbench. The benefits of using the DWDB include:

  • More generic version of CustomSettings.ini. Storing the configuration settings in the DWDB removes most of the detail from CustomSettings.ini. This change helps make the CustomSettings.ini file more generic so that the same file can be used in multiple deployment points.

  • Centralized repository for all property configuration settings. Centralizing the configuration for all property settings ensures consistency across all deployment points.  

To configure the rules in the configuration database

  1. Configure the property values in the DWDB by using in the Database node in Deployment Workbench.

  2. Configure CustomSettings.ini to include the appropriate database queries for returning the property values stored in the DWDB.

Configuring the Property Values in the Deployment Workbench Database

The configuration of the property values in the DWDB is organized by the method for applying the properties to the target computers. A node beneath the Database node in Deployment Workbench represents each method, as listed in Table 8.

Table 8. Nodes Beneath the Database Node in Deployment Workbench

Node

Use this node to define

Computers

Specific target computers based on the AssetTag, UUID, SerialNumber, and MACAddress properties. You can associate property settings, applications, packages, roles, and administrative-level accounts with a computer.

Roles

A group of computers based on the tasks performed by the users of the target computers (by using the Role property). You can associate property settings, applications, packages, and administrative-level accounts with a role.

Locations

A group of computers by using the DefaultGateway property of the target computers to identify a geographic location. You can associate property settings, applications, packages, roles, and administrative-level accounts with a location.

Make and Model

A group of computers by using the Make and Model properties of the target computers. You can associate property settings, applications, packages, roles, and administrative-level accounts with target computers that are of the same Make and Model

Note   Create the items in the Role node before you create the other items beneath other nodes (Computers, Locations, and Make and Model) because the other nodes can be associated with roles.

Creating a New Roles Item

To create a new Roles item , complete the following steps

  1. Start Deployment Workbench.

  2. In the console tree, expand Deploy, expand Database, and then click Roles.

  3. In the console tree, right-click Roles, and then click New.

  4. In the Properties dialog box, on the Identity tab, in the Role name box, type role_name (where role_name is the name of the role).

  5. Click the Details tab, and then configure the appropriate property values that you identified earlier in the process.

  6. Click the Applications tab, and then configure the applications to install and the order of the application installations.

  7. Click the Packages tab, and then configure the packages to install and the order of the package installations.

  8. Click the Administrators tab, configure the accounts to be made members of the local Administrators group on the target computers, and then click OK.

Creating a New Computers Item

To create a new Computers item , complete the following steps

  1. Start Deployment Workbench.

  2. In the console tree, expand Deploy, expand Database, and then click Computers.

  3. In the console tree, right-click Computers, and then click New.

  4. In the Properties dialog box, on the Identity tab, provide the information listed in Table 9.

    Table 9. Information to Complete Identity Tab for a New Computers Item

    In this box

    Type

    Description

    The user-friendly description of the computer.

    Asset tag

    The asset tag or inventory control tag assigned to the computer.

    UUID

    The universally unique identifier (UUID) assigned to the target computer.

    Serial number

    The serial number assigned to the target computer.

    MAC address

    The MAC address assigned to the target computer.

    For more information on the values for asset tag, UUID, serial number, and MAC address, see the AssetTag, UUID, SerialNumber, and MACAddress properties in Configuration Reference.

  5. Click the Details tab, and then configure the appropriate property values that you identified earlier in the process.

  6. Click the Applications tab, and then configure the applications to install and the order of the application installations.

  7. Click the Packages tab, and then configure the packages to install and the order of the package installations.

  8. Click the Roles tab, and then configure the roles that you want to associate with the computer.

  9. Click the Administrators tab, configure the accounts to be made members of the local Administrators group on the target computers, and then click OK.

Creating a New Locations Item

To create a new Locations item , complete the following steps

  1. Start Deployment Workbench.

  2. In the console tree, expand Deploy, expand Database, and then click Locations.

  3. In the console tree, right-click Locations, and then click New.

  4. In the Properties dialog box, on the Identity tab, in the Location box, type location_name (where location_name is the user-friendly name to associate with the location).

  5. In the Properties dialog box, on the Identity tab, in the Default gateways box, add the IP addresses for all default gateways that exist within the location.

  6. Click the Details tab, and then configure the appropriate property values that you identified earlier in the process.

  7. Click the Applications tab, and then configure the applications to install and the order of the application installations.

  8. Click the Packages tab and then configure the packages to install and the order of the package installations.

  9. Click the Roles tab, and then configure the roles that you wish to associate with the computer.

  10. Click the Administrators tab, configure the accounts to be made members of the local Administrators group on the target computers, and then click OK.

Creating a New Make and Model Item

To create a new Make and Model item , complete the following steps

  1. Start Deployment Workbench.

  2. In the console tree, expand Deploy, expand Database, and then click Make and Model.

  3. In the console tree, right-click Make and Model, and then click New.

  4. In the Properties dialog box, on the Identity tab, in the Make box, type make_name (where make_name is the user-friendly name to associate with the make of the manufacturer of the target computers).

  5. Also on the Identity tab, in the Model box, type model_name (where model_name is the user-friendly name to associate with the model of the target computers).

  6. Click the Details tab, and then configure the appropriate property values that you identified earlier in the process.

  7. Click the Applications tab, and then configure the applications to install and the order of the application installations.

  8. Click the Packages tab, and then configure the packages to install and the order of the package installations.

  9. Click the Roles tab, and then configure the roles that you wish to associate with the computer.

  10. Click the Administrators tab, configure the accounts to be made members of the local Administrators group on the target computers, and then click OK.

Configuring CustomSettings.ini for Database Queries

After you have configured the property values in the DWDB, you need to configure CustomSettings.ini to perform the appropriate database queries. You can do so by using the Configure DB Wizard in Deployment Workbench.

Run the Configure DB Wizard for each deployment point defined in Deployment Workbench that you wish to update.

To configure CustomSettings.ini for database queries by using the Configure DB Wizard in Deployment Workbench , complete the following steps

  1. Start Deployment Workbench.

  2. In the console tree, expand Deploy, and then click Deployment Points.

  3. In the details pane, right-click deployment_point, and then click Configure DB (where deployment_point is the name of the deployment point you want to configure).

    The Configure DB Wizard starts.

  4. Complete the Select computer query options. wizard page by using the information in Table 10, and then click Next.

    Table 10. Information to Complete the Select computer query options. Wizard Page

    Select this check box

    When you want to

    Query for computer-specific settings.

    Query the settings configured on the Details tab of the Properties dialog box of the computer item.

    Query for roles assigned to this computer.

    Query the roles associated with the computer on the Roles tab of the Properties dialog box of the computer item.

    Query for applications to be installed on this computer.

    Query the applications to be installed on the computer as configured on the Applications tab of the Properties dialog box of the computer item.

    Query for SMS packages to be installed on this computer.

    Query the packages to be installed on the computer as configured on the Packages tab of the Properties dialog box of the computer item.

    Query for administrators to be assigned to this computer.

    Query the accounts that are to be made members of the local Administrators group on the target computer as configured on the Administrators tab of the Properties dialog box of the computer item.

  5. Complete the Select role query options wizard page by using the information in Table 11, and then click Next.

    Table 11. Information to Complete the Select role query options. Wizard Page

    Select this check box

    When you want to

    Query for role-specific settings.

    Query the settings configured on the Details tab of the Properties dialog box of the role item.

    Query for applications to be installed for this role.

    Query the applications to be installed on computers that perform this role, as configured on the Applications tab of the Properties dialog box of the role item.

    Query for SMS packages to be installed for this role.

    Query the packages to be installed on computers that perform this role as configured on the Packages tab of the Properties dialog box of the role item.

    Query for administrators to be assigned for this role.

    Query the accounts that are to be made members of the local Administrators group on computers that perform this role as configured on the Administrators tab of the Properties dialog box of the role item.

  6. Complete the Select location query options. wizard page by using the information in Table 12, and then click Next.

    Table 12. Information to Complete the Select location query options. Wizard Page

    Select this check box

    When you want to

    Query for location names based on default gateways.

    Query for location names based on the IP addresses of the default gateways configured on the Identity tab of the Properties dialog box of the location item.

    Query for location-specific settings.

    Query the settings configured on the Details tab of the Properties dialog box of the location item.

    Query for roles assigned for this location.

    Query the roles associated with the location on the Roles tab of the Properties dialog box of the location item.

    Query for applications to be installed for this location.

    Query the applications to be installed on the target computers within the location configured on the Applications tab of the Properties dialog box of the location item.

    Query for SMS packages to be installed for this location.

    Query the packages to be installed on the target computers within the location as configured on the Packages tab of the Properties dialog box of the location item.

    Query for administrators to be assigned for this location.

    Query the accounts that are to be made members of the local Administrators group on the target computers within the location as configured on the Administrators tab the Properties dialog box of the location item.

  7. Complete the Select make and model query options. wizard page by using the information in Table 13, and then click Finish.

    Table 13. Information to Complete the Select make and model query options. Wizard Page

    Select this check box

    When you want to

    Query for model-specific settings.

    Query the settings configured on the Details tab on the Properties dialog box of the make and model item.

    Query for roles assigned to computers with this make and model.

    Query the roles associated with the make and model on the Roles tab of the Properties dialog box of the make and model item.

    Query for applications to be installed on computers with this make and model.

    Query the applications to be installed on the target computers with the make and model as configured on the Applications tab of the Properties dialog box of the make and model item.

    Query for SMS packages to be installed on computers with this make and model.

    Query the packages to be installed on the target computers with the make and model as configured on the Packages tab of the Properties dialog box of the make and model item.

    Query for administrators to be assigned to machines with this make and model.

    Query the accounts that are to be made members of the local Administrators group on the target computer with the make and model as configured on the Administrators tab of the Properties dialog box of the make and model item.

Upon completion of the Configure DB Wizard, the CustomSettings.ini file is configured to perform the selected queries. Listing 6 illustrates an example of the CustomSettings.ini file after completion of the Configure DB Wizard.

Listing 6. The CustomSettings.ini file After Completion of the Configure DB Wizard

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

[Settings]
Priority=ComputerSettings, ComputerPackages, ComputerApplications,
ComputerAdministrators, ComputerRoles, RoleSettings, RolePackages,
RoleApplications, RoleAdministrators, Locations, LocationSettings,
LocationPackages, LocationApplications, LocationAdministrators,
LocationRoles, MakeModelSettings, MakeModelPackages, 
MakeModelApplications,MakeModelAdministrators,
MakeModelRoles, Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
ScanStateArgs=/v:5 /o /c
LoadStateArgs=/v:5 /c /lac
[ComputerSettings]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=ComputerSettings
Parameters=UUID, AssetTag, SerialNumber, MacAddress
ParameterCondition=OR
[ComputerPackages]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=ComputerPackages
Parameters=UUID, AssetTag, SerialNumber, MacAddress
ParameterCondition=OR
Order=Sequence
[ComputerApplications]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=ComputerApplications
Parameters=UUID, AssetTag, SerialNumber, MacAddress
ParameterCondition=OR
Order=Sequence
[ComputerAdministrators]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=ComputerAdministrators
Parameters=UUID, AssetTag, SerialNumber, MacAddress
ParameterCondition=OR
[ComputerRoles]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=ComputerRoles
Parameters=UUID, AssetTag, SerialNumber, MacAddress
ParameterCondition=OR
[RoleSettings]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=RoleSettings
Parameters=Role
[RolePackages]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=RolePackages
Parameters=Role
Order=Sequence
[RoleApplications]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=RoleApplications
Parameters=Role
Order=Sequence
[RoleAdministrators]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=RoleAdministrators
Parameters=Role
[Locations]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=Locations
Parameters=DefaultGateway
[LocationSettings]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=LocationSettings
Parameters=DefaultGateway
[LocationPackages]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=LocationPackages
Parameters=DefaultGateway
Order=Sequence
[LocationApplications]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=LocationApplications
Parameters=DefaultGateway
Order=Sequence
[LocationAdministrators]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=LocationAdministrators
Parameters=DefaultGateway
[LocationRoles]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=LocationRoles
Parameters=DefaultGateway
[MakeModelSettings]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=MakeModelSettings
Parameters=Make, Model
[MakeModelPackages]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=MakeModelPackages
Parameters=Make, Model
Order=Sequence
[MakeModelApplications]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=MakeModelApplications
Parameters=Make, Model
Order=Sequence
[MakeModelAdministrators]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=MakeModelAdministrators
Parameters=Make, Model
[MakeModelRoles]
SQLServer=W2K3-SP1
Instance=
Database=DWDB
Netlib=DBNMPNTW
SQLShare=
Table=MakeModelRoles
Parameters=Make, Model

For more information on:

  • Customizing the configuration database, see:

    • “Automating Deployment to a Specific Computer” in Deployment Configuration Samples Guide.

    • “Automating Deployment by Role” in Deployment Configuration Samples Guide.

    • “Automating Deployment by Location” in Deployment Configuration Samples Guide.

    • “Automating Deployment by Computer Make and Model” in Deployment Configuration Samples Guide.

  • Each property, see the corresponding section for each property in “Property Reference” in Configuration Reference.

  • The tables and views in the configuration database, see “Tables and Views in the Deployment Workbench Database” in Configuration Reference.

Modifying the List of Incompatible BIOS Versions

The default task sequence for a build includes the Check BIOS task in the Non-Replace group in the Validation group. The Check BIOS task runs the ZTIBIOSCheck.wsf script. The ZTIBIOSCheck.wsf script checks the basic input/output system (BIOS) version of the target computers against the list of incompatible BIOS versions in the ZTIBIOSCheck.xml file.

You can modify the ZTIBIOSCheck.xml file to contain the list of BIOS versions that are incompatible with the target operating system in the operating system build. You can modify the ZTIBIOSCheck.xml for each build that you create in Deployment Workbench. The ZTIBIOSCheck.xml file is stored in the distribution_point\build_id\TS.xml file (where distribution_point is the name of the folder that is the root of the distribution point and build_id is the name of the Build ID listed in Deployment Workbench).

Update the attributes in the ZTIBIOSCheck.xml file listed in Table 14 for each incompatible BIOS version.

Table 14. Attributes to Update in the ZTIBIOSCheck.xml File

Attribute

Description

DESCRIPTION

Text description of the target computer that has an incompatible BIOS version, including any references to possible updates to the BIOS version.

Computer Manufacturer

Manufacturer of the target computer with an incompatible BIOS version. This value must match the value stored in the BIOS.

Model

Model of the target computer with an incompatible BIOS version. This value must match the value stored in the BIOS.

Date

Date of the BIOS for the target computer with an incompatible BIOS version. This value must match the value stored in the BIOS.

The ZTIBIOSCheck.xml file contains the source for a script (ZTIBIOS_Extract_Utility.vbs) that can help you extract the attributes listed in Table 14.

To use the ZTIBIOS_Extract_Utility.vbs utility to extract attributes on a target computer

  1. Start Notepad.

  2. Copy the script source from ZTIBIOSCheck.xml file into Notepad.

  3. Save the script source in Notepad as ZTIBIOS_Extract_Utility.vbs.

  4. Run ZTIBIOS_Extract_Utility.vbs on a target computer that has an incompatible BIOS.

  5. Update ZTIBIOSCheck.xml to include the BIOS based on the attributes retrieved in the previous steps.

Modifying the Task Sequence for a Build

You can modify the sequence to tasks performed for each build that you define in Deployment Workbench. The Task Sequencer used by BDD 2007 runs this task sequence. The task sequence information is stored in the distribution_point\build_id\TS.xml file (where distribution_point is the name of the folder that is the root of the distribution point and build_id is the name of the Build ID listed in Deployment Workbench). You can specify a unique task sequence for each build defined in Deployment Workbench.

Through Deployment Workbench, you can:

  • Add new tasks.

  • Modify existing tasks.

  • Remove existing tasks.

  • Change the sequence of tasks.

  • Group one or more tasks together.

  • Specify conditions for running a task.

Note   Although you can directly modify the TS.xml file, it is recommended that you modify the task sequence by using Deployment Workbench.

To modify the task sequence for a build

  1. Start Deployment Workbench.

  2. In the console tree, navigate to Builds.

  3. In the details pane, right-click build (where build is the build whose task sequence you want to modify), and then click Properties.

  4. Click the Task Sequence tab, and modify the task sequence by performing the appropriate actions in Table 15.

    Table 15. Actions to Modify the Task Sequence of a Build

    Action

    Step

    Add a new task

    Click Add, and then click Task

    Add a new group

    Click Add, and then click Group.

    Add a reboot step

    Click Add, and then click Reboot.

    Add an application to be installed

    Click Add, click Application, and then click name (where name is the name of the application that you want to install).

    Remove an existing task

    Click task (where task is the task that you want to remove), and then click Remove.

    Remove a group

    Click group (where group is the group that you want to remove), and then click Remove.

    Note   Removing a group removes all tasks and groups within the group.

    Remove a reboot step

    Click reboot (where reboot is the reboot step that you want to remove), and then click Remove.

    Remove an application to be installed

    Click application (where application is the application that you want to remove), and then click Remove.

    Change the sequence

    Click item (where item is the task, group, reboot step, or application that you want to move to earlier or later in the sequence), and then click direction (where direction is Up or Down, with Up causing the item to occur earlier in the sequence, and Down causing the item to occur later in the sequence).

    Modify the properties of a group

    Click group (where group is the name of the group you want to modify), click the Properties tab, and then modify the following boxes as appropriate:

    • Name. User-friendly name to be associated with the group.

    • Description. Text to describe the purpose of the group.

    Modify the properties of a task

    Click task (where task is the name of the task you want to modify), click the Properties tab, and then modify the following boxes as appropriate:

    • Name. User-friendly name to be associated with the group.

    • Description. Text to describe the purpose of the task.

    • Command line. The program to be run by the task, including any parameters.

    • Start in. The default folder in which to run the program specified in the Command line box.

    Modify the options of a group

    Click group (where group is the name of the group you want to modify), click the Options tab, and then modify the following boxes as appropriate:

    • Disable this step. If you select this box, all the tasks within the group are disabled.

    • Continue on error. If you select this box, all the tasks within the group continue to run if a task encounters an error.

    • Conditions. Add criteria for determining when the group of tasks should (or should not) be run. You can use the Add, Remove, and Edit buttons to modify the conditions under which the group of tasks is run. The criteria can be based on:

      • An IF statement.

      • A task sequence variable.

      • The version of the target operating system.

      • A WMI Query Language (WQL) within a WMI namespace.

        Note   Any conditions you configure for a group affect all the tasks within a group.

    Modify the options of a task

    Click task (where task is the name of the task you want to modify), click the Options tab, and then modify the following boxes as appropriate:

    • Disable this step. If you select this box, all the tasks within the group are disabled.

    • Success codes. List of the return codes from the program (specified in the Command line box) that indicate the program completed successfully.

    • Continue on error. If you select this box, all the tasks within the group continue to run if a task encounters an error.

    • Conditions. Add criteria for determining when the group of tasks should (or should not) be run. You can use the Add, Remove, and Edit buttons to modify the conditions under which the group of tasks is run. The criteria can be based on:

      • An IF statement.

      • A task sequence variable.

      • The version of the target operating system.

        A WQL within a WMI namespace.

  5. When you are finished modifying the task sequence, click OK.

For LTI, any applications that you install during the deployment process cannot reboot the computer during the installation process. If the installation process for the application reboots the computer, the Task Sequencer returns a failure code, and the deployment process terminates. For instances when you need to reboot the computer use the Reboot task in Task Sequencer instead of allowing the application installation process to perform a reboot.

For ZTI, no restarts are allowed.

Caution   Do not allow an application to restart the computer. BDD 2007 must control restarts, or the Task Sequence will fail. Use the command-line property REBOOT=REALLYSUPPRESS to prevent some Windows Installer–based applications from restarting, for example. You can cause BDD 2007 to restart the computer after installing an application by selecting the Reboot the computer after installing this application check box in the Application Properties dialog box of the Deployment Workbench as described in “Appendix B: Configuring the Distribution Share” in the Computer Imaging System Feature Team Guide.

Selecting the Driver Groups Included in a Build

For each build that you create in Deployment Workbench, you can select a driver group to be deployed with the build. A driver group is a logical grouping of one or more drivers defined in the Out-of-Box Drivers node in Deployment Workbench.

When you select the driver group for a build, the drivers are automatically copied to the deployment point and are available to the BDD 2007 deployment scripts. The drivers are stored in the distribution_point\Out-of-Box Drivers\driver folder (where distribution_point is the name of the folder that is the root of the distribution point and driver is the name of the driver listed in Deployment Workbench).

To select the drivers group for a build

  1. Start Deployment Workbench.

  2. In the console tree, expand Distribution Share and click Builds.

  3. In the details pane, right-click build_id, and then click Properties (where build_id is the ID of the build for which you want to select a driver group).

  4. In the build_id Properties dialog box, in the Driver group box, select driver_group, and then click OK (where build_id is the ID of the build for which you want to select a driver group and driver_group is the name of the driver group you want to select).

    Note If you want to deploy all drivers with a build, in the Driver group box, select All Drivers.

Updating Deployment Processing Rules

After you update CustomSettings.ini, you need to ensure the updated version is included in your images. For ZTI, the images created by the SMS OSD Feature Pack must be updated. For LTI, the images created by Deployment Workbench need to run the Configure DB Wizard each time updates are made.

Updating the Deployment Points

Each time changes are made in Deployment Workbench, update the corresponding deployment points in Deployment Workbench. Doing so ensures that all images and deployment configuration files contain the modifications.

To update the deployment points

  1. Start Deployment Workbench.

  2. In the Deployment Workbench console, in the console tree, expand Deploy, and then click Deployment Points.

  3. In the details pane, right-click deployment_point (where deployment_point is the name of the deployment point to update), and then click Update.

    The Update Deploy Point dialog box appears and indicates the progress for updating the deployment point. The dialog box closes when the process is complete.

  4. Close all open windows.

Note   Use the Update (files only) option instead of the Update option (as shown above in step 3). The primary difference between the two options is that Update (files only) does not regenerate the .iso or .wim file containing Windows PE. All other updates are performed.

Updating the SMS OSD Feature Pack Image

Each time you update the CustomSettings.ini file for ZTI, update the corresponding SMS OSD Feature Pack images.

Note   You do not need to perform this step for LTI.

For each SMS OSD Feature Pack image that you need to update, perform the following steps:

  1. Copy the modified CustomSettings.ini file to \\servername\ZTI (where servername is the name of the server hosting the shared folder).

  2. On the SMS site server or client computer on which you installed the SMS OSD Feature Pack, start the SMS Administrator Console.

  3. In the SMS Administrator Console, browse to OSDPackage (where OSDPackage is the name of the SMS OSD Feature Pack image that you want to update).

  4. Right-click OSDPackage, point to All Tasks, and then click Update Operating System Package Files (where OSDPackage is the name of the SMS OSD Feature Pack image that you want to update).

  5. Right-click OSDPackage, point to All Tasks, and then click Update Distribution Points (where OSDPackage is the name of the SMS OSD Feature Pack image that you want to update).

  6. Close the SMS Administrator Console.

Updating Customized Version of Windows PE the SMS OSD Feature Pack

Each time you update the Microsoft Windows Preinstallation Environment (Windows PE) 2004 or Windows PE 2005 configuration for ZTI (on the Windows PE 2004/2005 tab of the deployment point property sheet), update the customized version of Windows PE for the SMS 2003 OSD Feature Pack. After you have updated the distribution point, complete the steps in the following sections:

  • “Importing the Customized Version of Windows PE Into the SMS OSD Feature Pack” in Zero Touch Installation Guide

  • “Creating the SMS OSD Feature Pack Operating System Installation CD” in Zero Touch Installation Guide

Download

Get the Microsoft Solution Accelerator for Business Desktop Deployment 2007

Update Notifications

Sign up to learn about updates and new releases

Feedback

Send us your comments or suggestions