Solved

Convert Physical Domain Controller to Virtual

Posted on 2014-07-22
6
430 Views
1 Endorsement
Last Modified: 2014-07-26
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
1
Comment
Question by:Lumious
  • 3
  • 2
6 Comments
 
LVL 56

Expert Comment

by:Cliff Galiher
ID: 40213125
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.
0
 

Author Comment

by:Lumious
ID: 40213194
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
0
 
LVL 56

Expert Comment

by:Cliff Galiher
ID: 40213202
Most of those devices don't use DNS. So it'd be a non-issue. And the ones that do....change them.
0
Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

 

Author Comment

by:Lumious
ID: 40213224
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
0
 
LVL 56

Assisted Solution

by:Cliff Galiher
Cliff Galiher earned 250 total points
ID: 40213243
Open DHCP, expand the scope, expand scope options, edit the DNS scope option. Very very straightforward.
0
 
LVL 16

Accepted Solution

by:
vivigatt earned 250 total points
ID: 40213873
Specifically, you have to change the DHCP "DNS Server" option (option 6) for it to have one of your working DC as the 1st IP address (preferred DNS server). The clients will have to release their lease and request a new lease or to be rebooted for this setting to be taken into account (or you can use some kind of scripts, for instance based on "ipconfig /release ; ipconfig /renew" commands).
0

Featured Post

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Veeam Backup & Replication has added a new integration – Veeam Backup for Microsoft Office 365.  In this blog, we will discuss how you can benefit from Office 365 email backup with the Veeam’s new product and try to shed some light on the needs and …
In this article, I will show you HOW TO: Perform a Physical to Virtual (P2V) Conversion the easy way from a computer backup (image).
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

910 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now