If you accept the default names, Setup creates the package named Microsoft Updates Tool and a package named Windows Update Agent.

Important
If you are reinstalling the Configuration Manager 2007 Inventory Tool for Microsoft Updates, use the same package names. Before the client installs any software update, it runs the scan tool first. If the name of the inventory tool package has changed, packages previously created by the Deploy Software Updates Wizard will use the obsolete inventory tool package, resulting in incorrect results.

The Microsoft Updates Tool package always obtains its source files from the PkgSource directory. The package does not update distribution points on a schedule because the synchronization host automatically updates the distribution points with new catalogs as needed.

Note
Do not rename the packages or move the package source folder after installation. Doing so will cause the inventory scans to fail.

Setup can automatically configure the package to be copied to all distribution points in the site and to all child sites. If you prefer to limit the distribution points that contain the inventory tool package, you can manually configure the distribution points for the Microsoft Updates Tool package after Setup is complete.

Setup creates the following programs to run the inventory tool on the SMS client computers:

• Microsoft Updates Tool. This program runs the following command line: ScanWrapper.exe /Extended /cache.
  
  
• Microsoft Updates Tool (expedited). This program runs the following command line: ScanWrapper.exe/Extended/cache/kick.
  
  

Note

The /kick switch causes hardware inventory to be collected immediately after running the scan tool. This allows timelier reporting of which software updates are and are not applied. Use care when running /kick in a production environment. The first time the expedited program runs, it might cause significant network traffic, even if clients are generating only delta hardware inventory. If the expedited program runs regularly, the network impact should decrease.

Both programs share the following property settings:

• Run hidden.
  
  
• Do not reboot the computer after running.
  
  
• Can run only on Windows XP, Windows Server 2003, Windows 2000 Service Pack 3, and Windows 2000 Service Pack 4.
  
  
• Can run whether or not a user is logged on.
  
  
• Run with administrative rights.
  
  
• Suppress program notifications.
  
  
• Runs the Windows Update Agent program and package first.
  
  

During Setup, you have the option to create an advertisement called Microsoft Updates Tool to send the Microsoft Updates Tool package and program to the Microsoft Updates Tool collection. By default, the advertisement is scheduled to recur every seven days, effective as soon as the object is created. Advanced Clients will download the program from either a local distribution point (if available) or a remote distribution point (if no local distribution point is available) and then run the program from the cache. Changing this program to run directly from a distribution point is not recommended. For more information about the cache, see Microsoft Knowledge Base article 839513 at the Microsoft Help and Support site (http://go.microsoft.com/fwlink/?linkid=46676).

Setup can create the following collections to assist you in testing and deploying the Microsoft Updates Tool package to your SMS clients:

• Microsoft Updates Tool (pre-production)
  
  
• Microsoft Updates Tool
  
  

These collections are created only if you choose to have Setup create an advertisement for the package. If Setup creates the advertisement and the collections, you have the option to designate an Advanced Client to use as a test computer. The computer must have the SMS Advanced Client already installed, and it must belong to a collection that you can read with the account you are logged on with while running Setup. Setup adds the test computer to the Microsoft Updates Tool (pre-production) collection.

• The Microsoft Updates Tool collection has one query-based membership rule to include all operating systems where the version is greater than or equal to 5.0.2195, which evaluates to all computers that are running Windows 2000, Windows XP, or Windows Server 2003. However, because the default query rule properties limit the Microsoft Updates Tool collection to the Microsoft Updates Tool (pre-production) collection, the effective membership after Setup completes includes only the single test computer. This ensures that initially the Configuration Manager 2007 Inventory Tool for Microsoft Updates runs only on the known test computer. After you have completed your tests, you can remove the collection limiting option and the Inventory Tool for Microsoft Updates will automatically be distributed to all computers that are capable of running the inventory tool.
  
  

For more information about managing the collections created by Setup, see the Managing Collections section later in this guide.