The Create Update Wizard guides you though the creation of a new custom software update. The following procedures provide detailed steps on starting and using the wizard.

To view detailed descriptions for configuration options when on a page in the Create Update Wizard, press F1. For more information about the Create Update Wizard and the configuration options on each wizard page, see Create/Modify Update Wizard.

To start the Create Update Wizard

  1. In the Custom Updates Publishing Tool console, select the Custom Updates Publishing Tool repository, vendor, or product node in the tree pane.

  2. Start the Create Update Wizard by performing one of the following actions:

    1. Right-click the node, and then click Create Update.

    2. On the Action menu item, click Create Update.

    3. In the Action pane, click Create Update.

To use the Create Update Wizard

  1. On the Update Information page, configure the following custom update information:

    • Update Title: Enter the name of the custom update. This is a required field.

    • Description: Enter the description of the custom update. This is a required field.

    • Classification: Select a classification type from the drop-down list. You can select from the following values: Critical Updates, Feature Packs, Updates, Security Updates, Service Packs, Hotfixes, Tools, and Update Rollups. This is a required field.

    • Bulletin ID: Enter the bulletin ID for the custom update. This is an optional field.

    • Vendor: Enter the vendor name for the custom update. If the Create Update Wizard is started from the Vendor or Product node, this value is pre-populated. This is a required field.

    • Product: Enter the product name for the custom update. If the Create Update Wizard is started from the Product node of the console, this value is pre-populated. This is a required field.

  2. Click Next.

  3. On the Extended Properties page, configure the following properties for the custom update:

    • Article ID: Enter the article ID for the custom update. This is an optional field.

    • CVE ID: Enter the Common Vulnerability and Exposures (CVE) ID that provides the security information about the custom update. This is an optional field.

    • Severity: Select a severity type from the drop-down list. You can select from the following values: None (default), Critical, Important, Moderate, and Low. This is a required field when selecting the Security Updates classification on the previous page. For all other custom update classifications, this is an optional field.

    • Support URL: Enter the URL that provides support information about the custom update. This is an optional field.

    • More Info URL: Enter the URL that provides more information about the custom update. This is a required field.

    • Impact: Select an impact category from the drop-down list. You can select from the following values: Normal (default), Minor, and Requires Exclusive Handling. This is an optional field.

    • Reboot Behavior: Select the reboot behavior from the drop-down list. You can select from the following values: Never reboots, Always requires reboot, and Can request reboot (default). This is an optional field.

    Click Next.

  4. On the Define Prerequisite Rules page, provide the higher-level rules used as an initial check to determine whether the custom update is needed on the client, and then click Next. Providing the prerequisite rules is optional.

  5. On the Select Package page, configure the following package properties:

    • Installer Type: Select the type of installation required for the custom update from the drop-down list. You can select from the following values: Command Line Installation (.exe), Windows Installer File (.msi), and Windows Installer Patch (.msp). This is a required field.

    • Update Package Source: Enter or browse to the path for where the custom update is created. The source path must be on the local drive. This is a required field.

    • Download URL: Enter the URL or UNC path to the publish location for the custom update. This is a required field.

    • Binary Language: The wizard detects the language from the Update Package Source file for Command Line Installation (.exe) and Windows Installer File (.msi) custom updates and automatically populates the language field. For Windows Installer Patch (.msp) type files, you must select the language for the custom update from the drop-down list. This is a required field.

    • Success Return Codes: The wizard detects the success return codes for Windows Installer File (.msi) and Windows Installer Patch custom updates and automatically populates the Success Return Codes field. For Command Line Installation (.exe), you must specify the success return codes for the custom update. This is an optional field.

    • Success Pending Reboot Codes: The wizard detects the success pending reboot codes for Windows Installer File (.msi) and Windows Installer Patch custom updates and automatically populates the Success Pending Reboot Codes field. For Command Line Installation (.exe), you must specify the success pending reboot codes for the custom update. This is an optional field.

    • Command line (quiet): The wizard detects the command-line arguments for a quiet custom update installation (unattended setup with no user intervention) for Windows Installer File (.msi) and Windows Installer Patch custom updates and automatically populates the Command line (quiet) field. For Command Line Installation (.exe), you must specify the command-line arguments for the custom update. This is an optional field.

    Click Next.

  6. On the Define Applicability Rules page, define the rules used to determine whether the software update is applicable to a specific client. The applicability rules are optional, but to retrieve accurate reporting results about whether the custom update is applicable on clients, at least one rule must be defined. Click Next.

  7. On the Define Installed Rules page, define the rules used to determine whether the custom update is already installed on the client. The installed rules are optional, but the custom update can not be published until at least one installed rule is defined.

  8. On the Summary page, which displays a summary of the configured properties for the custom update, click Next to create the update.

    The Progress page displays the status and progress while creating the custom update.

  9. The Confirmation page displays a summary of the configured properties for the custom update that was created. If an error occurred during the custom update creation process, the error message displays in the properties pane. Click Close to exit the wizard.

    Note
    If an error occurs during the custom update creation process, review the PublishingTool.log file, located in %USERPROFILE%\Local Settings\Temp, for more information.

See Also