Determine Windows Channel (Retail or OEM or Volume)
You want to P2V a Windows machine but you want to avoid activation issues. With OEM and retail licenses the P2V conversion will result in reactivating the Windows installation because of the new virtual hardware. Since the virtual hardware does not comply to the OEM license, the activation will fail.
1 – Make sure you know what version of Windows you are running. Check the Microsoft Product Code against this list:
The following table lists the English MPC codes for Windows Server 2003.
|Product and Channel||WPA||MPC||Expiration date|
|R2 Datacenter x86||No||69754||No|
|R2 Datacenter x64||No||76871||No|
|Enterprise Edition 32-bit retail||Yes||69713||No|
|Enterprise Edition 32-bit volume licensing||No||69713||No|
|Enterprise Edition 32-bit OEM||Yes (see note)||69713||No|
|Enterprise Edition 32-bit evaluation||Yes||69763||Yes|
|Enterprise Edition 32-bit checked build||Yes||69713||No|
|Datacenter Edition 32-bit retail||Yes||69754||No|
|Datacenter Edition 32-bit OEM||Yes||69754||No|
|Standard Edition 32-bit retail||Yes||69712||No|
|Standard Edition 32-bit volume licensing||No||69712||No|
|Standard Edition 32-bit OEM||Yes (see note)||69712||No|
|Standard Edition 32-bit evaluation||Yes||69763||Yes|
|Web Edition 32-bit retail||Yes||69753||No|
|Web Edition 32-bit volume licensing||No||69753||No|
|Web Edition 32-bit OEM||Yes (see note)||69753||No|
|Web Edition 32-bit evaluation||Yes||69763||Yes|
|Enterprise Edition 64-bit retail||No||69770||No|
|Enterprise Edition 64-bit volume licensing||No||69770||No|
|Enterprise Edition 64-bit OEM||No||69770||No|
|Enterprise Edition 64-bit evaluation||No||69763||No|
|Enterprise Edition 64-bit checked build||No||69770||No|
|Datacenter Edition 64-bit retail||No||69769||No|
|Datacenter Edition 64-bit OEM||No||69769||No|
|Volume licensing||270, 470, 640-659|
|MSDN||197 – 198, 335 – 338, 365 – 367, 425|
|OEM||OEM, 550, 630 – 636, 665 – 669, 671 – 679, 681 – 689, 691 – 699|
|Other channels||000, 436, 460|
To view the PID of a computer that is running, follow these steps:
- Right-click My Computer, and then click Properties.
- On the General tab, the PID appears in the Registered to box.
If you are running a Retail or OEM version you will want to convert it to a Volume version before doing the conversion.
If the machine is a domain controller you will want to follow these special instructions.
A lot has been written about P2V’ing Windows Domain controllers. The preferred way is to build a new domain controller based on a virtual machine and demote the physical domain controller.
Rebuilding a new domain controllers may not always be possible due to time constraints or other dependencies like additional software running on the domain controller which can not be easily migrated.
However, P2V’ing of a domain controller is possible under the right conditions. These conditions are the same for any other transactional service like a Microsoft SQL server or a Microsoft Exchange server and comes to the following point:
‘Make sure all transactional processes are stopped during the P2V process’
For a Windows domain controller the transactional system consists of the Active Directory database. For a Windows 2000 and Windows 2003 domain controller the Active Directory service can’t be stopped. To solve this problem, boot the system in the Directory Service Restore Mode.
Directory Services Restore Mode (DSRM) is a special boot mode for repairing or recovering Active Directory. It is used to log on to the computer when Active Directory has failed or needs to be restored.
In DSRM mode Active Directory is not running and no transactions are occurring. In this state a hot clone can be made. After the hot clone is made, cleanup the system and restore the original ip address of the server.
The following steps describe the complete P2V process for a Windows 2000/Windows 2003 domain controller:
- If any other transactional services are running on the domain controller, stop and disable these services
- Boot the physical domain controller in Directory Services Restore Mode (DSRM)
- Clone the physical domain controller with VMware Converter
- After the conversion is completed, disable the nic(s) of the physical domain controller (through the physical console, iLO, DRAC or other consol tool). This prevents the physical server from being online on the network ever again.
- Shutdown the physical domain controller
- Start the virtual domain controller in Directory Services Restore Mode (DSRM). This prevents the directory service from starting and gives room to cleanup the system.
- Remove any unnecessary software, like hardware monitor agents (e.g. HP Insight Agents) and unnecessary hardware drivers. See this post for more information.
- Remove inactive devices in the device manager. See this post for more information.
- Configure the original IP address(es) to the virtual domain controller
- Enable any other transactional services you disabled in step 1
- Boot the virtual domain controller in normal mode.
The virtual domain controller should now be operational.
Be warned: from now on the physical domain controller can never be brought back online! This will result in USN rollback and Active Directory replication will not work correctly. See Microsoft Knowledge Base Article KB875495 for more information.
Perform the following checks to validate the domain controller:
- Check the eventlogs
- Check for NTDS Replication errors
- Run dcdiag from the windows support tools
- Run netdag from the windows support tools
- Create a test user on another domain controller and validate it’s replicated to the virtual domain controller
- Delete the test user on the virtual domain controller and validate the deletion is replicated to another domain controller
If you do resize the disk where the Active Directory replica root path is placed (e.g. %SystemRoot%Sysvol) during the P2V process, you will get the following error:
The File Replication Service has detected that the replica root path has changed from “d:sysvoldomain” to “d:sysvoldomain”. If this is an intentional move then a file with the name NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path.
Creating an empty file with the name NTFRS_CMD_FILE_MOVE_ROOT recreate the sysvol folder and solve this problem.