Make sure that all transaction processing is stopped during the P2V process

Make sure that all transaction processing is stopped during the P2V process

Much has been written about Windows P2V Services domain drivers. The preferred way is to create a new domain controller based on the virtual machine and degrade the physical domain controller.

Due to time constraints or other dependencies, such as additional software running on the domain controller, it is not always possible to build new domain controllers and they cannot be easily migrated.

However, a P2V 'range controller is possible under the right conditions. These terms are the same for all other transaction services, such as Microsoft SQL Server or Microsoft Exchange Server, do the following:

Make sure that all transaction processing is stopped during the P2V process

In a Windows domain controller, the transaction system includes an Active Directory database. For Windows 2000 and Windows 2003 domain controllers, Active Directory cannot be stopped. To resolve this issue, start the system directory service in restart mode.

Directory Services Recovery Mode (DSRM) is a specialized startup mode for restoring or restoring Active Directory. It is used to log on to the computer when Active Directory fails or needs to be restored.

In DSRM mode, Active Directory is not running and there are no events. In this case, a hot clone can be created. After creating the hot clone, the system is cleaned and the original IP address of the server is restarted.

The following steps describe the entire P2V process for a Windows 2000 / Windows 2003 domain controller:

If other transaction services are running in the domain controller, stop and disable those services
Starting the physical domain controller in Directory Services Recovery Mode (DSRM)
Clone the physical domain controller with VMware Converter

When the conversion is complete, disable the physical domain controller nicks (via the physical console, ILO, DRC, or other console device). This prevents the physical server from returning to the network on the network.

Stop the physical domain controller

Start the virtual domain controller in Directory Services Restore Mode (DSRM). This prevents the directory service from starting and cleans the system.

Remove unwanted software, such as hardware monitors (such as HP Insight agents) and unnecessary device drivers. See this message for more information.

Remove passive devices in Device Manager. See this message for more information.

Set the actual IP address (S) in the virtual domain controller

In step 1, enable all other deleted transaction services

Start the virtual domain controller in normal mode.

The virtual domain driver must now be enabled.

Note: From now on, you will no longer be able to bring the physical domain controller back online! This causes the USN to be cancelled and Active Directory replication is not working properly. See the Microsoft Database article KB875495 for more information.

Perform the following checks to verify the domain driver:

Check event logs
Check for errors
Run dcdiag from the Windows Support Tools
Run Netdag from Windows Support Tools
Create a test user for another domain controller and verify that it is copied to the virtual domain controller
Remove the test user from the virtual domain controller and verify that the deletion has been copied to another domain controller
If you resize the disk where the root path of the Active Directory copy is located (for example,% SystemRoot% \ Sysvol) during the P2V process, the following error occurs:

The file replication service has detected that the replication root path has changed from "d: \ sysvol \ domain" to "d: ys sysvol \ domain". In the case of an intentional transfer, you must create a file with a new path named NTFRS_CMD_FILE_MOVE_ROOT.

Creating an empty file named NTFRS_CMD_FILE_MOVE_ROOT To resolve this issue, re-create the sysvol folder.

1 Просмотры