Link to home
Start Free TrialLog in
Avatar of mthsupport
mthsupportFlag for United States of America

asked on

Internal Domain Rename

I have a two site single SBS domain network I want to break into two separate networks. Here is a brief description of the current setup.

Site A (Primary Site)
SBS2003 (FSMO holder, GC)

Site B
Win2k3 Srv
AD, DNS, DHCP, GC

Connected by site-to-site VPN

My goal is to get both sites operating independently and remove the VPN. I'm already aware of all the licensing I need to achieve this. I'm looking for some advice on the separation. Here is my initial plan.

Site A
perform swing migration from SBS 2003 to Win 2012 R2.

Site B
This is where I'm unsure on how to proceed. Can I run a swing to 2012 R2 then use the domain rename tool to rename my internal domain at site B to something more appropriate to the organization and different than site A? Or does that even matter? I do have several users that work primarily at Site A but occasionally travel to Site B to work. What ramifications, if any, exist by just renaming the domain for these users?

Of course I can always start from scratch and build a new internal domain and migrate existing users to it but that is much more labor intensive and disruptive.

I look forward to the feedback. Thanks in advance.
Avatar of Will Szymkowski
Will Szymkowski
Flag of Canada image

If you have Exchange or SQL in your environment I would not do internal domain name change as it could break several applications. Your best bet would be to create a new Forest in Site B and use the Active Directory Migration Tool to migrate the objects from Site B to the new Forest. From there you will have complete separation.

ADMT - http://www.microsoft.com/en-ca/download/details.aspx?id=8377

ADMT Guide - http://www.google.ca/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=1&cad=rja&ved=0CCsQFjAA&url=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2Fa%2F9%2F4%2Fa94c5f56-f7b5-4ec8-bcaa-1eadf84c4e3f%2FV3MigGuide.doc&ei=RMmMUpqEGMeSyAGT_4GIBA&usg=AFQjCNF5JJLhOP_rb1rAe7KfUtVQsk4rLA&sig2=r9Hv5v6Qxw2IvpH37XAlxQ

I would not recommend doing the domain name change in a produciton environment. This is for test purposes only.

Will.
I think you would encounter problems if you split the two sites (whether you renamed one of them or not) when you have domain users and/or machines traveling and connecting between the sites.  Domain SIDs are not going to be changed by a rename.

You're going to have to set up a new domain in a new forest.  Migrating objects would help to reduce disruptions.
Avatar of mthsupport

ASKER

Okay. Thanks for the feedback. A new domain it is.

I've never used ADMT before so I'm not sure if it is even worth it with a network of approximately 30 users. What advantages would using the ADMT provide me? It won't migrate passwords but will it migrate computer SID and user SID so at the workstations I won't have to create new profiles?
ASKER CERTIFIED SOLUTION
Avatar of Will Szymkowski
Will Szymkowski
Flag of Canada 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
Okay thanks Spec01.
Hi all,

short update 2 years later:

current status 2015
We also tought about renaming our domain or go ahead with a forest migration.
After discusison with Microsoft (ps calls) we identified exchange and sharepoint
as a no-go for any renaming procedures - only forest migration is an option (or just let it how it is ... ).

regards,
A.