ThinkVantage Technology System Information Center Scanning Tip
Published 27 March 2005, updated 28 March 2005
Authors: Byron Braswell
This technote documents a fix to the automatic System Information Gatherer scans not being uploaded to the System Information Center server.
The information in this tip applies to any ThinkPad system running Microsoft Windows XP or Windows 2000 running System Information Center V1.1.
System Information Center is a ThinkVantage Technology Java server application designed to meet the asset inventory and management needs of small and medium-sized businesses. It is a small and flexible inventory management tool that gathers inventory information from a client system and sends this information to the System Information Center database, where it is stored. The information in the database can then be accessed with a Web browser. The process of collecting asset data can be automated and scheduled. A small client application, System Information Gatherer, is required to gather the information from the client. It is installed during the registration of each client to the System Information Center server.
For more information about System Information Center, see Using ThinkVantage Technologies: Volume 2 Maintaining and Recovering Client Systems, SG24-6060, and IBM System Information Center Administrator's Guide at http://www.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57526.
When installing the System Information Center program, the administrator can customize some of the options. One customization option is to schedule automatic scans and specify the frequency with which the System Information Gatherer program uploads new asset scan information from the client machine to the System Information Center server. In the following figure, the Automatically upload revised asset information box is checked, and the upload interval is set to 4 days.
However, when a System Information Center server is configured to automatically upload asset scans, and clients have installed the System Information Gatherer program, automatic scans fail to upload to the server at the appointed time.
System Information Center server uses a configuration file named isic.properties to store default and customized product configuration data. The configuration file does not properly set up the asset scan information during System Information Center product installation. As a result, client computers are unable to automatically upload scheduled asset scans using the System Information Gatherer agent.
To correct this problem, the isic.properties file must be modified as follows:
- Logon to the server where System Information Center is installed, select Start -> Run.
- Type notepad.exe and select OK.
- In the Notepad menu bar, select File -> Open.
- Use the browse function to navigate to this directory: C:\ISIC\web\WEB-INF\classes
- Select the isic.properties file.
- In the Notepad menu bar, select Edit -> Find. The Find dialog box opens.
- In the Find what field, type url=.
- Select Find Next.
- The line found will contain url=http://yourservername/isic (where yourservername is the computer name of the server with System Information Center installed). Delete the /isic portion of the line, making the line now read url=http://yourservername.
- In the Notepad menu bar, select File -> Save. Close Notepad.
- From the desktop, select Start -> Run.
- Type services.msc.
- The Services console opens, displaying a list of services. Find the ISICTomcat4 service. Right-click ISICTomcat4 and select Stop.
- When the service stops, right-click ISICTomcat4 and select Start. This starts the Tomcat service. The System Information Center Web site should be available after approximately 30 seconds.
Client computers running the System Information Gatherer program that are configured to automatically upload asset scans can now upload scans. The time it takes for scans to appear on the server running System Information Center depends on the schedule setting that was specified during the installation and the amount of information the program is currently processing.
This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.
Follow IBM Redbooks
Follow IBM Redbooks