Note the following points when using WUA or MBSA 1.2.1 to detect patch information:

• If patch information detection using WUA fails, the Get software information from client job terminates with an error.
• Even if a database file for WUA is not stored in the client's installation directory \CLIENT\WUA, the Get software information from client job terminates normally. However, no patch information is detected.
• Even if the mbsacli.exe file and a database file for MBSA 1.2.1 are not stored in the client installation directory \CLIENT\MBSA, a Get software information from client job is terminated normally. However, unapplied patches, even if present, are not detected as unapplied patch information.
• If a patch requiring an OS restart is applied, that patch may be detected as both an applied and unapplied patch until the OS is restarted.
• Patch information that does not have an ID in the format KBxxxxxx or MSxx-xxxx cannot be collected.
• By operating the client's Package Setup Manager, you can scan the client's patch information. However, you cannot check patch information with Package Setup Manager. Additionally, no error occurs, even if the scan fails.
  To use Package Setup Manager to scan patch information, from the Execute menu in the Installed Software window, select the Collect Software Information and Update menu.
  
• To detect patch information from an offline machine, you must log on as a user with Administrator user permissions.
• To detect patch information from a client machine onto which a user without Administrator user permissions has logged, the following settings are required in the client setup:
  
  • If the client is resident, select the Run the client with non-Administrator user permissions check box on the Security page.
  • If the client is nonresident, on the Security page, choose Run the client with non-Administrator user permissions and Use the Package Setup Manager or Execute Job Backlog command when a client is not resident.
• When using WUA to detect patch information, applied patch information cannot be collected if 10 minutes are exceeded.
• If WUA is used in an environment in which updated inventory information is set to be automatically reported to the managing server, WUA checks for patch information changes when it connects to the managing server. Because patch information detection using WUA can take a long time, note the following points:
  
  • In the client setup, if the Client will poll the managing server check box on the Default Running Status/Polling page is selected, and a short polling interval is set, a large processing load may be placed on the client. To prevent this, set the polling interval as large as possible.
  • In the client setup, if the Client will poll the managing server check box on the Default Running Status/Polling page is selected, and the polling timing at the startup is set to Before the client starts, the startup of the programs registered in the Software Distribution Client Startup folder may take a long time.