Use vmwarevm to migrate existing servers and networks (8)

4. migrate Windows NT/2000/2003 Networks
For Windows networks, server migration is only involved, because Windows clients are easy to install, whether on physical hosts or virtual machines.
For servers above Windows 2000, "Migration" is required only when necessary, because for Windows products, whether it is server or workstation, installation is required after a period of time. Instead of "migrating" a system that may have problems, it is better to install a system "completely new" in the Virtual Machine and restore the data to the corresponding virtual machine. For Windows 2000 systems that cannot be migrated through "backup" or "recovery", you can also use ghost to clone the pre-migration server to a virtual machine and then use the VMware p2v tool, replace the corresponding driver to complete the migration.
For Windows NT, Windows 2000, and Windows Server 2003, the migration methods, steps, and tools are the same. We will take the migration of Windows 2000 Server as an example to introduce how to migrate these products.
Next, we will use an example to introduce the migration steps and methods for Windows 2000 Server.

4-1 preparations before migration
Before migrating a Windows server, you must perform the following operations:
① Use the disk check tool to check each hard disk and partition, and modify the error. Sort out the hard disk if conditions permit.
② Delete unnecessary software (such as some software installation programs) and other data (such as movies and MP3) on the hard disk, and "Clear the recycle bin ".
③ Install the latest patch (Upgrade Windows NT to SP6, Windows 2000 to SP4, and Windows 2003 to SP1 ).
④ Record the IP address, subnet mask, gateway, DNS, and other parameters of the current server. Record other related parameters.

4-2 upload the pre-migration server to the ghost Console
Use the ghost boot disk wizard tool to generate a boot floppy disk with a pre-migration server NIC driver and an AMD pcnet (vmwarevm Nic) NIC Driver. Next, refer to the content in the "2-3 ghost console upload (upload the pre-migration server to ghost server)" section, start the Windows 2000 server by using disk 1 and Disk 2, upload the entire hard disk on the Windows 2000 Server to the ghost console, and save the file name as w2kser. gho.
4-3 create a Windows 200 Server Virtual Machine in VMware gsx Server
Refer to the section "13.4.3 how to create a new Virtual Machine" to create a virtual machine for Windows 3.2 server on a VM of VMware gsx Server 2000. Note the following when creating a VM:
① Use custom to create a custom image.
② Select a guest operating system and select the corresponding operating system.
③ In "startup/shutdown options", specify the startup account.
④ Allocate appropriate memory for the VM. Generally, this can be considered based on the host memory of the pre-migrated server and the maximum memory/available memory of the migrated physical host. You can first allocate 64 MB to MB less memory than the original pre-migration server. After the migration is completed, you can monitor the status of the Virtual Machine. If the memory is insufficient, you can increase it. If the memory is left, it can continue to decrease (it is much easier to increase or reduce memory on virtual machines than on physical hosts ).
⑤ Use "bridge network ".
⑥ When selecting the disk interface, select the default configuration (for Windows NT and Windows 2000, The SCSI hard disk is buslogic, and for Windows 2003, The SCSI hard disk is LSI logic). When creating a disk, the closeness is the same as that of the original physical host. If the hard disk of the original physical host is not large and there is enough space on your server, you can select "allocate all disk space now" when creating the hard disk to obtain maximum performance. If you have limited space or the hard disk of the original physical host is large, you can choose not to use this option.

Figure 19 modifying Nic attributes
4-4 send the image file to the VM from the ghost Console
In the VM created in the previous section, use the image file "Disk 1 and Disk 2 of the VM" as the soft drive to start the VM, refer to the "2-4 ghost console distribution-distribute the pre-migration server image to the Virtual Machine)" section, the name "w2kser. the gho image file is distributed to the VM created in the previous section.
After the distribution is completed, shut down the virtual machine. Edit the virtual machine configuration file and set the NIC attribute to "vmxnet", as shown in Figure 19.

4-5 run p2v Tool
Install the VMware p2v program on the server where the VMware gsx server is installed. Currently, the VMware p2v version is 2.1. It is easy to install and can be installed by default. After that, register VMware p2v for use.
Run "VMware p2v assistant 2.1" in the VMware program group to go to p2v. On the next page, select the first item "perform a system reconfiguration ......", Convert an existing virtual machine.

Figure 20 select a virtual machine image
On the next page, select "open an existing virtual disk", click "Browse", browse and select the cloned virtual machine in the previous section, and click "Next, 20.
Then, p2v displays the virtual machine operating system and its information, as shown in Figure 21.

Figure 21 virtual machine information Figure 22 select the converted hardware environment

As shown in Figure 21, information about the virtual hard disk operating system in the same virtual machine is displayed. On the next page, select the target environment (that is, the product where the VM is running, such as vmware workstation, gsx, or ESX), and select "gsx Server 3.0 or higher ", then click "Next". p2v starts to convert (this step is fast), and the conversion is completed, as shown in 22, 23, and 24.

Figure 23 conversion started figure 24 conversion completed