Article ID: 953592 - View products that this article applies to.
The Custom Updates Publishing Tool is available in Microsoft Systems Management Server (SMS) 2003 R2. However, you cannot use this tool to author or publish software updates that are available in the Microsoft Update Standalone Package file type. The Microsoft Update Standalone Package file type has an .msu extension.
When you run the Create Update Wizard or the Modify Update Wizard, no option is available for the .msu file type in the Installer Type list.
Note Software updates for Windows Vista and for Windows Server 2008 are only available in the .msu file type.
This problem occurs because the current version of the Custom Updates Publishing Tool only supports custom updates that are available in the following file types:
Download informationThe following file is available for download from the Microsoft Download Center:
Download the R2MSUSupportEN.exe package now.
Collapse this imageExpand this image
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
(http://support.microsoft.com/kb/119591/ )How to obtain Microsoft support files from online services
PrerequisitesTo apply this hotfix, you must be running Systems Management Server 2003 R2 on the computer.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other previously released hotfixes.
Hotfix installation instructionsTo apply this hotfix, follow these steps:
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Systems Management Server 2003 R2
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
New options that are introduced by this hotfixThe Custom Update Publishing Tool is updated to support the Microsoft Update Standalone Package (.msu) file type. A Microsoft Update Standalone Package (.msu) option is added into the Installer Type drop-down list in the Create Update Wizard and in the Modify Update Wizard.
Additionally, the following rules are added as saved rules and are available when you select the Use existing rule option when an update is created or modified:
How to deploy an update by using the .msu file typeHow to deploy an update by using the .msu file type resembles how to deploy an update by using the .exe file type. This is true because both operations can use the basic rules that already exist. You can use basic rules to test for specific file versions of the updated files in the update package. The file versions for each update are documented in the corresponding Knowledge Base article. Or, you can use the Expand command to extract the updated files from the update package. To extract files from an .msu file, first extract a CAB package from the .msu file, and then extract the updated files from the CAB package. For example, you can run the following commands at a command prompt:
expand -F:* MSU_File_Name.msu MSUFolderFor more information about how to use the Expand command to extract files form an .msu file, click the following article number to view the article in the Microsoft Knowledge Base:
expand -F:* Extracted_CAB_Name.cab MSUFolder
928636We recommend that you target the software update to the appropriate clients by using the new rules that are added for Windows Vista and for Windows Server 2008.
(http://support.microsoft.com/kb/928636/ )You cannot extract the contents of a Microsoft Update Standalone Package for Windows Vista
Hotfix 953591 is required to fully support the .msu file typeFor the InstallPatch program on SMS clients to support the .msu file type, you must deploy hotfix 953591 on all SMS clients that are running Windows Vista or Windows Server 2008. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
953591If hotfix 953591 is not applied to Windows Vista-based or to Windows Server 2008-based clients, updates of the .msu file type cannot be applied, and the update distribution fails. Even if hotfix 953591 is installed, updates of the .msu file type cannot be applied on client computers that are running operating systems other than Windows Vista or Windows Server 2008. When the update distribution fails, the software update Web reports display the Distribution State as Failed. Additionally, an error code 193 is logged in the PatchInstall.log file on the client computer.
(http://support.microsoft.com/kb/953591/ )You cannot use the PatchInstall.exe program to install custom updates of the .msu file type on some Systems Management Server 2003 clients
The situation where hotfix 953592 is not appliedYou can import catalog updates that include updates of the .msu file type to the Custom Updates Publishing Tool even if the current hotfix (953592) is not applied. However, you cannot modify the .msu files because the Custom Updates Publishing Tool does not recognize the .msu file type. Although the update cannot be modified, the update catalog that contains the .msu files can still be published, exported, and synchronized with the site server.
Code 3017 in the "Success Pending Reboot Codes" fieldBy default, the Success Pending Reboot Codes field for .msu file type is 3017. Code 3017 corresponds to the following description: If the installation program returns a code 3017, clients receive a Software Updates Installation notification that requests the computer to restart. The software update Web reports display the Distribution State as Reboot Pending. After the client computer restarts, the system rolls back the changes.
You can choose to remove code 3017 from the Success Pending Reboot Codes field. In this case, clients will not receive the Software Updates Installation notification that requests the computer to restart. The software update Web reports display the Distribution State as Failed instead of Reboot Pending. In either case, the Distribution State shows the appropriate state after the next scan, and the Complaint field is not checked.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates