Server Manager 6.0 - Service Pack 2: Release Notes ============================= * Installation Notes: * Installing Server Manager Service Pack Requirement Whenever you experience a problem with Server Manager 6.0 the latest Service Pack should be installed. This Server Manager Service Pack is required when using Server Manager 6.0 with Windows NT 4.0, Terminal Server Edition. * Server Manager Reboots It is highly recommended that the "reboot now" option be selected at the end of both the Server Manager install and the Service Pack install. Immediately after each reboot, logon as the administrator of the local system to finish each install. If either of these installs fails after the logon, follow the note below. * Server Manager 6.0 - Service Pack 2 contains fixes from Service Pack 1. ============================= * Problems FIXED in SM 6.0 Service Pack 2: AMS incorrectly handles dates beyond December 31, 1999. Displays years after 1999 as "100" in alerts(Message Boxes) and logs (NT Event Log). ============================= * Problems FIXED in SM 6.0 Service Pack 1: NT_VP970476 - The following drivers cannot be stopped or removed without a reboot: incadrv, lcddrv, and memdrv. NT_VP980008 - The following Predator8 Server Manager functions are disabled: Second Inca Temperature sensors Second Inca Voltage Sensors Secondary Memory & LST errors Secondary Processor modules Port UNIX VDB performance enhancements NT_VP970866 - K2: System does not shutdown on fatal I/O temperature. NT_VP970487 - LCD display does get updated when warning status changes NT_VP970858 - K2: Memory instrumentation reports for 1 memory board on K2 With 4 GB of memory on a K2 unit with 12 DIMMs on the primary board and 4 DIMMs on the secondary board, SM reports only 16 memory slots instead of 32 and shows only 12 DIMMs present. NT_VP970859 - K2: Memory instrumentation reports max mem for DIMM as 0 MB Under more info when viewing the memory instrumentation on a K2 with 4GB of memory, reports that the maximum memory is 0MB. NT_VP980000 - Single Processor system doesn't report CPU Speed. With Server Manager 6.0 installed on a system with a single processor and viewing the processor information, the Max and Current Speed is reported as "Unsupported". NT_VP980012 - Setting WatchDog interval to 1 can reset the system Setting WatchDog interval to 1 can reset the system because the first poke may not occur in time. NT_VP980013 - incadrv, memdrv, and lcddrv don’t report messages to the NT EventLog NT_VP980014 - The K-2 Power Supply readings are reversed due to EEPROMS wired backwards NT_VP980026 - System resets before a dump can complete. The default WatchDog Interval prevents dumps of large memory systems Since time INCA is not poked during the dump process, the WD timer expires resetting the system before the dump can complete. NT_VP970675 - Server hangs during SMM shutdown after thermal event After a thermal event occurs on the SMM card, an error message is displayed during the shutdown which reads: "The application failed to initialize because the window station is shutting down..." The popup message stays on the screen until the "OK" button is pressed, thus preventing the system from coming down properly. After the message is cleared, all icons are cleared from the desktop, the start menu does not respond, and the machine is hung. Mouse control remains, however. The only way to recover use of the machine is to shut it power the machine off manually. NT_VP970842 - Uninstall hangs or displays an error NT_VP980009 - AMSDB Database Source Name not installed During initial install, the AMSDB Source Name did not get installed. NT_VP980010 - LANDesk hangs during startup. Following initial installation, the Server Manager application appeared to be hung at the LANDesk splash screen. NT_VP970731 - Event Log entries are missing descriptions The Intel Alert Originator service, Intel Server Monitor service, and the SCSIDMIService are missing message files. All other services have messages. NT_VP970837 - “Check Logical Unit” displayed on LED Server Manager causes the LED on the front panel of the server to read: "Check Logical Unit" NT_VP980007 - Cannot browse LogData and LogControl groups in basebrdm.mif Cannot browse Log Data and Log Control groups for basebrdm.mif, because baseboard instrumentation doesn’t supports the above groups. NT_VP980016 - Console-Only installation - cannot view local system If console only is installed, the user cannot view itself in the Server Manager browse list. Only other systems running server manager are viewable. ================================ * Server Manager Icons Missing or Unavailable servmon.ini was not installed properly for Terminal Server. This problem will occur if the system is in execute mode during the install. The command "change user/install" failed or was not used. The AutoUpdate.cmd script does execute this command. If this script was not used to install Service Pack 1, this failure will occur. If Server Manager 6.0 was installed using setup.exe instead of setup.cmd, this problem will also occur. The best way to handle this problem is to uninstall Service Pack 1 and/or Server Manager 6.0 and then reinstall them. * Clarification on Sending Pages - Specifying the Delay When configuring AMS alerts to send a page, the phone number for the pager service should be followed by at least 6 commas(,). Each comma specifies a very small unit of delay. Make sure that you enter at least 6 commas, otherwise the pager may not receive the complete message. The number of commas controls the length of delay. The delay required will differ depending on the pager service. Some services will disconnect if a tone is not transmitted within a specified time. * Firmware Updates for Server Management Components The directory \Servrmgr\FWupdates contains the most current firmware for the Hot Swap SCSI Backplane(HSBP) and the Server Management Board (SMB). See the \Servrmgr\FWupdates\readme.txt file for instructions on flashing HSBP firmware and flashing SMB firmware. The file \Servrmgr\FWupdates\smbfw115.exe creates DOS bootable diskette containing HSBP I2C firmware versions 1.12 and 2.11, and flash utilities. Also included are SMB firmware versions 1.00.15 for 4300 and 2.00.45 for 4700. * CPU Speeds May be Reported as "Unsupported" This will happen when CPU's are disabled in BIOS or have a failed VRM(Voltage Regulator Module). Server Manager can not report which CPU's are disabled or have a failed VRM. The CPU with a reported speed of "Unsupported" may be functioning properly. * Installing SM 6.0 with NT 4.0 Release Candidate Service Packs When a Release Cadidate Service Pack is installed, SM 6.0 may not install because it wrongly gives the error that SP 3 or higher is required. To bypass this problem, follow these steps: 1. Begin SM 6.0 installation and wait for the Welcome Dialog to appear. 2. Launch the explorer and open the %temp% directory. In the _istmpX.dir (where X represents a number from 0 or higher), rename the file uninst.dll to uninst.old 3. From the ValuePluse 6.5 CD, copy the file \servrmgr\ServerManagerServicePack61\uninst.dll to the %temp% directory. 4. Go back to the SM 6.0 Setup at the Welcome Dialog and continue setup. The SP 3 error message should not appear. * AMS Updates Fail When Running Modem Arbitrator When creating events under AMS, the user may receive the message, "Unable to update events, could not contact the alerting host." When the Server Manager Modem Arbitrator is open this error will occur. * SM 6.0 Install Overwrites SNMP Extension Agent Entries in Registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SNMP\ Parameter\ExtensionAgents key is incorrectly modified by the install of SM 6.0. The SM 6.0 Service Pack will attempt to restore the lost entries if they are available from previous control sets. If the lost entries can not be restored by the Service Pack, they can only be restored by the reinstalling applications that provide a SNMP extension agent DLL. Some of the applications providing extension agent DLL's are WINS, DHCP, and IIS. From NCR, Master Minder provides an extension agent DLL. * SM 6.X Intel LANAdapterExtensionGroup causes a access violation If an Intel EtherExpress(TM) PRO/100 B LAN Adapter is not present in a system and the Intel LANAdapterExtensionGroup is selected in the DMI browser, the following exception occurs and the Intel Server Monitor service is stopped: NTSM.exe -- Access Violation (0xc00000005), Address: 0x01d14063 To workaround this problem, close the Server Manager application and restart the Intel Server Monitor service and the Server Manager application. * SM 6.x Installation date is not present for NCR Network Adapter When viewing NCR Network Adapter Information -> Component ID, in the DMI Browser, the installation date that appears is: 00/00/0000 - 00:00:00. This is a known issue that is not corrected at this time. This reading does not cause any harm. * SM 6.X Service Pack cannot stop services during installation Sometimes during installation, an error is reported on a service while the services are being stopped. This can occur if a service is in a hung or uncontrollable state. The setup should be stopped and windows should be restarted. Restart the setup program again. * Local System information is displayed in test mode. If an alert is configured on a Server Manager console for a remote system and the alert is tested using the test button, the time and date information displayed in the alert is the local system's instead of the remote system. This problem only occurs in test mode. When an actual thresho