My guess is that you're still going to have problems P2Ving the machine once it's a member server, but there's no reason not to try.
We used to use the VMware Converter twice weekly to P2V a DC as a disaster recovery measure. I was able to do a test recovery of it multiple times. (I'm not saying it was a great solution, just that it worked.) And we didn't have to shut it down for the P2V, nor go into ADRM. On Fri, Apr 11, 2014 at 7:58 AM, David McSpadden <[email protected]> wrote: > Ok, you guys almost have me convinced to not P2V my 2 DC's at this Data > Center. > > > > Now I have never actually demoted one. (All of my old DC's have just > hardware failed.) > > > > (I do have a 2012 DC up and have migrated all the FSMO roles to it and > made it my SNTP time provider.) > > > > So to do this correctly. I am going to use this checklist. > > -Make sure none of them are in my SNTP setup and Time providers. > > -Make sure no clients are using them for DNS resolution. > > -Demote them. > > -Make sure they are no longer Global Catalog providers for the Exchange > 2010 environment. > > -Make sure they are no longer LDAP connectors for my Cisco Anywhere client > connection on my ASA 5500. > > -Make sure I can still access the IIS apps that are loaded on one of them. > > -For the 2008 R2 DC at this point I can just un join it from the Domain > and then shut off. > > ---Then remove all DNS records or OU records that may remain after 1 day. > (Give replication a very good amount of time.) > > -For the 2003 DC (With IIS apps installed.) I should be able to P2V at > this time. > > > > > > This e-mail and any files transmitted with it are property of Indiana > Members Credit Union, are confidential, and are intended solely for the use > of the individual or entity to whom this e-mail is addressed. If you are > not one of the named recipient(s) or otherwise have reason to believe that > you have received this message in error, please notify the sender and > delete this message immediately from your computer. Any other use, > retention, dissemination, forwarding, printing, or copying of this email is > strictly prohibited. > > Please consider the environment before printing this email. >
