How to Edit a Software Update

  • [アーティクル]

Applies To: System Center 2012 Configuration Manager, System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2, System Center Essentials 2010

Use these procedures to edit a software update. The first procedure in this topic describes how to start the Edit Software Update Wizard, and the following procedures describe what you can edit on each page of the wizard.

To start the Edit Software Update Wizard

  1. In the Updates Publisher 2011 console, click Updates. The workspace is displayed at the bottom of the navigation pane in the console.

  2. Locate the software update that you want to edit by using the following methods:

    • Click All software updates to display all the software updates in the Updates Publisher 2011 repository.

    • Click a manufacturer folder to see only those software updates that are related to the manufacturer.

    • Click a product folder to see only those software updates that are related to a product of a manufacturer.

    • Use Search to list only those software updates that include the search term.

  3. Select the software update that you want to edit, and then click Edit.

The Edit Software Update Wizard is now displayed in the Updates Publisher 2011 console. The following procedures describe what you can edit on each page of the wizard.

Package Information Page

This page specifies information such as the location of the package file, the location where the software update will be downloaded, and other optional information.

Important

You cannot change the package information for a software update once the software update is published.

To edit Package Information

  1. If you are not on the Package Information page, click Package Information to display the page.

  2. Click Browse to find the location of the software update package. You cannot enter the location of the package directly into the Package source box.

    Important

    After a software update has been published, you cannot change the Package Source box. If the package source is changed, Updates Publisher 2011 skips the software update when you attempt to publish it again.

  3. To use a local folder for the content of the software update, select the Use local content source for publishing check box. By default, Updates Publisher 2011 searches through the MyDocuments\LocalSourcePublishing folder for local source content.

    Important

    Updates Publisher 2011 can use the MyDocuments\LocalSourcePublishing folder, or you can specify a custom folder for local source content. For information about how to specify a custom folder, see Advanced Options.

  4. In the Download URL (or UNC) box, enter a URL (or UNC) to use a remote location for the content of the software update. The location is not verified in the wizard, but it must be accessible before the software update is published to the update server.

  5. In the Binary language box, select the language of the software update file. For command-line installation types, select the language of the software update file from the drop-down list.

  6. In the Success return codes box, specify the codes that are returned when the software update is successfully installed. Using success return codes allows you to get information on the number of software update installations that are successful. Windows Installer files and Windows Installer patch types automatically populate the Success return codes box. Separate multiple return codes using a comma.

    Important

    This setting is disabled for Windows Installer File (.msi) and Windows Installer Patch (.msp) software updates because the return codes are predefined in these file types.

    Important

    For EXE based software updates, if no return codes are specified the default codes definded by the EXE are used.

  7. In the Success pending reboot codes box, specify the code that is returned when the software update is successfully installed and a system restart is pending. Using success pending reboot return codes allows you to get information on the number of successful software update installations that require a system restart. Windows Installer files and Windows Installer patch types automatically populate the Success pending reboot codes box.

    Important

    This setting is disabled for Windows Installer File (.msi) and Windows Installer Patch (.msp) software updates because the return codes are predefined in these file types.

    Important

    For EXE based software updates, if no return codes are specified the default codes defined by the EXE are used.

  8. In the Command line box, specify the command-line arguments that are required to install the software update. Windows Installer files and Windows Installer patch types automatically populate the Command line box.

    For Windows Installer File (.msi) and Windows Installer Patch (.msp) software updates, the command-line arguments must be specified in the [name]=[value] format. In addition, /qn or any other / options are not supported for MSI/MSP software updates. For software updates based on an .exe file, all arguments are valid.

  9. To apply these settings, click Summary. For more information, see Summary and Confirmation pages.

Required Information Page

This page specifies information that is required to add the software update to the Updates Publisher 2011 repository so that it can be published or exported, such as the name of the software update, a description of the software update, and the classification of the software update. Classifications include a critical update, feature pack, update, security update, tool, and update rollup.

