Client Manager 6.3 release notes

This document contains a list of the known issues in this release of Intel® LANDesk® Client Manager. While these errors were not considered significant enough to delay this release, every effort will be made to address these issues in the next maintenance release of Client Manager 6.3.

Setup issues

Changing the installation path only changes the Client Manager path

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.

Setup allows installation to begin even when insufficient disk space is detected

Client Manager Setup's Select Components screen includes a field (in the bottom right corner) indicating how much hard drive space is required, and how much is available. Setup allows the installation to proceed even when the available space is substantially less than the space required (100 MB). If Setup continues, Client Manager begins copying files and eventually aborts due to lack of space.

Creative DVD decoder card causes Client Manager service provider to crash

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.

Error when uninstalling Client Manager: "Failed to create an instance of AOL 2 Agent object"

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.

Installing Japanese version when browser is set to English results in English interface

If you install the Japanese version of Client Manager on a computer whose browser has the default language set to English, Client Manager installs and displays the English interface.

Workaround—Set the browser's default language to Japanese before installing a Japanese version of Client Manager.

CIMOM not installed with Client Manager

If you want Client Manager to use the optional CIM hardware instrumentation to provide inventory information on Windows 98 Second Edition and Windows NT computers, you must download and install the WMI core download from Microsoft's Web site: http://download.microsoft.com/msdownload/wbem/2.0/x86core/en/wbemcore.exe. The CIM hardware instrumentation is not necessary in order to run Client Manager and view inventory information. If you use the CIM instrumentation, you must install it on the computer before installing Client Manager.

Uninstall leaves program folders under Program Files

When Client Manager uninstalls, some folders and files may remain under Program Files.

Client Manager fails when installed in the root directory

If you install Client Manager into the root directory, such as C: or D:, Client Manager doesn't run.

Workaround—Always install Client Manager into a subdirectory on a drive.

Administrator console is slow when loading a fully-qualified hostname

If you type a fully-qualified hostname in the browser's address field (such as http://computername.company.com:6787/index.tpc) instead of the abbreviated host name (such as http://computername:6787/index.tpc), the administrator console is slow in loading the page.

Workaround—Double-click Windows Control Panel's Network icon, click the Protocols tab, select TCP/IP Protocol, click Properties, click the DNS tab, and make sure all the information is filled out for your computer's DNS settings.

Different versions of Client Manager administrator should not be installed on the same computer

If you install Client Manager 6.3 administrator on a computer, you should not install an earlier version of Client Manager on the same computer—doing so causes some interface irregularities. Also, uninstalling an older version removes some files needed by the 6.3 version.

Updated network adapter required for Alert on LAN agent

If you plan to install the Alert on LAN agent on a computer using an Intel network adapter, the computer's network adapter driver must be dated March 5, 1999 or later. The latest drivers for Intel network adapters are available at the Intel Web site.

Don't install the Alert on LAN agent on a computer that doesn't support Alert on LAN

Installing the Alert on LAN agent on a computer that doesn't support Alert on LAN causes problems during install and uninstall. If you're not sure if the computer supports Alert on LAN, don't install the Alert on LAN agent.

Don't over-install the client version

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.

Client Manager not compatible with other DMI service providers

Client Manager should not be installed on computers running a DMI service provider from another vendor. DMI service providers from other vendors need to be removed from a computer before running Client Manager Setup.

Error message running Client Manager with HP OpenView, Tivoli, or CA

When Client Manager is installed on a Windows NT, 2000, or XP computer that is also running HP OpenView*, CA Unicenter*, or Tivoli TME* 10, the error message "Ordinal 383 could not be found in WDMIUTIL.DLL" may occur. Client Manager requires a newer version of the WDMIUTIL.DLL file and will not function when this error occurs.

Workaround:

  1. Install the Client Manager Application Integration Module (AIM), which will replace the DLL with the newer version Client Manager needs. The AIM is available on Intel's Web site.

  2. Rename the WDMIUTIL.DLL in the Windows\System32 directory.

  3. Copy the newer version of the WDMIUTIL.DLL file from the Program files\Intel\DMI\BIN directory to the Windows\System32 directory.

  4. Reboot the computer.

Uninstalling Client Manager with CIM on Japanese Windows 2000 displays errors in Event Viewer

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.

Uninstall stealth mode before installing non-stealth mode version

A "stealth mode" installation (no user interface on the client) should be uninstalled before installing the non-stealth mode version. If you install a non-stealth mode version over a stealth mode installation, several problems can occur, including:

Stealth mode admin install is possible

It is possible to do a "stealth mode" installation of the administrator console (choosing Admin or Full), which would result in the administrator console files being installed but not usable. The "stealth mode" installation option was intended for client installations only.

