How to move Windows 2000 to different hardware
Article ID: 249694 Last Update Date: June 25, 2004 Version: 1.0
WARNING: The problem discussed in this article and link article is the most common problem and restrictions you try to restore the backup to different hardware. Other issues may occur due to software and hardware configurations. Many of these problems can be resolved by troubleshooting the specific issues that appear, but some compatibility issues may occur, which will restrict the successful restoration of the backup to different hardware.
This page
Summary More Information
summary
This article describes how to move Windows 2000 installation and programs installed on a computer to another on the shortest downtime. You can also use this procedure to replace a small system / boot drive to a larger system / boot disk drive, or restore Windows backups on a non-working computer to another for disaster recovery.
Important: It is recommended not to use this process for domain controllers.
More information
Windows Backup (NTBackup.exe) combines the hardware configuration information between the source computer and the target computer, and maintains a critical registry entry that the target computer is unique.
Windows Backup The following registry restore operations are processed by querying the following registry items in the Target Computer Registry:
HKEY_LOCAL_MACHINE / SYSTEM / CURRENTCONTROLSET / CONTROL / BackupRestore / KeysNottorestore
The registry entry indicates that some registry entries under HKEY_LOCAL_MACHINE / SYSTEM should not be rewritten when restored.
Any item will show that it is protected by the end of the backslash (/). Windows Backups Do not restore any of this and values below. If this item ends in a backslash and an asterisk (/ *), Windows backups merge this and all its child; ie, Windows backup view of the backup set (source) and the current registry (target) Start value to determine which item is preferred. Items with lower starting values priority. If the starting value is the same, don't make any changes. This process ensures that all services and devices can be initiated correctly after the restore system state, even in different hardware.
For example, if the value of the following items has a smaller start value on the backup set, this item is prioritized:
HKEY_LOCAL_MACHINE / SYSTEM / CURRENTCONTROLSET / SERVICES / DHCP
If the start value of the value of the same item in the current registry is smaller than the item to be restored, the current item is preferred.
Current result after backup restoration
-------------------------------------------------- ----
DHCP is running: Yes Yes?
DHCP is running: No Yes
DHCP is running: No No No No No No No No No
Note: Upgrade from Microsoft Windows NT to Windows 2000 Use the start value hkey_local_machine / system / currentControlset / Services / TCPIP = 0x02 in the system status backup. The newly installed Windows 2000 TCPIP service uses the start value 0x01. This means that the TCPIP settings are not restored from the backup unless the start value is the same. To resolve this issue, change the starting value on the source computer to 0x01 before the backup, or change the starting value on the target system to 0x02 before restoring the system state.
After restarting the target computer, Windows plug and play can handle any subtle differences in the hardware configuration.
Messages to consider before deciding to use this process
The drive number and% systemroot% folder should be fully migrated, on the source computer and the target computer, any target volume containing the system status component and the% SystemRoot% folder (in Windows 2000, this folder is Winnt) target volume must have The same drive letter. This means that if Windows is installed in the C: / Windows folder on the source computer, the Active Directory (NTDS) and Sysvol are installed on the drive D and E, the target computer must pre-install Windows to C: The / Windows folder, and includes drive D and E before you can successfully perform the restore operation. For additional information, click the article number below to see the article in the Microsoft Knowledge Base: 235478 Use non-default% systemroot% folder from failed system drive recovery
The hardware abstraction layer (HAL) source computer and target computer should use the same HAL type to achieve better results. Although there is no need to match the HAL type, if the HAL does not match, the migration process may not be completed correctly. To determine the computer HAL type used on each computer, follow these steps:
1. Click Start, point to Setup, click Control Panel, and then double-click System. 2. On the Hardware tab, click Device Manager, then view the list below the "Computer" branch. The possible values for system descriptions and related HAL include:
ACPI MULTIPROCESSOR PC = halmacpi.dll
ACPI UNIPROCESSOR PC = HalacPi.dll
Advanced Configuration And Power Interface (ACPI) PC = HALACPI.DLL
MPS Multiprocessor PC = halmps.dll
MPS UNIPROCESSOR PC = Halapic.dll
Standard pc = hal.dll
Compaq systempro multiprocessor or 100% compatible = halsp.dll
% SystemRoot% / Repair folder Contains the Winnt / RepAir folder for the source computer hardware and software profiles and setup.log files may be invalid for the target computer hardware. To update these files to make a corresponding repair in the future, implement the original upgrade on the target computer.
The NTFS volume may have to start a special filter driver before restoring the file containing the NTFS rollup analysis point. To do this, restart the target computer after restoring the operating system. These types of file examples include: Restable Remote Installation Services (RIS) images depends on a zero backup storage (SIS), you want to restore the remote storage server (RSS) file of the managed volume and use the heavy analysis point and require a filter driver. Other third-party services.
When the network is restored (whether it is restored to the original computer or another computer), you may encounter network component issues. For additional information, click the article number below to see the article in the Microsoft Knowledge Base:
810161 Run NTBackup Restore System Status Data Post-Device Manager does not display NIC or display error network card
Mobile Windows installation
Important: To back up and restore system status data so that after restoring data, the device can run normally, install the repair 810161 before the backup source system, and then install this hotfix on the target system before restoring the system status data. If this fix is unable to get this hotfix, follow these steps to manually make changes:
1. Start the Registry Editor. 2. Find and click Next: HKEY_LOCAL_MACHINE / SYSTEM / CURRENTCONTROLSET / CONTROL / BackupRestore / KeysNottorestore
3. Right-click "Plug & Play" and click Modify. 4. In the "Numerical Data" box, delete the CurrentControlset / Enum entry. 5. Exit the Registry Editor. Follow the steps below, back up Windows 2000 installation on a single computer and restore it to another computer:
1. On the source computer, log in as an administrator and stop all services that are typically stopped before performing backup operations. 2. Use the NTBackup.exe backup system / boot volume, system status, and associated NTDS and Sysvol volumes (if applicable). 3. On the target computer, use the product type that matches the source computer to perform a new Windows installation. Make sure that the drive letter of the target computer and the% SystemRoot% folder name match the source computer. If you are using a non-default (WinNT) folder name, click the article number below to see the article in the Microsoft Knowledge Base:
235478 Use non-default% systemroot% folder from failed system drive recovery
4. After the new installation is complete, log in to the target computer as an administrator. If the system to be restored is a domain controller, press the F8 key as before logging in as an administrator, and then click Directory Service Restore Mode. Create and format any other volumes that can be used to save system status components (such as sysvol, Active Directory or Active Directory log files), and assign drive numbers for them. Make sure that all drive numbers match the drive letter of the source computer. 5. In the root of the system partition, create a copy of the boot.ini file. This copy may be required in a step behind. 6. Start NTBackup.exe, on the Tools menu, click Options, click Restore tab, and then click "Unconditional replacement files". Restore system / startup volumes, system status, system status, system status from previously performed backups Make sure you can restore them to the Original Location option. Note: You must access all removable media (tape or magnet [Mo] discs) from the source system after the complete system restore, you must click "Restore the Restore Movable Storage Database" under the Advanced "button before starting restore ". 7. After full restore completion (before restarting the target computer), replace the Boot.ini file for a copy created in step 5. This is necessary to do this only when the ARC path in the rest of the Boot.ini file is different from the source boot.ini file. Finally, if the source system is still online, disconnect the network cable to avoid name conflicts. 8. Restart your computer. Log in as an administrator, start the original upgrade process by running Winnt32.exe in the I386 folder on the Windows installation CD. This operation refreshes the setup.log and registry files in the% SystemRoot% / Repair folder. Note: If the Hal does not match, the computer is not restarted after the computer is restored, and the original installation is performed for repair. To do this, follow these steps:
a. Restart your computer from the installation media. On the "Welcome to the installer" screen, press ENTER to perform a new installation. Please accept the license agreement when the license screen appears. The installer is next to search for previous installations for repair. b. When the destroyed installation is found, press the R key to repair the selected installation. The installer re-enumerates the computer's hardware (including HAL) and performs the original upgrade; at the same time, the installer will keep your program and user settings unchanged. This operation also uses an accurate information to refresh the% systemroot% / repair folder; if necessary, you can use this information to be typically repaired. Note: In Windows NT 4.0, the user profile is stored in the form of subfolders in% SystemRoot% / Profiles folder. In Windows 2000, if the installation is upgraded, you will continue to use an existing configuration file path. In the new Windows 2000 installation, the "Documents and Settings" folder is created in the volume where Windows 2000 installation is located to save the user profile. If the source system is upgraded from Windows NT, the original configuration file will be used after restore. However, after the in situ upgrade, you may have to change the item under the following path in the registry, change the configuration file path to% systemroot% / profiles: hkey_local_machine / Software / Microsoft / Windows NT / CurrentVersion / ProfileList
For additional information about the user profile, click the article number below to see the article in the Microsoft Knowledge Base:
214653 How to set the path to all user profiles
228445 User Profile Storage Area in Windows 2000
9. After completing the upgrade and determines everything, you can delete the source computer from the network and connect the target computer to the location where the source computer is located.
Note: The difference between the backup time and the time to restore to the new computer may affect the computer account on the domain controller. You may have to join a workgroup first and then re-join the domain.
For additional information, click the article number below to see the article in the Microsoft Knowledge Base:
162797 Trust relationship between workstations and domains failed
240240 Use "Backup" to restore the computer after the program is not running
233427 Using NTBackup.exe tools unable to back up files and folders
237556 How to solve the problem of Windows 2000 hardware abstraction
305356 After recovering the computer, Windows XP prompts you to reactivate
318715 Restore Network Adapter in Device Manager
292175 How to perform the original upgrade of Windows 2000
