Upgrading from Windows 2000 The procedures detailed in this section support upgrading from Windows 2000 to Windows Server 2003 on ProLiant servers. When upgrading from Windows 2000 with NIC teaming installed and active, an issue with a .DLL file halts the manual install. This issue does not occur during an unattended/scripted install. Prerequisites Follow these steps to prepare for a successful upgrade: - 1. Select a supported system platform from the server platforms listed earlier in Table 7.2 and verify that the system ROM is at the supported revision or later.
- 2. Double-click My Computer, then select Help from the menu bar and click on the About Windows option. Verify whether the system has the latest Microsoft service pack installed. If not, download the latest service pack from the Microsoft Web site (http://www.microsoft.com/windows2000/downloads/servicepacks/sp3/default.asp) and install it on your server. This action ensures that the server has the latest software components Microsoft supplied prior to the upgrade.
- 3. Download and install PSP for Windows 2000 v6.30A or later from the software and drivers Web site at http://h18023.www1.hp.com/support/files/server/us/locate/1989.html . This action ensures that all drivers and utilities provided by HP are suitable for upgrading to Windows Server 2003.
warning Failure to update drivers provided by HP before beginning the upgrade process might result in unexpected failures during the upgrade to Windows Server 2003. - 4. If Compaq Network Teaming is installed, unteam currently teamed NICs prior to the upgrade.
- 5. If installed, uninstall HP Smart Array Multipath Software v1.0 before proceeding with either upgrade method by following these steps:
- 1. Select the Control Panel from the Start Settings menu.
- 2. Select Add/Remove Programs.
- 3. Select Compaq Smart Array Redundancy Filter Driver from the list of components.
- 4. Click the Change/Remove button.
- 5. Click the OK button.
- 6. Click the Cancel button.
- 7. Shut down the server.
- 8. Disconnect the SCSI cable from the redundant HBA.
- 6. Choose either of the following installation paths and proceed to the associated section to complete the upgrade:
Manual Install After completing the tasks identified in the preceding section, continue the upgrade, as follows , to perform a manual install: - 1. Insert the Windows Server 2003 CD into the CD-ROM drive to begin installation. Follow all instructions for upgrading the server.
- 2. When prompted, choose to download updated setup files from Microsoft.
You will then get two yellow bangs (which is expected and should not halt the upgrade from going forward). One message tells you that IIS is going to be disabled during the upgrade, and the other message for the fax service.
The upgrade proceeds through copying the install files, and then reboots the server. The install continues smoothly through the following phases: preparing installation, installing Windows, and installing devices.
If you have Compaq Network Teaming installed, during the Installing Network phase, the installation stops (approximately with 32 minutes left of the install to complete) and a dialog box pops up that reads "Please insert the compact disc labeled 'Compaq Network Teaming Disk' into your CD-ROM and then click 'OK'."
- 3. When the dialog box appears, click Cancel for the installation to proceed. After this point, the installation proceeds uninterrupted until it is complete.
- 4. Install PSP for Windows Server 2003 v6.30A (or later), which is available at http://h18001.www1.hp.com/ partners /microsoft/windowsserver2003/support.html. The PSP contains numerous files. All files must be present in the same directory as the SETUP.EXE program for the PSP to be installed properly.
note During the PSP installation, the HP ProLiant Network Teaming and Configuration for Windows Server 2003 utility will be installed. Use this utility to reteam your NICs if you were previously using network teaming. - 5. If HP Smart Array Multipath Software v1.0 was uninstalled prior to the upgrade, install HP Smart Array Multipath Software v2.0. Then, reconnect the SCSI cable to the redundant HBA.
Unattended/Scripted Install After completing the tasks identified in the "Prerequisites" section, continue the upgrade as follows to perform an unattended/scripted install: - 1. Using SETUPMGR.EXE, create a distribution on a remote server (or any server that does not contain the OS being upgraded). The SETUPMGR.EXE program can be found in \support\tools\deploy.cab of the Windows Server 2003 CD.
- 2. Choose Completely Unattended Install and proceed through the Setup Wizard until it completes.
- 3. Add the following in the [UNATTEND] section of the UNATTEND.TXT file:
[UNATTEND] NTUpgrade=Yes
warning The UNATTEND.TXT file created must be modified to allow unattended upgrade installs . If you do not put the string specified in the previous paragraph into the file, the install automatically defaults to a clean install. - 4. If you are using the OEMPreinstall flag with the UNATTEND.TXT file, remove the following:
[UNATTEND] OEMPREINSTALL=YES
warning Upgrades might fail if the OEMPREINSTALL=YES option is enabled. - 5. Start the unattended upgrade. Copy the UNATTEND.TXT file and UNATTEND.BAT file created in steps 1 and 2 to the server you are planning to upgrade.
note If the upgrade is being performed over the network, the UNATTEND.TXT and UNATTEND.BAT files need to run off of the local server that is being upgraded. - 6. Verify that you have network connectivity so you can run and install the files off the network. Also, verify that you have the correct privileges to run from the Windist folder. (This should have been configured when you ran SETUPMGR.EXE, but should be verified .)
- 7. Execute UNATTEND.BAT locally. There will be a brief pause, but then the GUI should run and proceed with no interruptions if everything was set correctly when you ran the SETUPMGR.EXE file and modified the UNATTEND.TXT file. The server should reboot once.
- 8. Pay close attention to the BOOT.INI options that pop up. Verify that the installation is performing an upgrade and not a clean install at this point.
- 9. After the upgrade has completed and you are logged into Windows Server 2003, install v6.30 or later of the PSP for Windows Server 2003, which is available at http://h18001.www1.hp.com/partners/microsoft/windowsserver2003/support.html . The PSP contains numerous files. For the PSP to be installed properly, all files must be present in the same directory as the PSP's SETUP.EXE program.
- 10. If HP Smart Array Multipath Software v1.0 was uninstalled prior to the upgrade, install HP Smart Array Multipath Software v2.0. Then, reconnect the SCSI cable to the redundant HBA.
Known Issues and Workarounds During Upgrades Table 7.12 details the known issues with installing Windows Server 2003 on ProLiant servers and provides information about resolving them. Table 7.12. Known Issues and Workarounds During Upgrades | Network Issues | | Issue 1 | A Windows 2000 manual upgrade to Windows Server 2003 prompts a message reporting the need for CPQTEAM.DLL. | | Description | While manually upgrading to Windows Server 2003 from Windows 2000 Server, a message pops up informing the user that CPQTEAM. DLL is needed. | | Workaround | To continue with the upgrade, select Cancel on the pop-up message. After Windows Server 2003 has been installed, install the PSP for Windows Server 2003. | | Solution | HP engineers are working with Microsoft to resolve this issue. | | Storage Issues | | Issue 2 | HP Smart Array Multipath Software v1.0 is not compatible with Windows Server 2003. | | Description | HP Smart Array Multipath Software v1.0 must be uninstalled prior to upgrading to Windows Server 2003 to avoid incompatibility issues. | | Workaround | See solution. | | Solution | Uninstall HP Smart Array Multipath Software v1.0 prior to the OS upgrade. After the Windows Server 2003 upgrade and the PSP installation are complete, install HP Smart Array Multipath Software v2.0 (or later). | | Issue 3 | Software fault-tolerant volumes (dynamic disks) fail during driver upgrade or rollback. | | Description | When a device driver is updated for a device containing dynamic disks, the software fault-tolerant volumes located on these dynamic disks fail and require regeneration. | | Workaround | No workaround is available at this time. | | Solution | Scheduled to be fixed in a later Microsoft OS release. | | Issue 4 | Upgrading miniport driver for secondary device requires reboot. | | Description | When a device driver for a secondary device is updated, the Windows Server 2003 OS may request a reboot. | | Workaround | Reboot the server as prompted. | | Solution | Scheduled to be fixed in a later Microsoft OS release. | | System Health Issues | | Issue 5 | Startup and Recovery server options revert back to default settings after an upgrade. | | Description | Startup and Recovery server options modified from default settings automatically revert to the default settings after upgrading from Windows 2000 Advanced Server to Windows Server 2003, Enterprise Edition (see the following sample setting modifications). | | Options | Default Setting | Modified Setting Before Upgrade | Setting After Upgrade | | automatically restart | enabled | disabled | enabled | | writing debugging information | complete memory dump | small memory dump (64K) | complete memory dump | | Workaround | See solution. | | Solution | This OS feature works as designed. | | Issue 6 | ProLiant Advanced System Management controller driver for Windows Server 2003 (CPQASM.SYS) will not load on the ProLiant 3000, 5500, or 6500. | | Description | The ProLiant Advanced System Management controller driver for Windows Server 2003 (CPQASM.SYS) will not load on the ProLiant 3000, 5500, or 6500. The Windows Server 2003 version of this driver depends on ACPI support, and these ProLiant models do not support ACPI. Other components that depend on this driver might fail to load or might not provide full functionality. The following message will be displayed in CPQSETUP.LOG after the driver is installed: Name: hp ProLiant Advanced System Management  Controller Driver for Windows Server 2003 New Version: 5.30.3718.0 Beginning Silent Session... The software is not installed on this system, but is supported for installation. - the component will be installed Installation failed on at least one device. One of the devices may have been deleted through Device Manager and a reboot may be necessary to complete the driver installation for this device. The operation was not successful.
Opening Device Manager will show a "yellow bang" on the HP ProLiant Advanced System Management Controller. Examining the properties for this device will show the following message: Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
| | Workaround | Install v5.30.2195.1 (or later) of the ProLiant Advanced System Management controller driver for Windows 2000. The Windows 2000 version of this driver does not have a dependency on ACPI support and provides the same functionality on the affected systems as the Windows Server 2003 version of the driver. | | Solution | A Windows Server 2003 driver will be available shortly at the following location: http://h18001.www1.hp.com/partners/microsoft/windowsserver2003/support.html . |
|
