Link to home
Start Free TrialLog in
Avatar of InSearchOf
InSearchOfFlag for United States of America

asked on

Physical to Virtual conversion

We recently stepped into the light and virtualized our environment. I was told that doing a p2v on a domain controller was not recommended. I was wondering if that is the case? I have a physical 2008 R2 server that is a DC, NPS and a Certificate server which is used for my wireless environment using Radius which EE helped me to set up and configure and works great.. I would like to virtualize this if possible. We had an outside company do the virtualization. For the DC they created a couple of VMs and made them Domain Controllers and transferred over the FSMO roles from the physical to the virtual. It has been a few months now and everything is running fine. We still have three physical servers because of their AD roles. What can I do about those?
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Make sure all links from your forest will be transferred to new DC before you''' demote them, especially if you do have Exchange server in your domain and was build when physical domain controllers was your primary DNS in domain.
I'd take this opportunity to create a new DC and separate out some of those roles during your migration.
Avatar of InSearchOf

ASKER

Thanks for the useful advice. Not to risk throwing a wrench into my AD environment and will go with the recommendations made here. Have to figure out what to with NPS and Radius configuration running on the physical 2008R2 box and run it on the 2016 virtual server. Anyway of exporting and importing that configuration?