To edit Required Information

  1. If you are not on the Required Information page, click Required Information to display the page.

  2. Specify titles and descriptions for the software update. You can specify a title and description for each language listed in the Language box.

    Note

    Updates Publisher 2011 supports only those languages available in the Language box.

    1. In the Language box, select the language of the title and description.

    2. In the Title box, enter the name of the software update. The name of the software update is displayed in the Updates workspace.

    3. In the Description box, enter a description of the software update. The description could include what is installed by the software update and why or when it should be used.

    4. Repeat this step for each language that you want to supply.

  3. In the Classification box, select the classification of the software update. The following values are available from the drop-down menu.

    • Critical Update: Specifies a broadly released update for a specific problem that addresses a critical bug that is not related to security.

    • Feature Pack: Specifies new product features that are distributed outside of a product release and are typically included in the next full product release.

    • Update: Specifies an update to an application or file that is currently installed.

    • Security Update: Specifies a broadly released update for a product-specific issue that is related to security.

    • Service Pack: Specifies a cumulative set of hotfixes that are applied to an application. These hotfixes can include security updates, critical updates, software updates, and so on.

    • Tool: Specifies a tool or feature that helps complete one or more tasks.

    • Update Rollup: Specifies a cumulative set of hotfixes that are packaged together for easy deployment. These hotfixes can include security updates, critical updates, updates, and so on. An update rollup generally addresses a specific area, such as security or a product feature.

  4. In the Vendor box, select or enter the vendor of the software update. Updates Publisher 2011 provides the names of those vendors whose software updates are already in the Updates Publisher 2011 repository, including vendors for software updates that you created.

    Important

    The following terms cannot be used when specifying a vendor:

    • Microsoft Corporation or Microsoft

    • Update or Software Update

    • Tools or Tool

    • Critical or Critical Updates

    • Security or Security Updates

    • Feature Pack

    • Update Rollup

    • Service Pack

    • Driver or Driver Update

    • Bundle or Bundle Update

  5. In the Product box, select or enter the type of product that is updated by the software update. Updates Publisher 2011 provides the products that have software updates in the Updates Publisher 2011 repository.

    Important

    The following terms cannot be used when specifying a product:

    • Microsoft Corporation or Microsoft

    • Update or Software Update

    • Tools or Tool

    • Critical or Critical Updates

    • Security or Security Updates

    • Feature Pack

    • Update Rollup

    • Service Pack

    • Driver or Driver Update

    • Bundle or Bundle Update

  6. In the More Info URL box, enter the URL where the user can get more information about the software update. You must use lowercase characters when specifying “http” or “https” in the URL.

  7. To apply these settings, click Summary. For more information, see Summary and Confirmation pages.

Optional Information Page

This page specifies general information about the software update, such as bulletin, article, and Common Vulnerabilities and Exposures (CVE) identifiers, a support URL, and the restart behavior when the software update is installed.

To edit Optional Information

  1. If you are not on the Optional Information page, click Optional Information to display the page.

  2. If a software update bulletin is available, in the Bulletin ID box, enter the identifier of the bulletin. Software update bulletins provide additional information about the update, and they are usually provided with Microsoft security software updates. Other vendors occasionally provide software update bulletins.

  3. If a software update article is available, in the Article ID box, enter the identifier of the article. Software update articles contain more information about the software update.

  4. If CVE identifiers are available, in the CVE ID box, enter the CVE identifiers separated by a semicolon. For example CVE1;CVE2. CVEs provide security information about the software update bundle.

  5. In the Support URL box, enter the URL to where support information for the software update is available. You must use lowercase letters when specifying “http” or “https” in the Support URL box.

  6. In the Severity box, select the severity of updating the software. This is required for security updates, and it is optional for all other categories of software updates. The following values are available from the drop-down menu: None, Critical, Important, Moderate, and Low.

  7. In the Impact box, select the impact of updating the software. The following values are available from the drop-down menu:

    • Normal: Specifies that the software update requires only typical installation procedures. This is the default value.

    • Minor: Specifies that the software update requires minimal installation procedures.

    • Require Exclusive Handling: Specifies that the software update must be installed exclusively from any other updates.

  8. In the Restart behavior box, select the restart behavior of the computer where the software update is installed. This setting is only informational and does not affect how the target computer is restarted when the software update is installed. The following values are available from the drop-down menu:

    • Never reboots: Indicates that the computer never performs a system restart after installing the software update.

    • Always requires reboot: Indicates that the computer always performs a system restart after installing the software update.

    • Can request reboot: Indicates that the computer requests a system restart, only if necessary, after installing the software update. The user has the option to postpone the restart by answering No to the restart request. This is the default value.

  9. To apply these settings, click Summary. For more information, see Summary and Confirmation pages.

