This document contains a list of the known issues in this release of Intel
Changing the installation path during Setup only changes the location of the LDCM directory tree. Other files and directories Client Manager installs, such as Alert on LAN*, DMI, SMBus and Bootstrap agent, are still installed to the default directories on the C: drive.
When installing Client Manager on a Windows* 98 Second Edition computer with a Creative DVD decoder card, the Client Manager service provider Win32sl.exe crashes and displays the following message:
Win32sl.exe caused an invalid page fault at 0000:efefefef.
This is followed by two or three blue screens with the following message:
Fatal exception error 0E at 0028:C006F20B in VXD VNETBIOS(01) + 000005EB.
Uninstalling a full Client Manager installation (including the Alert on LAN agent) on a computer running Windows NT* 4.0 displays an error message with the title: "Failed to create an instance of AOL 2 Agent object." The dialog contains only a title and an OK button. This message box can be ignored as it is not reporting an actual problem.
When Client Manager uninstalls, some folders and files may remain under Program Files.
If you need to reinstall the client software, either on the client or as part of a full installation at the administrator computer, you must first uninstall the Client Manager software.
On a computer running the Japanese version of Windows 2000 professional, if you install the CIM instrumentation during Client Manager Setup and then uninstall Client Manager, errors are displayed in the Windows 2000 Event Viewer. These errors should not display in the Event Viewer.
If the network adapter is removed from the computer after Client Manager is installed, the operating system can't shut down. When you attempt to shut down the operating system, it displays the message "Please wait while your computer shuts down," and never completes the shutdown. A network adapter (or modem) and TCP/IP are required for Client Manager to run. Removing the network adapter after Client Manager is installed results in an invalid hardware configuration for Client Manager.
If you install Intel InBusiness Remote Services Center and then install Client Manager administrator on the same computer, they both run and co-exist quite well. But if you uninstall Remote Services Center and reboot, Client Manager doesn't start properly and displays error messages such as "Unable to locate DLL." It is looking for NTS.DLL. If you manually restore this file and launch Client Manager, it displays a message indicating that PDS.DLL is missing.
Japanese Windows 98 Second Edition computers with Client Manager installed sometimes can't shut down properly if system resources are at 20 percent or lower.
If the computer name contains a space, the browser can't connect to the HTTP server. Other operations, such as inventory export, remote reboot, and remote power off/on also do not work if the computer name contains a space.
Workaround: Instead of using a space in the computer name, use a hyphen character (-).
If double-byte Japanese characters are used to name a computer, the Computer field in the notification monitor displays dashes (-). Also, if you try to select a computer that uses a double-byte name in the Select Computer page, the hotlink to log on to that computer will not be available and you will not be able to access the computer. According to RFC-1034, DNS is limited to 7-bit ASCII characters for computer domain names. Double-byte characters are not supported.
To improve readability, Client Manager uses JavaScript* to modify some DMI data on its inventory pages and in the exported HTML file. Because no method exists to modify the same data when exported to a CSV file, the CSV data can be slightly different. For example:
Data |
CSV file |
Inventory page / HTML file |
Total physical memory |
Lists total physical memory in KB, as reported by DMI. |
Memory page and HTML file list total physical memory in MB. |
Virtual memory |
Lists total virtual memory and used virtual memory, as reported by DMI. |
Memory page and HTML file list total virtual memory and free virtual memory. |
Processor |
Lists "Installed?" as processor data, as well as voltage, stepping, s-spec/QDF number, and cartridge revision, even if no information is available (these categories are listed primarily for multi-processor configurations). |
Processor page and HTML file do not list this data if information is unavailable. |
System resources |
Doesn't list system resources data. |
System Resources page and HTML file list system resources data by correlating two data sources from DMI. |
Video / monitor |
Lists "Active" and "Identifying number" as monitor data, even if the information is "No" and "Not available" respectively. |
Video / Monitor page and HTML file do not list this data if a monitor isn't active or the identifying number is unavailable. |
The Adaptec PCI Ultra2 SCSI controller shows that it is connected to IRQ 52, but computers only have 16 IRQs, numbered 0-15. Windows NT also reports the IRQ as 52 in Control Panel. The instrumentation appears to be reporting the value from the controller's BIOS. This problem is being investigated with Adaptec.
Windows 98 Second Edition and Windows 2000 both support multiple monitors. On these computers, the information displayed in Client Manager's Video inventory page is not the information for the primary video card. Ideally, this page should display information for all installed video cards.
On some computers, the network adapter information is not detected by Client Manager instrumentation. The Network Adapter Name field in the Network inventory page is left blank.
When you change data on the Asset Management page and click Apply, then right-click in the right frame and click Refresh, a dialog appears asking if you want to "Repost form data?" This happens because the data you just changed was updated (posted) when you clicked Apply, and now you're asking to post the same data to the form again.
When Client Manager is running on Windows NT and using the default vga.sys video driver, the Video inventory page doesn't display the supported video resolutions. The driver supports at least two modes: 800x600 with 16 colors, and 640x480 with 16 colors.
On computers that have two mice connected (one PS/2, one USB), Client Manager only displays information on the Keyboard/Mouse inventory page for the USB mouse.
When Client Manager is running on a Windows 98 Second Edition computer, the Operating System inventory page doesn't display version or date information for Real Mode Device Drivers. On computers running Windows Me/NT/2000/XP, these fields display the version and date information for the device drivers.
If a computer has a stripe set or volume set configured across multiple hard disks, the Drives inventory page reports information that can be misleading. For example, if a D drive stripe set is created on physical disks 0, 1, and 2, Client Manager lists all of drive D as a partition on disk 0 because disk 0 is the first disk of the stripe set. Client Manager doesn't report that the D drive is striped, so it appears that disk 0 is much larger than it actually is.
The first time Client Manager runs, it autodetects the CPU core voltage (if it was set to autodetect). The Windows registry is then updated with the processor information, and the processor autodetection is turned off. After this happens, if you upgrade or replace the processor to a processor with a different core voltage, Client Manager generates voltage warnings for the CPU core voltage because it doesn't match the value in the Windows registry.
Workaround—From the Client Manager CD, navigate to the ASICCFG directory and double-click the .REG file. (The name of the .REG file will vary depending on the computer manufacturer.) This forces Client Manager to autodetect the new processor's core voltage.
If the computer's BIOS settings for the serial/parallel ports are set to AUTO, the I/O Ports inventory page doesn't display the port information on Windows NT computers. Windows NT doesn't load the drivers (or set the registry) if the port is set to AUTO.
Workaround—Configure the port to ENABLED in the BIOS and reboot.
Some Windows utilities (such as Device Manager and WINMSD.EXE) report IRQs, memory addresses, and I/O ports differently than what Client Manager reports on its System Resources inventory page. This is due to differences in the way these programs read the system resource information of a computer.
If you are not logged in to a Windows NT operating system with administrator rights, the Real Mode Tasks and System Variables inventory information will not appear on the Operating System page (or in the export files if you export the information). This has been modified to work with Windows 2000 and Windows XP.
On installations of Windows NT 4.0, the Client Manager inventory may incorrectly report the Mouse Connector Type as "PS/2" and the Keyboard Port Type as "Unknown" for Universal Serial Bus (USB) mice and keyboards. This is because Windows NT 4.0 does not support USB.
Computers running Windows NT 4.0 with USB keyboards and mice can do so only because of the ability of the BIOS to convert USB signals to PS/2 signals. PS/2 is supported by Windows NT 4.0.
Windows 98 Second Edition reports some Drives inventory values differently. The values reported for "Set Thresholds Disk Space" and "Total Capacity" may vary (about 1 percent) on Windows 98 Second Edition computers. Also, the "Total Capacity" reported by Client Manager may differ (about 1 percent) from the amount reported by the operating system, particularly on drives larger than 8.4 GB. This is because the method used to calculate drive capacity differs between Client Manager and the Windows operating system.
On the System Resources inventory page, the values reported for IRQ, I/O, Memory, and DMA may not be consistent with values reported by the operating system.
The BIOS information does not display on the BIOS inventory page if the BIOS event logs are stored in General Purpose Non-Volatile memory on Windows NT and Windows 2000/XP computers.
When a CD-ROM is configured as a master and a hard drive is configured as a slave, the Client Manager instrumentation does not pick up S.M.A.R.T. drive errors from the slave hard drive. The following configuration results in this problem:
Main HD on Primary IDE controller
CD-Rom on secondary IDE controller (Master)
Second HD (generating SMART errors) on secondary IDE controller (Slave)
When Client Manager reports a S.M.A.R.T. drive error, it reports the drive as "IDE 0," "IDE 1," and so forth. Descriptions for these physical drive names are provided below:
IDE 0—The master drive on primary controller
IDE 1—The slave drive on primary controller
IDE 2—The master drive on secondary controller
IDE 3—The slave drive on secondary controller
The Alert on LAN agent is not supported on Client Manager clients running Windows Me.
If a client computer is off the network for several days or weeks and generates dozens or hundreds of alerts during that time, when it finally reconnects to the network, it sends all of its alerts to the administrator computer(s) it previously registered with. This can generate significant network traffic and quickly fill the administrator computer's notification monitor. The store and forward queue can't be turned off to prevent these alerts from forwarding. It is very unlikely, however, that such a scenario would occur since administrator computers are removed from the client's list of administrator computers in approximately 60 days.
If a client computer is disconnected from the network, and the administrator then deletes that computer from its Selected Computers list, when the client computer is reconnected to the network (without rebooting) it continues to forward its alerts to the administrator.
Workaround—Ideally, you should delete the computer from the list before disconnecting it from the network. If the client computer has already been removed from the network and then deleted, reboot the client after it is reconnected to the network. You can also rediscover from the administrator and then delete the client computer again.
The health status icon that Client Manager displays on the status bar may be incorrect and inconsistent with the health status reported in other areas of Client Manager. This generally occurs when rare steps are taken to create and resolve a Client Manager health problem.
If you set the computer's system date back, after the BIOS scan has occurred, POST errors are no longer reported in Client Manager until after the scan date is reached, or the registry values are set to zero.
Workaround—In the Windows registry, navigate to HKEY_LOCAL_MACHINE\Software \Intel \cimgr \Instrumentation \Intel.IOSystem.2.1 \POSTError \Health Contributor. Reset the keys ScanTimeHiDWORD and ScanTimeLoDWORD to 0.
Computers that use an Intel
If a client computer generates an alert while it (or the administrator computer) is off the network, the client computer stores the alert, then forwards it to the administrator when both computers are back on the network. The administrator computer must display the Select Computer page to receive the stored alert.
When Client Manager is installed on a Windows 98 Second Edition or Windows Me computer with two network adapters, using a discovery broadcast address of 255.255.255.255 should discover Client Manager computers on both networks, but it doesn't. Only one network is discovered.
You can change the IP address for the Alert on LAN proxy server to another IP address, but you can't delete it.
Workaround—Disable Alert on LAN on the client.
When the Alert on LAN "presence heartbeat expired" alert is disabled on the client computer, the proxy server receives a notification stating the Alert on LAN client computer is no longer available. This is incorrect—the computer is still available.
No issues.
When a computer is critically low on memory, many of its 16-bit applications can begin crashing. In addition, the Client Manager taskbar icon (as well as other icons) are unloaded from the operating system's taskbar. When the memory problem is corrected, the Client Manager taskbar icon is not automatically reloaded. This is not a defect of Client Manager; Client Manager is simply responding as it should when the operating system begins shutting down applications as a result of insufficient memory.
Solution—Reboot the computer to restore the Client Manager taskbar icon.
Pressing the F1 key anywhere in the Client Manager program causes the Internet Explorer Help to appear instead of Client Manager Help. This is working as designed, but may cause some confusion if you press F1 expecting to see Client Manager Help.
Client Manager randomly displays the text INVALID CGI REQUEST in a frame.
Workaround—Refresh the browser or close and restart Client Manager.
The Alert on LAN page accepts invalid characters (alpha characters where numbers are expected) without displaying an error message.
When you right-click an option in the left pane of the client console and click Open in New Window, Client Manager displays an Internet Explorer Script Error: "Object doesn't support this property or method."
Workaround—Use the Open option instead of Open in New Window.
Don't run the Client Manager interface as a Windows Active Desktop element. If you do, clicking many of the inventory links generates a script error.
If the Client Manager log or global log has been cleared, right-clicking in the right pane and clicking Refresh deletes the log again. To refresh the right pane, click the Refresh button rather than clicking Refresh on the right-click menu.
On the BIOS inventory page, the BIOS date always displays in the MM/DD/YYYY format, even when a different date style is selected under Regional Settings for the operating system.
If you attempt to access Client Manager while running an OpenGL* screen saver, your computer might crash.
When you run Windows using the Large Fonts font size (Control Panel | Display | Settings tab | Font Size), the column headings in the Select Computer page don't display correctly and are unreadable.