Removing network adapter causes shutdown problems

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.

Don't install administrator on laptop computer

The Client Manager administrator console should not be installed on a laptop computer (or any computer that goes into a suspended power mode). If a Client Manager administrator computer returns from suspend mode and then needs to be shut down, the computer may require an excessive amount of time (up to ten minutes) to power off. This is because the laptop must restore all of its connections with the Client Manager client computers it manages each time the computer returns from suspend mode and comes back online. This process can take several minutes.

Workaround—If you need administrative access to Client Manager computers from a laptop computer, use Internet Explorer on the laptop to browse to the Client Manager administrator on a non-mobile computer. For information on how to do this, see the topic "Connecting to a computer from any browser" in the online help.

Error: "The file 'SMBUS.VXD' or (Unknown) could not be found"

On Windows 98 Second Edition or Windows Me computers that support SMBUS, the error message "The file 'SMBUS.VXD' or (Unknown) could not be found" appears when reinstalling Client Manager.

Steps to reproduce:

  1. Install Client Manager on an SMBUS computer and reboot.
  2. Uninstall Client Manager and reboot.
  3. Install Client Manager again and reboot.
  4. During bootup, the SMBUS.VXD error appears.

Workaround—Specify the path to the SMBUS.VXD driver, such as \WINDOWS\SYSTEM (for Windows 98 Second Edition).

Intel® InBusiness™ Remote Services Center deletes crucial Client Manager DLLs when uninstalled

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.

Discovery and network issues

Japanese Windows 98 SE computers running Client Manager can't shut down if system resources are low

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.

Client Manager computer names can't contain spaces

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 (-).

Administrator can't connect to client temporarily if client's IP address changes

If a client computer on the network using one IP address later connects to the network using a different IP address (through a RAS connection, for example) the administrator can't connect to the client computer until the DNS server resolves the computer name with its new IP address.

Workaround—On the client computer, provide the IP address of the administrator computer you want to manage the client (from the Windows Start menu, click Programs | Intel LANDesk Management | Client Manager | Options | Remote Administrator tab). Or if you know the new IP address of the client, on the administrator computer's Select Computer page, delete the old reference to the client computer and add the new IP address using the Add Computer button on the toolbar.

Double-byte Japanese computer names not supported

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.

Microsoft TV Data Adapter prevents discovery of clients from administrator console

If the Microsoft TV Data Adapter is installed on a Windows 98 Second Edition computer, the Client Manager administrator console is unable to discover client computers. This is because the TV Data Adapter registers with the operating system as the first network adapter installed, and Client Manager attempts to use the first network adapter it finds when performing a discovery.

Workaround—Uninstall the TV Data Adapter. To do this, from the Windows Start menu, click Settings | Control Panel. Double-click the Network icon. On the Configuration tab, click TV Data Adapter and click Remove.

Administrators using a Japanese language computer only see English information from non-Japanese clients

Install the Japanese OS language pack on Windows NT 4.0 clients from the operating system CD. Once you do this, information from these clients will appear in Japanese on Japanese Client Manager administrator computers. Note—This only resolves the problem for Windows NT 4.0 clients, not for Windows 98 Second Edition clients.

Remote administrator doesn't completely power down some Windows 2000 computers

When a remote administrator sends a power-down instruction to computers, some computers running Windows 2000 may only shut down to the screen "It is now safe to turn off your computer" but not actually power off the computer.

Workaround— In the Windows registry, navigate to HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NT/Winlogon. Change the powerdownaftershutdown value to 1.

Managing clients over a router

If you need to manage Client Manager clients over a router, you must configure your router to forward broadcast (or Magic Packet) packets to the other networks where Client Manager clients are located.

Inventory issues

Exported CSV files and HTML files contain different information

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.

Adaptec PCI Ultra2 SCSI controller reports being connected to IRQ 52

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.

Partial video information on a multi-monitor Windows 98 SE or Windows 2000 system

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.

Network adapter not detected by instrumentation

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.

Refreshing the Asset Management inventory page displays confusing message

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.

Video doesn't show supported resolution with default vga.sys driver

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.

Computers with two mice (one PS/2, one USB) only report information for one mouse (USB)

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.

Operating System inventory page doesn't display information for device drivers

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.

Drives information reported for stripe sets and volume sets can be misleading

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.

Client Manager doesn't autodetect new processor core voltage if the processor is replaced

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.

Missing data in the I/O Ports page

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.

Discrepancies exist between Client Manager's System Resources and Windows utilities

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.

Operating System information doesn't appear unless logged in with administrator rights

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.

Mouse connector type incorrectly reported as "PS/2"

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.

Drives information different than that reported by Windows 98 SE

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.

