VMware Cloud Community
Murali99
Contributor
Contributor

Domain controller P2V conversion

Hi All

Please let me know the prerequisites for Domain controller P2V conversion.

What are the steps need to be taken before and after P2V conversion of domain controller (OS: Windows 2003 server R2 Enterprise edition).

..Murali

Reply
0 Kudos
5 Replies
RvdNieuwendijk
Leadership
Leadership

Hi Murali,

read Best practices for using and troubleshooting VMware Converter and Virtualizing existing domain controllers for more information about virtualizing domain controllers. If the domain controller that has to be virtualized has only the domain controller role, it might be better to do a fresh installation of a new domain controller.

Regards, Robert

Blog: https://rvdnieuwendijk.com/ | Twitter: @rvdnieuwendijk | Author of: https://www.packtpub.com/virtualization-and-cloud/learning-powercli-second-edition
AntonVZhbankov
Immortal
Immortal

P2Ving domain controller is a bad idea. Create new VM with Windows, raise it to additional DC, transfer all roles and remove old DC from AD.


---

MCSA, MCTS Hyper-V, VCP 3/4, VMware vExpert

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda
PhilippeMasse
Enthusiast
Enthusiast

I did P2Ving a 2003 Domain Controller 1 year ago for a client that needed his PDC in a Test env. and I did have a couple of issues but for a Test env. only it can be done.

After the P2V, you will have to run DCDIAG.exe and NETDIAG.exe to make sure everything is up and running. Also, do this trick to make all de previous hardware devices viewable in the Device Management console. Then delete all remaining drivers that are not usefull to VMware (make sure you know what to delete).

http://support.microsoft.com/kb/241257

But there is one MS function that will be broken and it's the SYSVOL and FRS synchronisation within AD.

To resolve this issue, follow this link :http://support.microsoft.com/kb/290762

Other than that, your DC should be working fine. But as always the better way to do it is to create a new DC but sometimes it's not possible.

Bye

Reply
0 Kudos
Rubeck
Virtuoso
Virtuoso

Never had an issue with P2V'ing DC's... Cold cloning (requires a valid license ofc) and prober time sync have worked for me at all times...

  • Checked that the targeted ESX host has valid date /time configured

  • Cold clone and power off source

  • Keep the clone disconnected from network until HW releated apps have been uninstallled, VMwareTools installed and prober IP config. done.

If not sync'ing time using VMware Tools which targets the ESX host time underneath, the sync might occur anyway in various management operations. To bypass this add this to .vmx file which belongs to the converted DC:

tools.syncTime = "0"

time.synchronize.continue = "0"

time.synchronize.restore = "0"

time.synchronize.resume.disk = "0"

time.synchronize.shrink = "0"

time.synchronize.tools.startup = "0"

My 2 cents..

/Rubeck

Reply
0 Kudos
DSTAVERT
Immortal
Immortal

As an add on to what Anton said ,you also end up with a clean VM. Especially after a long run computers seem to accumulate junk and old hardware drivers etc. Since it is such an easy process there is no real reason to not create from scratch and migrate the roles etc.

-- David -- VMware Communities Moderator
Reply
0 Kudos