timmy90210
MIS
Has anyone had luck doing this? We are using Compaq hardware. I have a procedure from Sungard, hey tells us it works but we have been unable to successfully get results. Any help would be great. IIS also gives us isues after the move to new hardware.
Here is the doc from sungard:
Restoring Windows 2000 to different hardware:
Revised: 29 January 2003
Important Note: Although SunGard Recovery Services has had much success with the
following procedure, it is not guaranteed by SunGard Recovery Services or Microsoft to
work in every Windows 2000 environment. The information below was taken in part from
Microsoft Knowledgebase article Q249694: How to Move a Windows 2000 Installation to
Different Hardware. This process will take about 45 minutes to complete after the data is
restored.
General
All servers assigned to the test will be in the command center, in a rack-mounted configuration.
To avoid sharing consoles between servers, the command centers will have the Keyboard,
Mouse and Video extended via CAT5 cabling to up to 18 individual consoles within the
command center. If more than 18 servers are required, console sharing will be necessary. Any
required stand-alone tape drives will be attached to the SCSI bus of the server indicated in the
test plan. Some of the larger tape autoloaders and libraries will be located in a common tape
room and connected via differential SCSI or fiber channel.
Since the hardware will generally have the latest BIOS updates, etc applied, updated drivers
will be provided. Because of this configuration, the servers will be set up for use according to
the OS specified in the test plan. “Windows 2000 Server” or “Windows 2000 Advanced Server”
should be specified. The size of the windows system partition should also be specified.
Pre-test Set up
Each server will be set up with one RAID-5 logical drive per array controller. If specific array
configurations are required, this should be communicated during the pre-test conference call
and indicated on the test plan. SunGard will make every effort to accommodate these
requirements if possible. Windows 2000 will be pre-installed on a 6GB NTFS partition if no
partition size is specified. The system identification (SID) information will be removed using the
“sysprep” utility. When you arrive in the command center, the systems’ license agreement will
be displayed. After acceptance, you will be presented with the mini setup program to set up
networking and system identification.
NOS Setup
Ensure that the drive letter and %SystemRoot% folder names match those of the source
computers. If you are using a non-default (Winnt) folder name, please refer to the following
Microsoft Knowledge Base article: Q235478 Recovering from Failed System Drive with Non-
Default %SystemRoot% Folder.
Page 1 of 4
SunGard Availability Services
Since all of the servers have multiple NICs installed, it will be necessary to disable (not
uninstall) all unused NICs from within device manager. It is especially important to disable
the token ring NIC if it is not being used. If the token ring NIC is not disabled and it is not
connected to a MAU, system resources will be used to try to join a ring. This will cause the
mouse and keyboard to freeze frequently. All NICs being used must be forced to 100MB
full duplex.
Using Disk Management, create, format, and assign drive letters to any additional volumes that
may be required to hold a system-state component (for example, SYSVOL, Active Directory, or
Active Directory Log files). Ensure that all drive letters match the source computers. It is also
necessary to disable the option to automatically reboot on system error in the startup
and recovery settings under the advanced tab in the system properties.
After setup is completed, apply the service pack level that is used in production. This is a very
important step. If the proper service pack is not applied, the system restore will fail. This will
also address any open system files during the restore.
If a Compaq server is being used, apply the Compaq Support Paq. Insert the Compaq Smart
Start CD provided and run %CDROM%:\CPQSUPSW\NTCSP\Setup.exe. Normally, only the
drivers should be selected. If you are not familiar with the CSP, your recovery specialist will
assist you.
Install the proper drivers for the tape drive if applicable. These can be found in the
C:\DRIVERS directory. Install the backup software as specified by the manufacturer and apply
the latest service pack. This will assure that the backup software recognizes the updated
hardware. If only data is being restored, complete the installation of any required applications.
If remote control software, such as PC Anywhere or Win-VNC is used in production, install and
configure it with the same settings. If you are using Citrix Metaframe, it should also be installed
using the same settings as in production.
Run NTBACKUP and click on the “Emergency Repair Disk” button. Check the “Also backup
registry to repair directory” box and click OK. You will get an error message that the operation
failed because there is not a disk in the floppy drive, but the registry will be backed up to the
repair folder. Copy the ENTIRE contents of the %SYSTEM%\REPAIR folder and any subfolders
to another location on the c: drive in case it may be needed later.
System Restore
Before restoring the system state, start device manager and uninstall all NICs and any
Video Adapters listed. Select “NO” if asked to reboot. These will be rediscovered after
reboot. If you are restoring over the wire, uninstall any unused NIC before the restore and
uninstall the required NIC after restore, but before rebooting the server.
Page 2 of 4
SunGard Availability Services
If a full file and system state restore is being done, select the “overwrite files” and “restore
registry” options within the backup software. The restore may be initiated by session to save
time. If the tape database is cataloged or merged, deselect the following files:
C:\BOOT.INI
C:\NTDETECT.COM
C:\NTLDR
Restore the system/boot volume, the system state, and associated volumes from the backup
that you performed previously. Make sure that you select the options to restore them to
"original location" and to always overwrite existing files in the backup program. If this is the first
server being restored, select the "When restoring replicated data sets, mark the restored data
as the primary data for all replicas" option.
Before restarting the computer, uninstall any remaining NICs from within Device
Manager. If this is the first server being restored in an Active Directory server, boot into Active
Directory Restore Mode. Run NTDSUTIL from the CMD prompt and perform an Authoritative
Restore.
After the server has been restored, it is recommended that you perform an in-place
upgrade of the OS by running WINNT32.EXE from within the Windows GUI. This will
assure that the hardware specific settings are discovered. If the computer does not restart after
restoration because of HAL mismatches, you can boot using the Windows 2000 installation
disk and perform an in-place installation / repair:
• Boot to the Windows 2000 Installation CD.
• At the first screen, hit <ENTER>=Continue
• At the next screen, hit <F8> to accept the license agreement
• After it searches your hard drives and finds your installation, hit <R>=Repair
• Allow setup to replace non-Microsoft files if prompted.
• After reboot, the system will run through the GUI-based portion of setup and perform a
hardware discovery.
If the system starts with a “black Screen” condition, cold boot the server and restart in SAFE
MODE. After upgrading, it is advisable to re – apply the service pack and SSD.
Page 3 of 4
SunGard Availability Services
What does a Windows 2000 in-place upgrade change and not change?
When you perform an in-place upgrade:
1. Service Packs, hotfixes, and IE upgrades are rolled back.
2. Default registry values are restored.
3. Default permissions are reapplied.
4. COM and WFP are reregistered.
5. Plug and Play devices and the HAL are re-enumerated.
6. Drive letters are changed based upon the current drive and partitions.
The following is NOT changed:
1. Installed components and programs.
2. Passwords.
3. Third-party registry entries.
4. The computer's role.
NOTE: If you upgraded your computer from Windows NT 4.0, profiles were stored at
%SystemRoot%\Profiles. The in-place upgrade creates a \Documents and Settings folder
and changes the registry profile to point to it. To fix the problem, use the Registry Editor to
navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList. For each user, there will be a SID sub-key and a Value Name
of ProfileImagePath. Change the string value to point to
%SystemRoot%\Profiles\<UserName>.
Here is the doc from sungard:
Restoring Windows 2000 to different hardware:
Revised: 29 January 2003
Important Note: Although SunGard Recovery Services has had much success with the
following procedure, it is not guaranteed by SunGard Recovery Services or Microsoft to
work in every Windows 2000 environment. The information below was taken in part from
Microsoft Knowledgebase article Q249694: How to Move a Windows 2000 Installation to
Different Hardware. This process will take about 45 minutes to complete after the data is
restored.
General
All servers assigned to the test will be in the command center, in a rack-mounted configuration.
To avoid sharing consoles between servers, the command centers will have the Keyboard,
Mouse and Video extended via CAT5 cabling to up to 18 individual consoles within the
command center. If more than 18 servers are required, console sharing will be necessary. Any
required stand-alone tape drives will be attached to the SCSI bus of the server indicated in the
test plan. Some of the larger tape autoloaders and libraries will be located in a common tape
room and connected via differential SCSI or fiber channel.
Since the hardware will generally have the latest BIOS updates, etc applied, updated drivers
will be provided. Because of this configuration, the servers will be set up for use according to
the OS specified in the test plan. “Windows 2000 Server” or “Windows 2000 Advanced Server”
should be specified. The size of the windows system partition should also be specified.
Pre-test Set up
Each server will be set up with one RAID-5 logical drive per array controller. If specific array
configurations are required, this should be communicated during the pre-test conference call
and indicated on the test plan. SunGard will make every effort to accommodate these
requirements if possible. Windows 2000 will be pre-installed on a 6GB NTFS partition if no
partition size is specified. The system identification (SID) information will be removed using the
“sysprep” utility. When you arrive in the command center, the systems’ license agreement will
be displayed. After acceptance, you will be presented with the mini setup program to set up
networking and system identification.
NOS Setup
Ensure that the drive letter and %SystemRoot% folder names match those of the source
computers. If you are using a non-default (Winnt) folder name, please refer to the following
Microsoft Knowledge Base article: Q235478 Recovering from Failed System Drive with Non-
Default %SystemRoot% Folder.
Page 1 of 4
SunGard Availability Services
Since all of the servers have multiple NICs installed, it will be necessary to disable (not
uninstall) all unused NICs from within device manager. It is especially important to disable
the token ring NIC if it is not being used. If the token ring NIC is not disabled and it is not
connected to a MAU, system resources will be used to try to join a ring. This will cause the
mouse and keyboard to freeze frequently. All NICs being used must be forced to 100MB
full duplex.
Using Disk Management, create, format, and assign drive letters to any additional volumes that
may be required to hold a system-state component (for example, SYSVOL, Active Directory, or
Active Directory Log files). Ensure that all drive letters match the source computers. It is also
necessary to disable the option to automatically reboot on system error in the startup
and recovery settings under the advanced tab in the system properties.
After setup is completed, apply the service pack level that is used in production. This is a very
important step. If the proper service pack is not applied, the system restore will fail. This will
also address any open system files during the restore.
If a Compaq server is being used, apply the Compaq Support Paq. Insert the Compaq Smart
Start CD provided and run %CDROM%:\CPQSUPSW\NTCSP\Setup.exe. Normally, only the
drivers should be selected. If you are not familiar with the CSP, your recovery specialist will
assist you.
Install the proper drivers for the tape drive if applicable. These can be found in the
C:\DRIVERS directory. Install the backup software as specified by the manufacturer and apply
the latest service pack. This will assure that the backup software recognizes the updated
hardware. If only data is being restored, complete the installation of any required applications.
If remote control software, such as PC Anywhere or Win-VNC is used in production, install and
configure it with the same settings. If you are using Citrix Metaframe, it should also be installed
using the same settings as in production.
Run NTBACKUP and click on the “Emergency Repair Disk” button. Check the “Also backup
registry to repair directory” box and click OK. You will get an error message that the operation
failed because there is not a disk in the floppy drive, but the registry will be backed up to the
repair folder. Copy the ENTIRE contents of the %SYSTEM%\REPAIR folder and any subfolders
to another location on the c: drive in case it may be needed later.
System Restore
Before restoring the system state, start device manager and uninstall all NICs and any
Video Adapters listed. Select “NO” if asked to reboot. These will be rediscovered after
reboot. If you are restoring over the wire, uninstall any unused NIC before the restore and
uninstall the required NIC after restore, but before rebooting the server.
Page 2 of 4
SunGard Availability Services
If a full file and system state restore is being done, select the “overwrite files” and “restore
registry” options within the backup software. The restore may be initiated by session to save
time. If the tape database is cataloged or merged, deselect the following files:
C:\BOOT.INI
C:\NTDETECT.COM
C:\NTLDR
Restore the system/boot volume, the system state, and associated volumes from the backup
that you performed previously. Make sure that you select the options to restore them to
"original location" and to always overwrite existing files in the backup program. If this is the first
server being restored, select the "When restoring replicated data sets, mark the restored data
as the primary data for all replicas" option.
Before restarting the computer, uninstall any remaining NICs from within Device
Manager. If this is the first server being restored in an Active Directory server, boot into Active
Directory Restore Mode. Run NTDSUTIL from the CMD prompt and perform an Authoritative
Restore.
After the server has been restored, it is recommended that you perform an in-place
upgrade of the OS by running WINNT32.EXE from within the Windows GUI. This will
assure that the hardware specific settings are discovered. If the computer does not restart after
restoration because of HAL mismatches, you can boot using the Windows 2000 installation
disk and perform an in-place installation / repair:
• Boot to the Windows 2000 Installation CD.
• At the first screen, hit <ENTER>=Continue
• At the next screen, hit <F8> to accept the license agreement
• After it searches your hard drives and finds your installation, hit <R>=Repair
• Allow setup to replace non-Microsoft files if prompted.
• After reboot, the system will run through the GUI-based portion of setup and perform a
hardware discovery.
If the system starts with a “black Screen” condition, cold boot the server and restart in SAFE
MODE. After upgrading, it is advisable to re – apply the service pack and SSD.
Page 3 of 4
SunGard Availability Services
What does a Windows 2000 in-place upgrade change and not change?
When you perform an in-place upgrade:
1. Service Packs, hotfixes, and IE upgrades are rolled back.
2. Default registry values are restored.
3. Default permissions are reapplied.
4. COM and WFP are reregistered.
5. Plug and Play devices and the HAL are re-enumerated.
6. Drive letters are changed based upon the current drive and partitions.
The following is NOT changed:
1. Installed components and programs.
2. Passwords.
3. Third-party registry entries.
4. The computer's role.
NOTE: If you upgraded your computer from Windows NT 4.0, profiles were stored at
%SystemRoot%\Profiles. The in-place upgrade creates a \Documents and Settings folder
and changes the registry profile to point to it. To fix the problem, use the Registry Editor to
navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList. For each user, there will be a SID sub-key and a Value Name
of ProfileImagePath. Change the string value to point to
%SystemRoot%\Profiles\<UserName>.
but I think you might to look at the SYSPREP tool?
