The UDI Wizard provides the UI for collecting deployment settings that the UDI task sequences consume. The UDI Wizard is initiated as a part of a UDI task sequence and collects the necessary configuration information for customizing the deployment of the Windows client operating systems and applications. The wizard pages read their configuration settings from the UDI Wizard configuration file, which is customized using the UDI Wizard Designer.

The UDI Wizard is initiated by the UDI Wizard task sequence step in task sequences created using the UDI task sequence templates. The UDI Wizard task sequence step runs the UDIWizard.wsf script, which in turn initiates the UDI Wizard (OSDSetupWizard.exe). Table 9 lists the UDI Wizard command-line parameters and provides a brief description of each.

Table 9. UDI Wizard Command-Line Parameters

Parameter

Description

/preview

Allows you to preview the current configuration of the wizard by enabling the Next button, which allows you to move from page to page without requiring valid input.

/xml

Specifies the name of the UDI Wizard configuration file. The UDIWizard.wsf script automatically sets this parameter to the OSDSetupWizard.xml file, which is stored in the folder in which the task sequence stores log files. This parameter defaults to the config.xml file.

The syntax for this parameter is as follows (where <full_path> is the fully qualified path to the .xml file, including the file name and extension):

/xml:<full_path>

/stage

Specifies the name of the UDI stage to run. The UDIWizard.wsf script automatically sets this parameter to the appropriate stage, as described in UDI Stage Reference. This parameter defaults to the first stage in the UDI Wizard configuration file.

The syntax for this parameter is as follows (where <stage_name> is the name of the stage to be run):

/stage:<stage_name>

Note   The value for <stage_name> is case sensitive.

/locale

Specifies the language to use in the UDI Wizard in the form of a locale identifier (LCID), which is represented by a numeric value. For a list of the available LCIDs, see Locale IDs Assigned by Microsoft.

You would use this list to identify the language you want to use, and then provide the corresponding LCID.

The syntax for this parameter is as follows (where <locale_id> is the numeric value of the LCID to be used):

/locale:<locale_id>

 

Related Topics

UDI Concepts