We have a domain (domain.corp) with two sites (NY, SF) and a child domain (London.domain.corp). The child domain seems to be causing problems. In the past it was having replication issues and Exchange queing problems. Another tech preformed some pretty radical DNS changes and now we are having extremely long logins in two of the sites in the primary domain. I think that the child domain's default domain policy is being applied to other sites in the primary domain over a slow VPN link. Also a GC in the child domain seems to be advertising for the primary domain. As the child domain only has 6 users and 2 servers (Exchange and DC), it seems unessecary to have it as a seperate domain. I'd like to tear it down and rebuild it as a new site in the primary domain. Anyone have any experience with this?
Here's my plan so far:
1. Convert london from a child domain to a site in domain.corp
a. Transfer London mailboxes to PSTs.
b. Remove London mail server from domain.
c. Demote child domain DC and remove child domain
1. If the child domain is still visible in primary domain follow this white paper to remove the orphaned objects: http://support.microsoft.com/default.aspx?scid=kb;EN-US;230306
d. Promote london DC server as a DC in domain.corp
e. Add LondonDC to the London site as a Global Catalog.
f. Add the London Exchange server to the domain.
g. Recreate users, mailboxes, shares
h. Import old mailboxes from PSTs
Any ideas to streamline improve this plan? Thanks for any help.