I have a domain spanning a few sites. Nothing fancy, just one domain. The sites are all connected via VPN and each site has a Windows 2003 R2 domain controller.
For an assortment of reasons, one of those remote sites is leaving my little domain "family." I will be disconnecting the VPN soon and turning them loose to be autonomous. I'm pondering on the best approach to keep that site up and running independently after the VPN is gone. (I should mention that I will have physical access to the newly disconnected site after the VPN is dropped.)
I see a few options.
1) Do nothing. Well, I'd change their domain admin password after the VPN drop but then just leave things alone. Will that now "orphaned" domain controller run into issues? It certainly won't have all the FSMO roles... but can that be fixed?
2) Demote the current DC. Re-premote it into a new domain. Remove their client machines from the old domain and re-add them to the new domain. There are some SQl Server boxes running as service accounts from the old domain that I'd have to fix up but otherwise...?
3) Open to other more logical ideas.
How would you approach this? Are either of my options viable? I think option 2 makes the most sense, but also the most effort. I'm limited a bit by how much time I'll have to get these configured so this option does make me a bit nervous.
Figure I'd turn to the experts before I roll up my sleeves. Can't help but suspect there's a better way.