Hello,
I've taken over a mess of a migration project, the goal of which is two take two offices working in their own domains, create a third domain and migrate them all into that one. There are, however, two major problems with this plan:
* The two offices have the same netbios name for their domains
* The new domain was created as a child domain of one of the offices
So we have:
companyltd.london
companyltd.berlin
and the newly created, mostly migrated to, company.local.
Domain controllers for company.local exist in both sites and AD replication and mail is flowing happily between the sites. There is a trust between companyltd.london (parent) and company.local (child). (When I say parent and child, I mean that the _msdcs folder in the company.london DNS contains all the GUIDs of the domain controllers for company.local)
The problem is that since there is already a trust between companyltd.london and its child domain company.local I cannot create a second trust between companyltd.berlin and company.local, as the netbios names for london and berlin are the same (companyltd).
If companyltd.london and company.local were in fact separate forests I'd simply break the trust after resource migration and create a new one with companyltd.berlin. As far as I can tell I have two choices:
* Perform a manual migration of the berlin office
or
* re-promote the child domain, then break the trust between it (company.local) and companyltd.london
I would like the community's opinion on which of these two options is less painful and less risky. I see manual migration as being both painful and risky: each workstation must be done manually, I'm not sure if the user profiles will be preserved, we have to do every workstation in a single weekend (which is hard because of permanently remote users) and there is no easy rollback strategy.
Repromotion of a child domain is, on the other hand, a complete unkown for me. What do you guys think?
Start Free Trial
