Convert Physical Domain Controller to Virtual
Hi,
In our current environment there are 2 physical Domain Controllers at 2 different remote locations acting as the main domain controllers. What we are trying to do is convert the physical domain controllers to virtual domain controllers. I've already done a lot of research of what everyone is suggesting and basically to just spin up new virtual machines and make them domain controllers instead of doing a P2V, which is perfectly fine with me.
Location A:
- DC1
- All FSMO Roles
- DHCP for that location
- DNS
Location B:
- DC2
- DHCP for that location
- DNS
For right now I'm working on Location B. I've spun up a virtual machine, made it a domain controller, added it to the domain, and all replication for Active Directory and DNS has been successful because its currently pointing towards the original 2 domain controllers for replication for DNS.
Since DC2 in Location B is a DHCP server for this location, I already Exported the DHCP by running the following command in CMD:
netsh dhcp server export C:\dhcp.txt all
Now from what I've been told for the next steps would be to perform the following:
- Stop the DHCP Service on DC2
- Run the following command on the new domain controller to import the DHCP Export file from DC2
netsh dhcp server import c:\dhcp.txt all
- Make sure the services for DHCP are running on the new domain controller
- Open DHCP and verify that it's Authorized.
Also:
Everything in Location B has their DNS initially set to look towards DC2 (Ex: 192.168.1.2) currently. If we are spinning up a new virtual domain controller, with the steps above almost carried out, can we just change the new virtual domain controller to have the same IP as the original DC2 domain controller? Because if we had a new domain controller for this Location B, everything is already set to point to DC2 and not the new domain controller.
Suggestions please...
Thanks
In our current environment there are 2 physical Domain Controllers at 2 different remote locations acting as the main domain controllers. What we are trying to do is convert the physical domain controllers to virtual domain controllers. I've already done a lot of research of what everyone is suggesting and basically to just spin up new virtual machines and make them domain controllers instead of doing a P2V, which is perfectly fine with me.
Location A:
- DC1
- All FSMO Roles
- DHCP for that location
- DNS
Location B:
- DC2
- DHCP for that location
- DNS
For right now I'm working on Location B. I've spun up a virtual machine, made it a domain controller, added it to the domain, and all replication for Active Directory and DNS has been successful because its currently pointing towards the original 2 domain controllers for replication for DNS.
Since DC2 in Location B is a DHCP server for this location, I already Exported the DHCP by running the following command in CMD:
netsh dhcp server export C:\dhcp.txt all
Now from what I've been told for the next steps would be to perform the following:
- Stop the DHCP Service on DC2
- Run the following command on the new domain controller to import the DHCP Export file from DC2
netsh dhcp server import c:\dhcp.txt all
- Make sure the services for DHCP are running on the new domain controller
- Open DHCP and verify that it's Authorized.
Also:
Everything in Location B has their DNS initially set to look towards DC2 (Ex: 192.168.1.2) currently. If we are spinning up a new virtual domain controller, with the steps above almost carried out, can we just change the new virtual domain controller to have the same IP as the original DC2 domain controller? Because if we had a new domain controller for this Location B, everything is already set to point to DC2 and not the new domain controller.
Suggestions please...
Thanks
Cliff Galiher
You could, but I'm not a big fan of changing IP addresses of infrastructure servers. It is just as easy TO change the setting in DHCP and reboot client machines. As they check their leases, the new setting even if the lease hasn't expired yet. Less risk of ab issue arising.
ASKER
Hi,
As of right now, "nothing" is looking towards the new domain controller that I created. So are you suggesting "not" to change the IP of the new domain controller to the original IP of DC2?
If I change the settings in DHCP to the new domain controller I created, client machines will probably be fine, but what about other devices that have their DNS set to the original DC2 address (Ex: applications, routers, switches, printers, etc...)
Suggestions please...
Thanks
As of right now, "nothing" is looking towards the new domain controller that I created. So are you suggesting "not" to change the IP of the new domain controller to the original IP of DC2?
If I change the settings in DHCP to the new domain controller I created, client machines will probably be fine, but what about other devices that have their DNS set to the original DC2 address (Ex: applications, routers, switches, printers, etc...)
Suggestions please...
Thanks
Most of those devices don't use DNS. So it'd be a non-issue. And the ones that do....change them.
ASKER
Hi,
If we decide to change in the DHCP Settings to point to one of the new domain controllers, could you provide the steps to perform these changes when you get a chance?
Everyone:
Still Open to Suggestions...
Thanks
If we decide to change in the DHCP Settings to point to one of the new domain controllers, could you provide the steps to perform these changes when you get a chance?
Everyone:
Still Open to Suggestions...
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.