Solved

moving a DC to a ESXi host via VMWare Stand Alone Converter

Posted on 2014-03-08
5
588 Views
Last Modified: 2014-03-17
I have 4 x DC's..  The previous admin got DC happy..  One of the DC's I plan to convert from a physical machine to a virtual machine.  I plan on making a system state backup prior to the conversion.  Currently it's carrying all of the FSMO roles.  Should I transfer the roles to a different DC prior to converting/moving it?  I figure the safest route would be to transfer the roles for I didn't want the version that I would mount causing odd AD replication issues for it would be slightly older copy of the replica than the others.  I figure transferring the roles would best.  Or..  Should I simply transfer the roles, demote it, and then assign it's IP to one of the other DC's since it currently answers DNS requests?  I do have a DC that's on an Exchange server but I'm not messing with it.. At least not for now.
0
Comment
Question by:gopher_49
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
5 Comments
 
LVL 11

Assisted Solution

by:gmbaxter
gmbaxter earned 250 total points
ID: 39915686
Rather than virtualise the fsmo role holder, I would build a new VM, add the domain controller role, let everything replicate and then transfer the fsmo roles to the new vm. After allowing for a little time to pass, check the logs and if clear, demote the old fsmo role holder to a member server.
0
 

Author Comment

by:gopher_49
ID: 39915866
Do you feel it's safer your route than converting over?
0
 
LVL 11

Expert Comment

by:gmbaxter
ID: 39915899
Yes. It is probably a little over cautious but has worked every time for me.
0
 

Author Comment

by:gopher_49
ID: 39916138
I don't feel we can be over cautious.   I'm all about being over cautious.  

Thanks!
0
 
LVL 28

Accepted Solution

by:
jhyiesla earned 250 total points
ID: 39917284
gmbaxter is correct that this is a better way to virtualize a DC.  I did something like this some time back and went the route he suggests and it worked well.  They only caveat is if you have the name or IP of the DC you'll eventually demote hard coded anywhere, those devices will obviously have an issue with locating the old DC once you demote it.

If that's the case you need to create the new VM server, demote the old one first, let ADSS figure that out, change name and IP of old DC, re-IP the new virtual machine to be the same as the old one and let DNS settle down, rename the VM to the same name as the old one and let DNS settle and finally promote the new VM to a DC and assign any necessary roles. This ultimately keeps the new DC with the same name and IP as the old. During this time, there will be some disruptions along the network, but they work themselves out in a short time frame.

Of course if you do NOT have any name or IP hardcoded then it's a very simple thing to just add a new DC and demote the old one.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

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

Will try to explain how to use the VMware feature TAGs in the VMs and create Veeam Backup Jobs using TAGs. Since this article is too long, I will create second article for the Veeam tasks.
In this article, I will show you HOW TO: Create your first Windows Virtual Machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, the Windows OS we will install is Windows Server 2016.
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…

617 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