In the following procedures, you install the Configuration Manager 2007 Inventory Tool for Microsoft Updates, verify that the installation was successful, and then force the client to run the inventory tool. Complete the installation procedure on your primary site server.

Note
When a Systems Management Server (SMS) 2003 site server is upgraded and a previous version of the Inventory Tool for Microsoft Updates is found, Setup automatically upgraded the tool, and when complete, initiates synchronization.

To install the Inventory Tool for Microsoft Updates

Manually run SMSITMU.msi from the Configuration Manager 2007 DVD.
When prompted, click Next.
Click I accept the license agreement, and then click Next.
Click Next to accept the default path of %\Program Files%\Microsoft Updates Inventory Tool\.
In the Synchronization host computer box, type the name of the SMS Advanced Client that will retrieve the latest Windows Update Catalog.
If the synchronization host computer will download the Windows Update Catalog from the Internet, click Next to continue and proceed to step 10.
If the synchronization host computer will obtain the Windows Update Catalog from a local source rather than directly from the Internet, click I will download the catalog and the synchronization host will copy it from a folder and then click Browse.
Open the folder that the Configuration Manager 2007 Inventory Tool for Microsoft Updates will copy the catalog from. This folder must contain Wsusscn2.cab for a manual synchronization to successfully complete.
Click Next.

When prompted to enter a name for Configuration Manager objects, use the default object name of Microsoft Updates Tool and then enter the name of an client computer as the test computer

Important
The default object name must not contain invalid characters, such as a double quote and semi-colon, or the following error occurs during the object creation when completing the wizard: Failed to create SMS Package object. (Error code: 0x80041001).

Click Next.
When prompted to create Configuration Manager objects to deploy the Windows Update Agent, click Next.
When prompted to complete installation, click Next.
After the Inventory Tool for Microsoft Updates is installed, a dialog box appears indicating the installation was successfully completed. Click Finish.

To verify successful installation of the Inventory Tool for Microsoft Updates

In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Collections.
Verify that the Microsoft Updates Tool, Microsoft Updates Tool (pre-production), Microsoft Updates Tool Sync, Microsoft Updates Tool IA64, and Microsoft Updates Tool x64 collections are created.
In the console tree, click Packages.
Verify that the Microsoft Updates Tool, Windows Update Agent x86, Windows Update Agent IA64, and Windows Update Agent x64 packages are created.
In the console tree, click Advertisements.
Verify that the Microsoft Updates Tool and Microsoft Updates Tool Sync advertisements were created.

To force the SMS 2003 Inventory Tool for Microsoft Updates to run on the synchronization host

On the computer that serves as the synchronization host, navigate to Control Panel and start Configuration Management.
Click the Actions tab.
Click Machine Policy Retrieval & Evaluation Cycle, and then click Initiate Action, which causes the client computer to request new policies, including the policy related to the advertised program.
When the Machine Policy Retrieval & Evaluation Cycle message box appears indicating the action was initiated, click OK.
When the Configuration Manager Properties dialog box appears, click OK.

To verify that the SMS client computer has successfully run the Inventory Tool for Microsoft Updates program

In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / System Status / Advertisement Status.
Click Advertisement Status, and then on the Action menu, click Refresh.
In the console tree, click Microsoft Updates Tool.
Determine that the client that has received the advertisement, started the program, and successfully completed the advertised program. Notice that two programs were started and successfully installed for each system that ran the program. This is because of the dependent program to install the Windows Update Agent.

In the details pane, right-click the local site, point to Show Messages, and then click All.

Note
When the SMS Status Message Viewer for <site code> window appears, you should see status messages with message IDs of 10002, 10005, and 10008. These status messages show that the client received, started, and successfully completed running the Inventory Tool for Microsoft Updates program for the first time. When the inventory tool runs again, the 10008 message ID will be replaced with message ID 10009. You might also notice status message 10035, which indicates that the program has not started because a request to download the content was initiated

Note

When the SMS Status Message Viewer for <site code> window appears, you should see status messages with message IDs of 10002, 10005, and 10008. These status messages show that the client received, started, and successfully completed running the Inventory Tool for Microsoft Updates program for the first time. When the inventory tool runs again, the 10008 message ID will be replaced with message ID 10009. You might also notice status message 10035, which indicates that the program has not started because a request to download the content was initiated

Close the SMS Status Message Viewer for <site code> window.
If you are not using the expedited action with the Microsoft Updates Tool (expedited) program, you should now either initiate hardware inventory on your clients or wait until the next hardware inventory cycle has completed before you check to see which updates are required and before distributing software updates to them.