System Resources information different than that reported by Windows

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.

BIOS information not displaying

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.

Health issues

Registry key needed for chassis detection and alerting to occur on Intel chipset-based motherboards

For all current and future Intel chipset-based motherboards, a missing registry key prevents chassis detection and alerting from working correctly.

Workaround—You need to add a key to the registry that enables chassis detection and alerting to work correctly with these motherboards.

1.   In the Registry Editor, navigate to:

HKLM\software\intel\cimgr\instrumentation\intel.iosmal.2.1\Chassis\Health Contributor|Intrusion Detection|001\state

2.   Add a new DWORD value, name it OKState, and set its value to 1.

3.   Reboot the computer.

S.M.A.R.T. drive errors not detected with CD-ROM as master and hard drive as slave

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)

S.M.A.R.T. drive errors not very descriptive

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

Alerting issues

Alert on LAN support

The Alert on LAN agent is not supported on Client Manager clients running Windows Me. The Alert on LAN proxy is not supported on Client Manager administrators running Windows 98 Second Edition or Windows Me.

Registry key needed for chassis detection and alerting to occur on Intel chipset-based motherboards

For all current and future Intel chipset-based motherboards, a missing registry key prevents chassis detection and alerting from working correctly.

Workaround—You need to add a key to the registry that enables chassis detection and alerting to work correctly with these motherboards.

1.   In the Registry Editor, navigate to:

HKLM\software\intel\cimgr\instrumentation\intel.iosmal.2.1\Chassis\Health Contributor|Intrusion Detection|001\state

2.   Add a new DWORD value, name it OKState, and set its value to 1.

3.   Reboot the computer.

A client computer's store and forward queue can't be turned off

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.

Deleting a client computer may not prevent it from forwarding alerts to the administrator

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.

Health icon on status bar may display incorrect health in rare conditions

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.

Clearing global log and refreshing deletes the log again

When the global log in the administrator console is cleared and then receives a new alert, if you right-click in the right pane and click Refresh, the log doesn't display the new alert(s). Instead, Client Manager deletes any new alerts that have been received by the global log.

Workaround—Instead of right-clicking in the right pane and clicking Refresh, click the Global Log link in the left pane again. (If you right-click in the right panel and click Refresh, clicking Global Log won't show the new event.)

POST errors aren't reported if date is set back

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.

JN440BX motherboards may generate a cover tamper alert when computer is powered down

Computers that use an Intel® JN440BX motherboard may send a cover tamper alert to the Alert on LAN proxy server when they are powered down, even when the computer's cover is not open.

Store-and-forward alerts from client aren't forwarded until administrator clicks Refresh on the Select Computer page

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.

Client Manager doesn't discover both networks on computers with two network adapters

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.

Alert on LAN proxy server can be changed but not removed

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.

Alert on LAN proxy server receives "presence heartbeat expired" alert when heartbeat is disabled 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.

Client Manager account issues

Changing username and password from a remote console transmits data as clear text

When you connect to a remote installation of Client Manager from a browser on the network, then make changes to Client Manager user accounts, the usernames and passwords you create or change are transmitted over the network using clear text. Although this information remains invisible to the average user, the clear text makes it possible to identify Client Manager account information using a packet sniffer on the network.

Workaround—If you're concerned about the security of your Client Manager accounts, only create and modify user accounts from the computer on which they reside.

Performing an action on a client computer from an administrator computer requires an account on the client computer

In order to perform most administrator console actions on a client computer (such as remotely powering on/off a computer, remotely flashing the BIOS, and so on), you must be logged into the administrator console using a username and password that is identical to a user account on the client computer.

User interface issues

Client Manager taskbar icon disappears when computer has critically low memory

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 F1 in Client Manager displays Internet Explorer Help

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 error text in a frame

Client Manager randomly displays the text INVALID CGI REQUEST in a frame.

Workaround—Refresh the browser or close and restart Client Manager.

Alert on LAN page accepts invalid character input

The Alert on LAN page accepts invalid characters (alpha characters where numbers are expected) without displaying an error message.

Selecting "Open in New Window" generates a script error

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.

Client Manager shouldn't run as an Active Desktop element

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.

Date format is inconsistent between administrator console and notification monitor

An administrator console displays its dates in the mm-dd-yyyy format. However, for notifications that display in the notification monitor, the date format used is according to the regional settings specified on the computer generating the alert, which may be a format of dd-mm-yyyy.

Clicking Refresh in log and global log pages can clear log

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.

BIOS date format doesn't reflect format in regional settings

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.

Conflict with OpenGL Screen Savers

If you attempt to access Client Manager while running an OpenGL* screen saver, your computer might crash.

Large fonts cause display problem in the Select Computer page

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.