Important Information about Intel(R) Server Control v3.1.1
March 6, 2001
Errata Items
A. Install
B. Silent Install
C. Uninstall
D. Documentation
E. Platform Instrumentation Control
F. Stand-alone Console
G. Platform Instrumentation
H. LANDesk(R) Server Manager
I. Independent Hardware Vendor (IHV) Instrumentation
Adaptec* SCSI Instrumentation
QLogic* SCSI Instrumentation
J. DPC Console Manager
K. Client System Setup Utility (CSSU)
L. EMC Integration (includes SNMP Support)
M. LAN Alert Viewer
**********************************************************************
Information in this document is provided in connection with Intel
products. No license, express or implied, by estoppel or otherwise,
to any intellectual property rights is granted by this document.
Except as provided in Intel's Terms and Conditions of Sale for such
products, Intel assumes no liability whatsoever, and Intel disclaims
any express or implied warranty, relating to sale and/or use of Intel
products including liability or warranties relating to fitness for a
particular purpose, merchantability, or infringement of any patent,
copyright or other intellectual property right. (Intel makes no
representations or warranties and specifically disclaims all liability
as to the sufficiency, reliability, accuracy, completeness or
usefulness of information in this file or in the ISC software).
Intel products are not intended for use in medical, life saving,
or life sustaining applications. Intel may make changes to
the information contained in this file and/or the ISC Software,
specifications, and product descriptions at any time, without
notice, (however, Intel has no obligation to provide modifications,
updates and/or support for same, nor shall Intel bear any liability
whatsoever for any such changes or modifications.)
This file identifies certain currently characterized errata, however,
Intel does not represent or warrant either that such list is all
inclusive or the absence of errata which do not appear on this
list.
Intel shall not be liable for any damages whatsoever (including
without limitation, lost profits, business interruption, computer
failure or malfunction, or lost information) arising out of the
use of or inability to use the ISC Software.
(Copyright c Intel Corporation 2000).
*Other product and corporate names may be trademarks or registered
trademarks of other companies, and are used only for explanation and
to the owners' benefit, without intent to infringe.
**********************************************************************
**********************************************************************
A. Install:
**********************************************************************
1. Use of the ISC setup and some of the components thereof require a
pointing device and will not be driven with keyboards alone.
2. If PI-only install is attempted on a system with a non-supported
platform, install will not clean up after itself after determining
it should not install PI on this particular system.
PI-only install on a supported platform will work properly.
3. On internationalized releases, some translations may be
inaccurate or inconsistent.
PROBLEM: Some text may not have been translated correctly,
consistently, or extraneous characters may be present, in both the
user interface and the documentation.
IMPLICATION: User may not have a clear understanding of the
information being communicated.
WORKAROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
4. On internationalized releases, some text may appear in English.
PROBLEM: At the time of release, some user interface and Help strings
may not have been translated, or may contain redundant English
text.
IMPLICATION: User may not have a clear understanding of the
information being communicated by the user interface.
WORKAROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
5. In Win98, using Netware Client Services for mapping drives to a Netware
system on the network, a default password or a previously used password
is used if no password is provided. Consequently, during ISC installation
when connecting to a netware system, a password is not required, if that
particular system was previously mapped and connected to the Win98 system
that we are running the ISC setup from.
**********************************************************************
B. Silent Install:
**********************************************************************
1. Silent install will work best if ISC is installed on one server
at a time.
**********************************************************************
C. Uninstall:
**********************************************************************
1. For customers using HP OpenView*, the files Ezrpcw32.dll,
Wcdmionc.dll, Wcrap.dll, Winrpc32.dll, and Wonctcp.dl are not
removed during uninstall when HP OpenView is running.
PROBLEM: Since the ISC Uninstall does not have information regarding
other applications running, ISC does not know how to shutdown HP
OpenView. Therefore, there are ISC files that are being used by HP
OpenView that can not be deleted.
IMPLICATION: Not all the files that are installed are removed from the
system during uninstall.
WORKAROUND: Stop HP OpenView prior to ISC Uninstall.
STATUS: Intel is investigating the possibility of fixing this erratum.
2. Intel Server Control objects are not being removed from the HP
OpenView database and map.
PROBLEM: After uninstalling the Intel Server Console, ISC symbols are
left on the HP OpenView map. If the user double clicks on a ISC
symbol, HP OpenView throws a Dr. Watson.
IMPLICATION: ISC symbols and objects created during ISC integration
are not removed from the system during uninstall.
WORKAROUND: Users have to copy manually
"c:\Program files\Intel\ServerControl\Bin\UninstIscOv.txt" file to
"c:\Openview\registration\C\UninstIscOv.txt".
STATUS: Intel is investigating the possibility of fixing this erratum.
3. On internationalized releases, some text may appear in English.
PROBLEM: At the time of release, some user interface and Help strings
may not have been translated, or may contain redundant English
text.
IMPLICATION: User may not have a clear understanding of the
information being communicated by the user interface.
WORKAROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
4. During UW uninstall the following message may show up on the server,
"S99ISC: Cannot open". This message does not bear any significance,
and the file s99isc will be removed once ISC uninstall is complete.
**********************************************************************
D. Documentation:
**********************************************************************
1. Background color of help does not always display correctly when
the help window is redrawn.
PROBLEM: After moving the help window off the screen and SLOWLY
dragging it back onto the screen the background color is redrawn
with too many white pixels.
IMPLICATION: Background color change.
WORK-AROUND: None
STATUS: Intel is investigating the possibility of fixing this erratum.
**********************************************************************
E. Platform Instrumentation Control:
**********************************************************************
1. Keyboard shortcuts do not always work.
PROBLEM: The ISC GUI is split into two windows or panes. The left
pane is used for navigation, the right pane is used for
presentation of information. If the current window focus is in the
right pane, then keyboard shortcuts will not work. For example,
the F5 key will not refresh the screen, the tab key will not
navigate, and the Alt-A shortcut will not Apply. If the current
window focus is in the left pane, then the F5 key will refresh
the data displayed including the right pane.
IMPLICATION: The mouse and menu must be used instead of the
keyboard.
WORK-AROUND: Use the mouse to click in the left pane to apply the
window focus. This will allow use of the F5 key for refresh. The tab
key and Alt-A key do not work.
STATUS: Intel is investigating the possibility of fixing this erratum.
2. The win32rap service reports several error messages if NetWare*
services are not installed.
PROBLEM: If ISC is installed on a console or server without installing
the NetWare services, then win32rap may report the following error
messages in the application event log:
"failed to initialize transport 'ddetrdll'"
"failed to initialize transport 'ipx'
"initializing winsock for ipx failed (winsock error 0x0000273f)"
IMPLICATION: These messages simply indicate that win32rap
attempted to start the NetWare services. If you are using tcp/ip
for server communication then they are not a concern.
WORK-AROUND: You can ignore the error if your network only supports tcp/ip.
STATUS: Intel is not investigating this erratum.
3. Shutting down the Windows NT* OS may fail to complete on a busy
system.
PROBLEM: If the server performs a "Shutdown the OS", "Shutdown the OS
and Power Off", or "Shutdown the OS and Hardware Reset" event
action on a Windows NT server, while the server is very busy, the
OS shutdown may fail to complete. If the OS shutdown fails to
complete, the power off or hardware reset will not occur.
IMPLICATION: A very busy server may fail to shutdown completely, and
will remain in that state until a user intervenes.
WORK-AROUND: Use other event actions.
STATUS: Intel is investigating the possibility of fixing this erratum.
4. ISC shutdown and power control actions may not work on NT 4.0 SP3
or Enterprise Edition if IRMC driver is loaded.
PROBLEM: If NT 4.0 Service Pack 3 is loaded on a system with a
Intel remote management card (IRMC) installed and a ISC
"Shutdown the OS and Power Off" or "Shutdown the OS and
Hardware Reset" event action is attempted, the system will
shutdown, but the power off or hardware reset may not occur.
IMPLICATION: The system will not perform the requested power off or
hardware reset.
WORK-AROUND: Use IRMC functions to power off or reset the
system.
STATUS: Intel is investigating the possibility of fixing this erratum.
5. The "Immediate Hardware Reset" and "Immediate Power Off"
features may not work properly during initialization.
PROBLEM: During the ISC GUI initialization, if the user selects
the power control actions "Immediate Hardware Reset" or
"Immediate Power Off", the actions may not work as
documented.
IMPLICATION: The power control actions "Immediate Hardware
Reset" and "Immediate Power Off" may not work properly and
the server may continue to run without the desired action.
WORK-AROUND: Users should wait until the ISC GUI has
completed initialization (READY state in status bar) before
attempting these actions.
STATUS: Intel is investigating the possibility of fixing this erratum.
6. Paging alert actions may continue to happen after it has been
removed as an alert action.
PROBLEM: If paging is configured as an alert action for a threshold
and that threshold is crossed, a page will happen as desired.
If paging is then removed as an alert action from the threshold,
it may still occur.
IMPLICATION: A page may be issued when undesired.
WORK-AROUND: No work-around has been identified.
STATUS: Intel is investigating the possibility of fixing this erratum.
7. If both a shutdown action and a page are selected, the page may
not be sent.
PROBLEM: If both a shutdown action and a page are selected, the page
may not be sent.
IMPLICATION: A page may not be issued.
WORK-AROUND: Do not configure both a page and a shutdown action on
the same event.
STATUS: Intel is investigating the possibility of fixing this erratum.
8. Under Netscape* 4.x w/ ScriptActiveX installed, user may see the
following error message when loading the ISC console: "This page
attempted to load an ActiveX control not registered as safe for
loading (209)"
PROBLEM: Additional registry updates are required to run the ISC
Console under Netscape 4.x when ScriptActiveX is installed.
IMPLICATION: User will see the error message listed above and the
ISC console will not load.
WORK-AROUND: See support.intel.com
STATUS: Intel is investigating the possibility of fixing this erratum.
9. Some processor temperature sensors may first show a current status of
'unknown' with a current reading of 'unsupported'.
PROBLEM: The processor temperature sensors may initially show a current value
of 'unknown' and a current reading of 'unsupported'. These values will
be replaced by the correct data as soon as the sensor becomes active,
this may take up to two minutes. It may be necessary to manually refresh
the console application before the health indicators correctly reflect
the new status values.
IMPLICATION: The processor temperature sensor status information may not be
available for approximately two minutes after the server boots. A
manual refresh of the console application may be needed to correct the
health indicators of a console that started before the status information
was available.
WORK-AROUND: If a processor temperature sensor has a status of 'unknown'.
Wait two minutes and refresh the console display.
STATUS: Intel is investigating the possibility of fixing this erratum.
10. Due to the rounding of floating point values, the user can set
different threshold values without variance in ISC PIC.
PROBLEM: Due to the rounding of floating point values, the user can set
different threshold values without variance. This is possible only if
the user tries to set different threshold values so close to each other
that the hardware characteristics of the sensors are bypassed.
IMPLICATION: The user may be able to set the same value for different
sensor thresholds.
WORK-AROUND: Do not set different threshold values very close.
STATUS: Intel is investigating the possibility of fixing this erratum.
11. Server will not shutdown gracefully and will hang if not logged into
PROBLEM: Under Microsoft Windows NT4, if an event shuts down
the server and the server has not been logged into, the system
will be halted and the shutdown will not occur. If the server
has been logged into, the shutdown will happen as desired.
But, after the server comes back up, if another event
attempts to shut down the server before it has been logged into,
the system will be halted and the shutdown will not occur.
IMPLICATION: Server may not shutdown when needed.
WORK-AROUND: Logging into server when it first starts up and again
after any subsequent reboots will allow graceful shutdown actions.
STATUS: Intel is investigating the possibility of fixing this erratum.
12. Broadcast messages sent from NetWare to a Windows 9x/NT console may
not be displayed.
PROBLEM: When an alert action "Send Broadcast Message" is selected as one
of the LRA actions for a sensor whenever it crosses a threshold, the
broadcast message may not get displayed at the console if the console
is running Windows 9x/NT/2000. This is the case when Microsoft Client
for NetWare is being used at the console to access NetWare resources.
IMPLICATION: It gives the impression that NetWare broadcast messages are
not sent to the console at all.
WORK-AROUND: If the Novell client for Windows 9x/NT is used instead of the
Microsoft client, then this problem does not happen.
STATUS: Intel is investigating the possibility of fixing this erratum.
13. ISC PIC may not show all servers manageable via ICMB.
PROBLEM: After the user selects the "Enable as Management Point" checkbox in
the "Local ICMB Server Configuration" group box in the "ICMB Configuration"
tabbed page which is accessed using the ICMB folder in the left pane sensor
tree view, PIC may not discover all of the servers that support
management via ICMB.
IMPLICATION: User will not be able to manage all servers on the network that are
manageable via ICMB.
WORK-AROUND: Relaunch PIC after selecting the "Enable as Management Point"
checkbox.
STATUS: Intel is investigating the possibility of fixing this erratum.
14. Server health update is slow on Windows 98 console when connecting to a
NetWare 5 server.
PROBLEM: When PIC is running on a Windows 98 machine to connect to a
NetWare 5 server, the server health update might be very slow.
The server health status is usually updated more quickly on a
Windows NT or Windows 2000* console.
IMPLICATION: User will observe slow health update of ISC NetWare 5 server
on Windows 98 console.
WORK-AROUND: User might hit the F5 key to get the server health
updated correctly.
STATUS: Intel is investigating the possibility of fixing this erratum.
15. Server health update is slow or missing on Windows 98 console
when connecting to a UnixWare 7.1.1 server.
PROBLEM: When PIC is running on a Windows 98 machine to connect to
a UnixWare 7.1.1 server, the server health update might be very slow
or completely missing. PIC updates server health in a more timely
reliable fashion when running on a Windows NT or Windows 2000 console.
IMPLICATION: User may not observe health update of ISC UnixWare 7.1.1 server
on Windows 98 console. Even if PIC does update the server health, it
will be slow.
WORK-AROUND: User might hit the F5 key to get the server health
updated correctly.
STATUS: Intel is investigating the possibility of fixing this erratum.
16. On internationalized releases, some translations may be
inaccurate or inconsistent.
PROBLEM: Some text may not have been translated correctly, consistently,
or extraneous characters may be present, in both the user interface
and the documentation.
IMPLICATION: User may not have a clear understanding of the information
being communicated.
WORKAROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
17. On internationalized releases, some text may appear in English.
PROBLEM: At the time of release, some user interface strings may not
have been translated.
IMPLICATION: User may not have a clear understanding of the information
being communicated by the user interface.
WORKAROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
18. On non-English operating systems, the font display may be unclear
in some portions of the user interface.
PROBLEM: The display may be unclear or difficult to read on the main
user interface.
IMPLICATION: User may have difficulty reading output.
WORK-AROUND: None.
STATUS: Intel is currently investigating a fix for this erratum.
19. All Intel(R) Pentium(R) III Xeon(TM) Processor factory thresholds
are read-only and cannot be changed through ISC.
PROBLEM: All thresholds related to Pentium(R) III Xeon(TM) Processor are
set during manufacturing and cannot be changed. The ISC application
allows users to modify these values but the changes are not written to
the system.
IMPLICATION: Thresholds appear editable even though they cannot be changed.
WORK-AROUND: None.
STATUS: Intel is currently investigating a fix for this erratum.
**********************************************************************
F. Stand-alone Console:
**********************************************************************
1. A new item titled 'Stop Discovery" was added to the "Server" pull-down
menu to allow the user to stop the ISC discovery process whenever there is
at least one server being discovered. This should work fine in general. However,
the user might encounter some error condition (like application error) when
terminating the application. This could be caused by some possible resource
leaking when a discovery thread is forced to terminate. The symptoms varies on
different Windows platforms (Win98, NT Workstation/Server, Win2000) depending on
system resources available. This should not have any impact on launching all
of the ISC applications.
IMPLICATION: The system might be in a unstable state when some discovery threads are
forced to terminate.
WORK-AROUND: Stop the ConsoleToolsMgr.exe process (if running) and restart the ISC console.
STATUS: Intel is currently investigating a fix for this erratum.
2. ISC Console reports one server when there are none.
PROBLEM: When all servers have been deleted, one at a time, the status
box reports that there is still one server.
IMPLICATION: User may may be confused by the information conveyed by
the user interface.
WORKAROUND: If the servers are deleted with the Delete All button,
the status is correct.
STATUS: Intel is investigating the possibility of fixing this erratum.
**********************************************************************
G. Platform Instrumentation:
**********************************************************************
1. Unloading SENSOR.NLM may show a small number of short term memory
allocations that were not free.
PROBLEM: SENSOR.NLM may not free all memory associated with some
function. This will cause NetWare to display a message when
it frees the memory after unloading the NLM.
IMPLICATION: A small amount of memory will be used and will not
be made available again until the NLM is unloaded. This should
not be a significant number of bytes and should not impact server
performance.
WORK-AROUND: No work-around has been identified.
STATUS: Intel is investigating the possibility of fixing this erratum.
2. ISC may cause a floppy error message being generated on a Linux
server
PROBLEM: While starting ISC on a RedHat Linux server, the user may see
the message "end_request: I\O error, dev 02:00 (floppy), sector 0"
on the system console. It is because ISC tries to mount the
floppy drive to check for some configuration files. The mount
command results in the above message being generated if there is
no floppy in the drive. This message comes from the floppy driver
in the kernel and can't be suppressed.
IMPLICATION: User may think that some errors have occurred when in fact
this is the expected behavior if there is no floppy in the drive.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
3. The Power Unit Global Table on Intel Server Control Platform
Instrumentation Control (User Interface) for SBT2 & STL2 servers will
not provide indication for "Power Unit Redundancy Lost".
PROBLEM: The ISC PIC on SBT2 & STL2 servers does not produce
indications for "Power Unit Redundancy Lost". Actions configured for
a "Power Unit Redundancy Lost" alert will not occur. However, there
is a SEL entry for the "Power Unit Redundancy Lost".
IMPLICATION: Actions configured for the "Power Unit Redundancy Lost' alert
will not occur.
WORK-AROUND: The "Power Unit Redundancy Lost' event will always be
accompanied by a power supply failure alert for the power supply that failed.
Configure any desired actions to occur when any of the the individual power
supplies fail and not on the Power Unit Global Table.
STATUS: Intel is currently investigating a fix for this erratum.
4. The SNMP "read only" access option for Intel Server Control Platform
Instrumentation (ISC PI) does not function as desired.
PROBLEM: The Intel Server Control (ISC) version 3.x feature of providing
support to disabling SNMP Set Commands to the sets on a server with Intel
Server Control Platform Instrumentation is currently not functioning as
expected. During installation of Intel Server Control (ISC)
there is an option under "Platform Instrumentation"
called "SNMP Read Only access". Selecting this option will not actually
disable Set commands. By default SNMP Set & Get commands are permitted
and work correctly. There is no impact to generation of SNMP traps
which functions normally. Traps are processed and received by the SNMP
consoles, as desired.
WORK-AROUND: The security feature in the Operating System for
SNMP Service, allows a user to configure "Community Rights"
to "READ ONLY". This is essentially the same as disabling SNMP
Sets for all extension agents including Intel Server Control
Platform Instrumentation.
STATUS: Intel is currently investigating a fix for this erratum.
******************************************************************
H. LANDesk(R) Server Manager:
******************************************************************
1. Repair AMS2 database message is displayed after abnormal server
shutdown.
PROBLEM: Repair AMS2 database message is displayed after abnormal
server shutdown.
IMPLICATION: The LDSM application may fail to start or function
correctly as a result of a corrupted AMS2 database. A corrupted
AMS2 database may result from an immediate server shutdown,
immediate hardware reset or immediate power-off action.
WORK-AROUND: The AMS2 database may be repaired as follows:
1. Control panel
2. ODBC icon
3. System DSN tabbed page
4. Configure button
5. Select AMS
6. Repair button
If the above steps do not fix AMS2 database corruption,
replace the AMS2 database with the one on the LDSM CD.
STATUS: Intel is investigating the possibility of fixing this erratum.
2. An error message appears on the LDSM console when attempting to
start ISC.
PROBLEM: If the ISC server software is installed on a remote server,
but the console software is not installed on the machine that has
LDSM installed, then an error message will appear that reads:
"Error : Token not defined on the server Result = 80004005.
Return Server manager setup and use the Have disk option to
install the application. The application should be included
on disk supplied by the original equipment manufacturer "
The LDSM software is told, by the server, that ISC is installed and
so should appear in the Tools menu. However, if the ISC console
software is not installed on the LDSM client, then LDSM can not
run the ISC application.
IMPLICATION: ISC will not start on the console.
WORKAROUND: The user must install the ISC console software on the
same client computer that has LDSM installed.
STATUS: Intel is not investigating this erratum.
3. ISC may not appear in the Tools menu on the LDSM console.
PROBLEM: The DMI Service Provider maintains a backup copy of the
DMI database for recovery purposes. If after installing ISC, the DMI
database gets corrupted prior to a normal server shutdown, then the
next time the server boots the DMI database will be restored from a
version which does not contain ISC installed components. If the
LDSM console is run on this version of the DMI database, then ISC
would not appear under the Tools menu even though ISC had been
installed.
IMPLICATION: ISC will not appear in the LDSM Tools menu even though
it has been installed.
WORKAROUND: There are several workarounds that will solve this
problem.
1- Reinstalling ISC.
2- Manually copying the DMI database file sldb.dmi to the
MIFS\backup directory after installing ISC.
STATUS: Intel is investigating the possibility of fixing this erratum.
4. SNMP traps are not appearing in the LDSM Trap Receiver
PROBLEM: The LDSM SNMP trap receiver log does not appear to be
receiving the events that are generated by ISC. ISC is correctly
generating the AMS event, because an AMS message box will appear.
However, LDSM is not creating an SNMP trap and logging it into the
trap receiver log.
IMPLICATION: Not all ISC events appear as SNMP traps.
WORKAROUND: None known at this time.
STATUS: Intel is investigating the possibility of fixing this erratum.
5. LDSM SNMP Event Viewer cannot run on the same machine as
HP OpenView*.
PROBLEM: Conflict between LDSM and HP OpenView.
IMPLICATION: Only one of these applications can receive TRAPs, if
running on the same Windows NT system.
WORK-AROUND: Run one viewer at a time.
STATUS: Intel is investigating the possibility of fixing this erratum.
6. ISC alerts are not appearing in the LDSM Alertlog.
PROBLEM: The LDSM alertlog does not appear to be receiving the
events that are generated by ISC. ISC is correctly generating the
AMS event, because an AMS message box will appear. However,
LDSM is not logging it into the LDSM alertlog.
IMPLICATION: Not all ISC events appear in the LDSM Alertlog.
WORKAROUND: None known at this time.
STATUS: Intel is investigating the possibility of fixing this erratum.
7. DPC icon may not appear or be launchable.
PROBLEM: Under some server configurations, the DPC icon may not appear
within LDSM or it may appear but not be launchable.
IMPLICATION: DPC cannot be launched from within LDSM.
WORKAROUND: Start Standalone Console and launch DPC from within it.
STATUS: Intel is investigating the possibility of fixing this erratum.
8. ISC SNMP traps fail to show up on Enterprise Management Consoles (EMCs)
if LANDesk(R) Server Manager (LDSM) agents are running on same server.
PROBLEM: ISC traps fail to show up on EMCs if LDSM agents are
running on the server before ISC is installed on that server.
IMPLICATION: If LDSM is installed on a server prior to ISC installation
on that server, no ISC traps will be received by any SNMP trap
consoles that are configured to receive these traps from this server.
WORK-AROUND: Installing ISC before LDSM install
on that server will allow proper ISC SNMP trap reception on SNMP
trap consoles. An alternate workaround if LDSM is already installed
before ISC on that server is to change the LDSM services - Alert
Originator (AOS) and the Server Monitor (NTSM) to manual start at
boot time. Then during boot sequences, start these same two LDSM
services after all ISC services have initialized first on the
server (approx 2-3 minutes).
STATUS: Intel is investigating the possibility of fixing this erratum.
9. Intel Server Control cannot launch from the LANDesk(R) Server
Manager Snap-in folder.
PROBLEM: Intel Server Control should display an icon within
LANDesk Server Manager and allow the user to launch Intel Server
Control from that location. In some cases the user may not see an
Intel Server Control icon or they may receive a Windows error
message when trying to launch.
IMPLICATION: If Intel Server Control is installed on a console system
first, and them LANDesk Server Manager is subsequently installed,
an incorrect Windows Registry Key entry is made which prevents
ISC from being able to correctly launch from within LANDesk Server
Manager. ISC will correctly launch and run normally if selected
from the Windows "Start/Programs" menu.
WORK-AROUND: Two possible work-arounds exist. The user may
reinstall ISC for a second time after the LANDesk Server Manager
installation.
The second workaround involves the user modifying the Window
registry. This modification should only be attempted by
experienced users. Complete the following steps. These changes
would be appropriate for a console system running Windows NT 4.0,
Windows 2000 or Windows 98.
- Confirm that neither LANDesk Server Manager or ISC are running
- Registry path is HKEY_Local machine on local machine, go to
SOFTWARE\INTEL\LANDesk\Management Console\Launch Guids\
* Find the token for {5cde3320-8928-11d1-86ce-00a91abc89}
There may be several similar tokens present
* Find the token that contains: CommandLine & Launch App
* Edit CommandLine to show:
REG_SZ: MachineName CurrentConnection
* Edit Launch App to show:
REG_SZ: C:\Program Files\intel\servercontrol\bin\iscpic.exe
* Close registry and launch the LANDesk Server Manager console
Any server that has Intel Server Control software installed will
now be manageable from the LANDesk Server Manager Snap-in folder
on the console system
STATUS: Intel is investigating the possibility of fixing this erratum.
******************************************************************
I. Independent Hardware Vendor (IHV)
******************************************************************
Adaptec* SCSI Instrumentation:
1. The Adaptec SCSI component reports the wrong information about
Logical Unit Drives on Mylex* Host Adapters.
PROBLEM: On NetWare Servers, a known incompatibility between the
Adaptec and the Mylex ASPI drivers can cause the Adaptec SCSI
component to report the wrong information about Logical Unit Drives
on Mylex Host Adapters.
IMPLICATION: The wrong information may display.
WORK-AROUND: The SCSI DMI instrumentation requires Adaptec ASPI
drivers (ASPI32.SYS and WNASPI32.DLL). The user must load these
drivers on the server. The Mylex DMI instrumentation does not
require Mylex ASPI drivers. Unless some other application requires
the Mylex ASPI drivers, do not load the Mylex ASPI drivers.
STATUS: Intel is currently not investigating a fix for this erratum.
2. During Wired for Management (WfM) testing, the DMTF CompChk
tool reports errors in the Adaptec MIF.
PROBLEM: The recent discovery of MIF syntax violations in Adaptec
instrumentation does not compromise the Intel(R) AD450NX MP
systems standing as "WfM upgradable" system. The SCSI
instrumentation supplied by Adaptec is not required on WfM 1.1a
servers.
IMPLICATION: As a side effect of WfM testing, we have found cases
where the Adaptec MIF does not comply with the syntax of DMTF
standard groups. The WfM test suite uses the DMTF CompChk
tool to scan the entire system MIF. It reports WfM pass/fail on the
specific groups required by WfM, and also notifies the user about
any problems it detects with respect to general DMI compliance
for all other groups it finds registered with the service provider. The
Adaptec problems fall into this second category.
WORK-AROUND: None required. The (slightly) non-compliant MIFs
can be successfully browsed by LDSM and the DMI Explorer browser
bundled with ISC. We currently believe there should be no effect on
the user's ability to access and use this data.
STATUS: Intel is investigating the possibility of fixing this erratum.
3. On server systems with onboard Adaptec SCSI controllers, users will
see CIO events messages as the operating system loads.
PROBLEM: These messages are not reporting a problem with the
system. The messages are normal indications from Self Monitoring
and Reporting Technology (SMART) that the SCSI controller
and hard drives are communicating normally.
IMPLICATION: Some users may find these messages annoying as
the operating system is loading.
WORKAROUND: In Microsoft* Windows* operating systems the
user may turn off SMART polling to eliminate these messages. This will
however also prevent any other SMART messages being generated, including
those predicting drive failure. To turn off SMART polling the user can
modify the file IOMGR.INI in the following file folder,
Program Files\Adaptec\CIO400.
Any text editor may be used to open this file. Near the end of this file
is a line which reads by default...
"SmartPolling = Yes". The user may modify this line to read
"SmartPolling = No".
STATUS: CIO messages are normal indications.
QLogic* SCSI Instrumentation:
******************************************************************
J. DPC Console Manager:
******************************************************************
1. Redirect doesn't support green (teal) color.
PROBLEM: Console redirect does not display green shades. Currently,
teal is displayed as cyan (or aqua).
IMPLICATION: The Adaptec* Option ROM BIOS displays white text on teal
background. DPC Console Manager is displaying this as white text
on cyan, which is extremely hard to read.
WORK-AROUND: None identified.
STATUS: Intel is investigating the possibility of fixing this erratum.
2. Press F1 for help may not work.
PROBLEM: On non-English operating systems, pressing F1 may not cause
the help to show up. The user receives a message that help does
not exist.
IMPLICATION: User may not have F1 access to needed help topics.
WORKAROUND: Access the help topic through the menu selection.
STATUS: Intel is investigating the possibility of fixing this erratum.
3. On internationalized releases, some text may appear in English.
PROBLEM: At the time of release, some user interface strings may not
have been translated.
IMPLICATION: User may not have a clear understanding of the information
being communicated by the user interface.
WORKAROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
4. On internationalized releases, some translations may be
inaccurate or inconsistent.
PROBLEM: Some text may not have been translated correctly, consistently,
or extraneous characters may be present, in both the user interface
and the documentation.
IMPLICATION: User may not have a clear understanding of the information
being communicated.
WORKAROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
5. On non-English operating systems, the text may be cut off in the
status box.
PROBLEM: The translations of the status may not fit within the
space provided.
IMPLICATION: User may be unable to read the output.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
6. Dial-up connection dialog appears when performing Service Partition operations
PROBLEM: On Win2000, when connected via DPC to the Service Partition, sometimes when
performing Service Partition actions, the dial-up connection dialog appears. Also
under this circumstance, any other application, such as a web-browser, that attempts
to access the internet, if run, could cause this dialog to appear. If the user
presses 'cancel' the correct dialog box appears.
IMPLICATION: Unexpected interface behavior.
WORK-AROUND: Cancel the extraneous box and continue normal use. Another option is to select
the settings option in the dial-up connection dialog. If you see that the option is
set to "Always dial my default connection" you can fix the problem by changing that
to "Dial whenever a network connection is not present".
This problem can also occur in instances where there is no dial-up connection listed,
you can create a 'dummy' entry and set it to be the default, with a setting of "Dial
whenever a network connection is not present".
STATUS: Intel is currently investigating a fix for this erratum.
7. "Graceful Shutdown has failed." or "Graceful reset has failed" dialog
appears when you know the OS is up and Platform Instrumention is running.
PROBLEM: On rare occasions (less than 2%) of the time, when you attempt to do a reset,
shutdown or boot to Service Partition. The Platform Instrumentation service may
begin performing this operation, howver DPC may not receive notification of
this action. Under this circumstance, DPC will present a dialog indicating that
this 'graceful' action failed, would you like to 'force' it.
IMPLICATION: Unexpected behavior, user thinks the reset,power-down or reboot to Service
Partition action failed, when in fact it is successfully being carried out.
WORK-AROUND: If you see in the status of DPC that the OS is detected, or if you are certain
this OS is running and the Platform Instrumentation service is active, and this dialog
appears, press 'Cancel' when prompted for a 'Force' operation. Wait 5 minutest and
try again.
STATUS: Intel is currently investigating a fix for this erratum.
8. FRU loaded twice.
PROBLEM: If after downloading FRU, the user attempts to download SDR,
the FRU gets downloaded again, and when finished, the SDR information
is downloaded.
IMPLICATION: Poor performance.
WORK-AROUND: None.
STATUS: Intel is currently investigating a fix for this erratum.
9. DPC will crash if the system tray connection icon is used to
disconnect.
PROBLEM: If the system tray connection icon is used to disconnect the
modem DPC will crash. This is only reproducable under Windows 98.
IMPLICATION: DPC crashes and the server and console system must be
rebooted to continue.
WORK-AROUND: Do not use the system tray icon to disconnect the
connection.
STATUS: Intel is investigating the possibility of fixing this erratum.
******************************************************************
K. Client System Setup Utility:
******************************************************************
1. In the Resource Configuration Manager, if the Resources dialog is
displayed, clicking on a device in the resource list does not open the
corresponding device window dialog.
PROBLEM: Users cannot get to device window dialogs from the System
Resource dialog.
IMPLICATION: Users must get to the device window dialogs using another
method.
WORK-AROUND: Users can get to device window dialogs from the Device
dialog (first dialog that appears when the Resource Configuration Manager
comes up.
STATUS: Intel is investigating the possibility of fixing this erratum.
2. Pointing device needed to run CSSU.
PROBLEM: Most managers do not have keyboard support for dialogs; for example,
pressing the Enter key does not cause any action to occur dialogs for most
managers.
IMPLICATION: A pointing device, such as a mouse, is needed when running CSSU.
WORK-AROUND: Use a pointing device to access CSSU functions. Accelerator keys
can also be used.
STATUS: Intel is investigating the possibility of fixing this erratum.
3. SDR Manager may not be able to read all .sdr files.
PROBLEM: SDR Manager has problems reading .sdr files produced outside
of the Client SSU.
IMPLICATION: Some records may appear corrupted in the SDR Manager
display when such a file is opened using the CSSU SDR Manager.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
4. SDR Manager displays some values incorrectly.
PROBLEM: In Full Sensor Records and Compact Sensor Records, the SDR Manager
displays the Sensor Owner ID bits in the reverse order. In Generic Device
Locator Records, the Device Type Modifier is translated incorrectly.
IMPLICATION: Users will see some values displayed incorrectly.
WORK-AROUND: None
STATUS: Intel is investigating the possibility of fixing this erratum.
5. FRU files will not load after loading of an invalid FRU file is attempted.
PROBLEM: If an attempt is made to load an invalid FRU file with the FRU Manager,
then if an attempt is made to load a valid file, an error message will
be displayed.
IMPLICATION: User cannot load a valid FRU file after trying to load an invalid file.
WORK-AROUND: Close the FRU Manager and reopen. The valid FRU file should load.
STATUS: Intel is investigating the possibility of fixing this erratum.
6. Unable to change BIOS passwords from a Chinese Windows 98 client.
PROBLEM: If the client system is running the Simplified Chinese version
of Windows 98, users will be unable to change BIOS passwords from
within the Password Manager of Client SSU. Instead, all attempts
will result in message indicating that invalid characters have
been entered.
IMPLICATION: From a Chinese Windows 98 client, users will not be able to
change BIOS administrator or user passwords.
WORK-AROUND: Use a Chinese Windows NT client or set the BIOS passwords
locally. Note that BIOS passwords do not affect the ability of
the Client SSU to establish a connection to a remote server from
a Chinese Windows 98 client since only the EMP password is required.
STATUS: Intel is investigating the possibility of fixing this erratum.
7. Untranslated or missing help topics.
PROBLEM: On internationalized releases, the CSR help topic may appear in
English and the SUM help topic may be absent..
IMPLICATION: User may not have access to necessary help files.
WORKAROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
8. On internationalized releases, some text may appear in English.
PROBLEM: At the time of release, some user interface strings may not
have been translated.
IMPLICATION: User may not have a clear understanding of the information
being communicated by the user interface.
WORKAROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
9. In FRU Manager the Mode text may be truncated.
PROBLEM: On any Chinese OS, while viewing the FRU Manger the information
in the status bar indicating that the mode is modem may be truncated.
IMPLICATION: Mode may not be clearly communicated to the user.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
10. Hotkeys may not work.
PROBLEM: Some dialogs may have hotkeys which do not work. When
user attempts to use some hotkeys, nothing happens.
IMPLICATION: User cannot control the dialog without a mouse.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
11. Pressing F1 for help may not work.
PROBLEM: On non-English operating systems, pressing F1 may not cause
any help to appear. Instead, the user may receive a message that
help does not exist.
IMPLICATION: User may not have F1 access to needed help topics.
WORKAROUND: Access the help topic through the menu selection.
STATUS: Intel is investigating the possibility of fixing this erratum.
12. Garbage characters appear for the server name.
PROBLEM: When dialed in from an English operating system to a
non-English server, the server name may display garbage characters
in the server box at the bottom of the Client SSU container.
IMPLICATION: User may be unable to identify server.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
13. On internationalized releases, some translations may be
inaccurate or inconsistent.
PROBLEM: Some text may not have been translated correctly, consistently,
or extraneous characters may be present, in both the usr interface
and the documentation.
IMPLICATION: User may not have a clear understanding of the
information being communicated.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
14. On non-English operating systems, the text may be cut off in the
SDR properties dialog.
PROBLEM: The translations of the properties may not fit within the
space provided, and the user is unable to scroll or resize the
dialog.
IMPLICATION: User may be unable to read the output.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
15. On non-English operating systems, the text may be cut off in the
status box.
PROBLEM: The translations of the status may not fit within the
space provided.
IMPLICATION: User may be unable to read the output.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
**************************************************************
L. EMC Integration
**************************************************************
1. SNMP Support : Some MIB files will not manually load in some versions
of HP OpenView.
PROBLEM: Some of the MIBs provided with ISC will not load in some
versions of HP OpenView.
IMPLICATION: HP OpenView will not provide as rich information when
displaying a SNMP trap from ISC.
WORK-AROUND: No work-around has been identified.
STATUS: Intel is investigating the possibility of fixing this erratum.
2. Unable to launch ISC applications from CA-TNG map.
PROBLEM: After ISC gets installed and some ISC servers being discovered
and added to the CA-TNG map, right-clicking on a ISC server and selecting
"Launch ISC" fails to start an ISC application.
IMPLICATION: It is not clear if the problem is in CA-TNG or the ISC-TNG
integration component.
WORK-AROUND: This problem can be easily fixed by rebooting the system
one more time. After the second reboot everything should work properly.
STATUS: Intel is investigating the possibility of fixing this erratum.
3. Slow server health status updates within HPOV.
PROBLEM: If a server's health status changes states, the change may not
be reflected from within HPOV by a change in icon color for up to 10 minutes.
This time will vary depending on network configuration, data traffic on the network,
etc.
IMPLICATION: Server health status as represented by icon color from within HPOV may not be
accurate immediately following a change of server health state.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.
**************************************************************
M. LAN Alert Viewer
**************************************************************
1. LAN Alert Viewer is not available on Simplified Chinese operating
systems.
PROBLEM: This functionality has not been enabled. It is not
available on Chinese operating systems.
IMPLICATION: User may not have access to this functionality.
WORKAROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum
Note: (*)Third-party brands and names are the property of
their respective owners.
******************************************************************
End of errata file
******************************************************************
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.