Prerequisite Updates page

This page specifies which software updates and detectoids must be installed on the target computer before this software update can be installed. A detectoid is a high-level rule, such as a rule that the CPU of the target computer must be a 64-bit processor. You can specify that specific software updates and detectoids must be installed, or you can specify that at least one software update or detectoid from a group of software updates and detectoids must be installed.

Important

Whenever possible, use built in or well-known WSUS detectoids instead of defining installable rules that perform the same action.

To edit prerequisite updates and detectoids

  1. If you are not on the Prerequisite Updates page, click Prerequisite Updates to display the page.

  2. Select a software update or detectoid that must be installed, and then click Add Prerequisite. Notice that Updates Publisher 2011 adds a group to the Prerequisites list that contains the software update that you selected. All software updates that are added to the list are added in groups. Repeat this step for every software update or detectoid that must be installed.

  3. Select the software updates or detectoids that you want to include as a group where at least one of the software update or detectoid must be installed, and then click Add Group. Notice that Updates Publisher 2011 adds all the software updates and detectoids in the group to the Prerequisites list.

  4. You can remove groups or individual software updates and detectoids from the Prerequisites list.

    • To remove a group, including a group that contains a single software update or detectoid, select the group, and then click Remove Group.

    • To remove a single software update or detectoid from a group that contains multiple software updates or detectoids, click Remove Prerequisite.

  5. To apply these settings, click Summary. For more information, see Summary and Confirmation pages.

Superseded Updates Page

This page specifies which software updates are superseded by this update. When this software update is published, Configuration Manager marks all the software updates that you specify on this page as ”Expired”.

To edit Superseded Updates

  1. If you are not on the Superseded Updates page, click Superseded Updates to display the page.

  2. Select the software updates that you want to add from the Available software updates list, and then click Add Update. This adds the software updates to the Superseded software updates list.

  3. To remove a software update from the Superseded software updates list, select the software updates to remove, and then click Remove Update.

  4. To apply these settings, click Summary. For more information, see Summary and Confirmation pages.

Installable Rules Page

This page adds a set of applicability rules to the software update that are used to determine whether the software update must be installed. You can add rules to this rule set, edit the rules in the set, add logical operators to change the behavior of how the rules are applied, remove rules, and you can save rules for use in other software updates.

Important

Whenever possible, use built in or well-known WSUS detectoids instead of defining installable rules that perform the same action. For information on specifying detectoids, see Prerequisite Updates page.

