jskfan
asked on
consolidating Child domain with parent domain
I have a parent domain and a child domain that are in 2 different site (Geographical zones).
I would like someone of the expert to provide me with link for documentation on how to merge the child domain with parent domain in order to form one domain as well as with some warnings, heads up, tricks and tips,etc...
FYI in child domain we have 700 users and in the parent domain 1300 users
both domains are Windows 2000 domains.
Thanks
I would like someone of the expert to provide me with link for documentation on how to merge the child domain with parent domain in order to form one domain as well as with some warnings, heads up, tricks and tips,etc...
FYI in child domain we have 700 users and in the parent domain 1300 users
both domains are Windows 2000 domains.
Thanks
ASKER
MyParentDomain (windows 2000 domain) located in California
all clients machines are XP
It has one Windows 2000 exchange server
Mychild.MyParentDomain (Windows 2000 domain)located in Florida
all Clients machines are XP
It has one Windows 2000 exchange server
the goal of merging both domains into one (MyParentDomain) is to centralize management.
I don't know which more info that you need me to provide you. but please let me know if you have any specific info you need.
thanks
all clients machines are XP
It has one Windows 2000 exchange server
Mychild.MyParentDomain (Windows 2000 domain)located in Florida
all Clients machines are XP
It has one Windows 2000 exchange server
the goal of merging both domains into one (MyParentDomain) is to centralize management.
I don't know which more info that you need me to provide you. but please let me know if you have any specific info you need.
thanks
ASKER
any documentation please regarding this topic?
thanks
thanks
Hi!
The recommeded way by MS is using intraforest migration and ADMT.
I'll try to send you more detailed step-by-step instructions.
Dean
The recommeded way by MS is using intraforest migration and ADMT.
I'll try to send you more detailed step-by-step instructions.
Dean
ASKER
I appreciate it.
ASKER
I guess this link is good
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook/cookch11.mspx
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook/cookch11.mspx
The link is good and it goves a very detailed guidelines.
The delicate part is the Exchange Migration. How do you plan to move the mailboxes?
Dean
The delicate part is the Exchange Migration. How do you plan to move the mailboxes?
Dean
ASKER
I don't know if there is a way to mirror the existing exchange servers.
Do you plan to upgrade the Exchange server at the central site to Exchange 2003?
Dean
Dean
Actually, I have to ask you first are the two Exchange 2000 servers in the same Administrative group or they are in separate Administrative groups?
Dean
Dean
ASKER
exchange 2000 servers are both in the same administrative group. it would be nice if we migrate and upgrade to 2003 at the same time.
ASKER
I also took a look at the microsoft migration cookbook, and noticed that the scenario they were talking about in chapter 11 is about merging 2 domains into one new domain, which is different from our case where we are planning to merge a child domain into an existing paremt domain.
ASKER
Let me know if Hyena Tool would be any help during the process of migration.
thanks
thanks
I am fine with closing the question and refunding the points to jskfan.
Here are some general instructions for intraforest domain consolidation in case jskfan (or somebody else who stumbles on that question) needs them.
1. You have to use ADMT version 3. It gives you more options and you are able to successfully transfer computer accounts, user accounts and passwords, with Windows and Microsoft Outlook profiles. You can download it from here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=6F86937B-533A-466D-A8E8-AFF85AD3D212&displaylang=en
2. The process of transferring the accounts can be time consuming – for example transferring about 40 user accounts (the DCs were 3 GHz/4 GB servers, T1 connectivity between the sites) took me about 15 minutes. Perform the appropriate calculations for 700 users.
3. When you choose to transfer the user passwords each account is marked for “Change password at next login”. You have to manually uncheck this option. If you have a Windows 2003 DC you can select all the accounts and remove this option very quickly. On a Windows 2000 DC you will have to perform this individually on each account or use a script.
4. I would suggest as a best approach to start with upgrading the Root domain to Windows 2003 (first take care of Exchange 2000 mangled attributes). Add a DC/GC belonging to the root domain in the remote site.
5. Then upgrade the Exchange server in the root site to Exchange 2003. Add a new Exchange 2003 server, belonging to the root domain, in the remote site.
6. Move the mailboxes residing on the Child Domain’s Exchange 200 server (using ADUC – Active Directory Users and Computers) to the new Exchange 2003 server.
7. Wait until everybody in the child domain logs in to their Outlook and gets redirected to the new Exchange 2003 server. Then use ADMT v.3 and move the computer and user accounts.
8.
I hope these instructions were helpful
Dean
Here are some general instructions for intraforest domain consolidation in case jskfan (or somebody else who stumbles on that question) needs them.
1. You have to use ADMT version 3. It gives you more options and you are able to successfully transfer computer accounts, user accounts and passwords, with Windows and Microsoft Outlook profiles. You can download it from here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=6F86937B-533A-466D-A8E8-AFF85AD3D212&displaylang=en
2. The process of transferring the accounts can be time consuming – for example transferring about 40 user accounts (the DCs were 3 GHz/4 GB servers, T1 connectivity between the sites) took me about 15 minutes. Perform the appropriate calculations for 700 users.
3. When you choose to transfer the user passwords each account is marked for “Change password at next login”. You have to manually uncheck this option. If you have a Windows 2003 DC you can select all the accounts and remove this option very quickly. On a Windows 2000 DC you will have to perform this individually on each account or use a script.
4. I would suggest as a best approach to start with upgrading the Root domain to Windows 2003 (first take care of Exchange 2000 mangled attributes). Add a DC/GC belonging to the root domain in the remote site.
5. Then upgrade the Exchange server in the root site to Exchange 2003. Add a new Exchange 2003 server, belonging to the root domain, in the remote site.
6. Move the mailboxes residing on the Child Domain’s Exchange 200 server (using ADUC – Active Directory Users and Computers) to the new Exchange 2003 server.
7. Wait until everybody in the child domain logs in to their Outlook and gets redirected to the new Exchange 2003 server. Then use ADMT v.3 and move the computer and user accounts.
8.
I hope these instructions were helpful
Dean
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Can you provide more info about the network configuration (a diagram would be great)?
Do you have Exchange servers in your domains, how many and what version?
What is the final goal - to have one domain and centralized management?
Dean