...and the only thing to be careful about is IP addresses From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Webster Sent: Thursday, June 5, 2014 5:50 PM To: ntsysadm@lists.myitforum.com Subject: [NTSysADM] RE: P2V DC
Why? Is this server a DC only and runs nothing but DC type functions? If so, bring up a new VM and DCPromo it. Thanks Webster From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Neil Standley Sent: Thursday, June 05, 2014 4:40 PM To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com> Subject: [NTSysADM] P2V DC I've been reading up regarding P2V of Domain controllers (2003 R2 SP2 in this case) and I think I have it down but wanted to get some feedback from the collective before setting forth on my project. Following the recommendations from the articles below, my understanding is that I should: a. Perform an Offline conversion. Both DCs would be powered off at the completion of the conversion process. b. Disable time sync between the virtual DC and the virtual host. In this case I'm using VMware Essentials 5.5 U1 - Note this is already done. c. Never connect the original, physical DC to my network again to avoid USN rollback. http://blogs.technet.com/b/askds/archive/2010/06/10/how-to-virtualize-active-directory-domain-controllers-part-21.aspx http://blogs.technet.com/b/askds/archive/2010/06/10/how-to-virtualize-active-directory-domain-controllers-part-2.aspx http://www.sole.dk/virtualizing-your-domain-controllers-without-getting-fired/ Is it really this simple? I feel like there's a gotcha out there waiting to bite me real hard. Any suggestions or pointers to additional reading is much appreciated.