To edit Installable Rules

  1. If you are not on the Installable Rules page, click Installable Rules to display the page.

  2. Use the Rule Editor to define the rules that determine if the software update should be installed. You can perform the following actions:

    • To add rules to the rule set, click Create. You can add rules that are associated with files, registry keys, Windows operating systems, Windows Installer, and rules that you have already saved. For information about how to add these types of rules, see How to Create Applicability Rule Sets.

    • To edit a rule, select the rule, and then click Edit. For information about how to edit rules, see How to Edit Applicability Rule Sets.

    • To delete a rule or a logical operator, select the item that you want to remove, and then click Delete.

    • To add a logical And operator, click And. The Rule Editor adds a logical And operator to the end of the rule set. After the operator is added, you can move it by using Move Up or Move Down.

    • To add a logical Or operator, click Or. The Rule Editor adds a logical Or operator to the end of the rule set. After the operator is added, you can move it by using Move Up or Move Down.

    • To switch between logical operators, select the operator, and then click Toggle.

    • To specify or remove a Not rule, select the rule, and then click Not.

    • To move a rule or a group of rules in a logical operator so that it is applied earlier in the rule set, select the rule or logical operator, and then click Move Up. This is helpful when you are adding logical operators to your rule set. The rules in the rule set are applied in the order that they are listed.

    • To move a rule or a group of rules in a logical operator so that it is applied later in the rule set, select the rule or logical operator, and then click Move Up. This is helpful when adding logical operators to your rule set. The rules in the rule set are applied in the order that they are listed.

    • To save a rule so that it can be used in other rule sets, click Save.

  3. To apply these settings, click Summary. For more information, see Summary and Confirmation pages.

Installed Rules Page

This page adds applicability rules to the software update that are used to verify whether the software update is already installed on the computer. You can add rules to this rule set, edit the rules in the set, add logical operators to change the behavior of how the rules are applied, remove rules, and you can save rules for use in other software updates.

Important

Whenever possible, use built in or well-known WSUS detectoids instead of defining installable rules that perform the same action. For information on specifying detectoids, see Prerequisite Updates page.

To edit Installed Rules

  1. If you are not on the Installed Rules page, click Installed Rules to display the page.

  2. Use the Rule Editor to define the rules that determine if the software update should be installed. You can perform the following actions:

    • To add rules to the rule set, click Create. You can add rules that are associated with files, registry keys, Windows operating systems, Windows Installer, and rules that you have already saved. For information about how to add these types of rules, see How to Create Applicability Rule Sets.

    • To edit a rule, select the rule, and then click Edit. For information about how to edit rules, see How to Edit Applicability Rule Sets.

    • To delete a rule or a logical operator, select the item that you want to remove, and then click Delete.

    • To add a logical And operator, click And. The Rule Editor adds a logical And operator to the end of the rule set. After the operator is added, you can move it by using Move Up or Move Down.

    • To add a logical Or operator, click Or. The Rule Editor adds a logical Or operator to the end of the rule set. After the operator is added, you can move it by using Move Up or Move Down.

    • To switch between logical operators, select the operator, and then click Toggle.

    • To specify or remove a Not rule, select the rule, and then click Not.

    • To move a rule or a group of rules in a logical operator so that it is applied earlier in the rule set, select the rule or logical operator, and then click Move Up. This is helpful when adding logical operators to your rule set. The rules in the rule set are applied in the order that they are listed.

    • To move a rule or a group of rules in a logical operator so that it is applied later in the rule set, select the rule or logical operator, and then click Move Up. This is helpful when adding logical operators to your rule set. The rules in the rule set are applied in the order that they are listed.

    • To save a rule so that it can be used in other rule sets, click Save.

  3. To apply these settings, click Summary. For more information, see Summary and Confirmation pages.

Summary and Confirmation pages

Use the Summary page to validate the setting you specified for the software update and the Confirmation page to validate that Updates Publisher 2011 created the software updates as you requested.

To view and confirm the software update

  1. If you are not on the Summary page, click Summary to display the page.

  2. Review the information on this page to ensure that the settings for the software update are correct.

    To go back and change a setting, click Previous, or select the page where the setting is specified.

  3. To accept the settings and to start creating the software update, click Next.

  4. Updates Publisher 2011 displays a Progress page while it is creating the software update, and then displays a Confirmation page that shows the details of the created software update.

  5. Click Close to exit the Edit Software Update Wizard.

See Also

Concepts

Managing Software Updates