Recently we have done more research and found that as we deployed more domain controllers, this solution became less secure. Additionally, it was not as flexible in a non-centralized IT structure. In light of these circumstances, we have decided to break our enterprise geographically using several regional domains.
My questions are:
- With Exchange 5.5/2000 already in place and running, what is the best approach?
- Can Microsoft's Active Directory Migration Tool handle the tasks of both domain and Exchange migrations? If so, where do we find procedures, white papers, etc.?
- It depends on where the Exchange 5.5/2000 is located in the domain structure. My first inclination would be to put the Exchange installation in the domain where the IT group that organizes it will be. I am assuming here that you will still have a hierarchy of domains with one domain serving as the forest root as opposed to using complete trusts. You may have to migrate the user account and Exchange mailboxes to accomplish this.
- ADMT will move users, service accounts, etc. But it will not move the Exchange mailboxes. You will need to prepare the new domain for Exchange and then move the accounts. The Knowledge Base article XADM: Using the Exchange Migration Wizard to Migrate Mailboxes From an Exchange Organization (328871) should help get you started moving Exchange 2000 mailboxes to the new server.
Dig Deeper on Windows systems and network management
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.