Requirements of the /qn switch are different for the Inventory Tool for Custom Updates in Systems Management Server 2003 R2 and for System Center Updates Publisher when you import software update catalogs
This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
You use the Inventory Tool for Custom Updates (ITCU) in Microsoft Systems Management Server (SMS) 2003 R2 and System Center Updates Publisher (SCUP) to import software update catalogs.
You use Windows Software Update Services (WSUS) and System Center Configuration Manager 2007 to deploy software updates.
You prepare the software update catalogs that you want to import.
In this scenario, you have to prepare different catalogs for ITCU and for SCUP if Microsoft Windows Installer (MSI) packages or Windows Installer update (MSP) packages are used for deployment. Specifically, you must include a /qn switch in the command line when you prepare catalogs for MSI packages and MSP packages that will be used by ITCU. However, when you prepare catalogs for MSI packages and MSP packages that will be used by SCUP, you do not have to include a /qn switch in the command line.
This behavior may cause various problems, depending on the versions of ITCU and SCUP that you use.
ITCU and SCUP impose different requirements of the /qn switch for MSI packages and for MSP packages. The /qn switch is required for ITCU. However, the /qn switch is not required for SCUP.
After you apply this hotfix, ITCU will automatically add a /qn switch in the command line for MSI packages and for MSP packages during the importing process if a /qn is not present in the catalog file.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To apply this hotfix, you must have Systems Management Server 2003 R2 installed on the computer.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The 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.
Note Removal of this hotfix is not supported. To remove the hotfix, you have to uninstall the Custom Update Publishing Tool, and then you have to reinstall the product.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about ITCU and SCUP, visit the following Microsoft TechNet Web sites: