New Domain & Exchange 2003 Server - Migration from NT4.0 Domain

Posted on 2006-06-08
Medium Priority
Last Modified: 2010-05-18
I am in the process of migrating from an NT4.0 Domain with Exch 5.5 to an AD 2003 Domain with Exch 2003.

I have created the 2 way trust and am working on getting DNS functioning both ways.
I want to maintain access to resources on both sides of the trust during the migration process.

Here is my question : (forgive my limited knowledge please)

When I first fire up my Exchange 2003 Server, does it matter what I set the "Exchange Namespace" to ?

Can I have a different Exchange environment on the AD Domain side and still make an ADC connection back across to the Exch 5.5 environment for the migration ?

Will this initial choice have a major impact when it comes to migrating the users and mailboxes from the NT4.0 side ?

Ideally I would like to have Exchange 2003 fully functional right away and be able to do some testing on the AD domain before extablishing the connection back across the trust to the NT4.0 Domain.

Can someone please give me some specific info here on what I can and can't do here ?
Question by:semncw

Accepted Solution

san_swa earned 900 total points
ID: 16863310
If you are doing Migration, then the Exchange name space should be same as Exchange 5.5.
If you want to use a seperate name space then it would be interorg migration. In this case you would not have to join the Exchange 5.5 Server, you just transfer the users from NT to AD then use Migration Wizard to move the mailboxes.
Best deal is to perform follow the ExDeploy Tools in Exchange 2003, which would tell you what needs to be done.
You can download Deployment Guide from http://www.microsoft.com/downloads/details.aspx?FamilyID=77B6D819-C7B3-42D1-8FBB-FE6339FFA1ED&displaylang=en
Also, you would have to move the users from NT Domain to AD Domain before moving the mailboxes or it would result into Disaster.

Can I have a different Exchange environment on the AD Domain side and still make an ADC connection back across to the Exch 5.5 environment for the migration ?====> You would not be able to join the Exchange 5.5 ( In ADC you would have to choose Interorg Connection option)...

Migration is always recommended to be peformed on Test Enviornment first and then on Production.

Author Comment

ID: 16871654
I did some more reading on this and have concluded that my best bet is to joing the existing Exch 5.5 organization.

Thanks for the info !

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

There can be many situations demanding the conversion of Outlook OST files to PST format and as such, there is no shortage of automated tools to perform this conversion. However, what makes Stellar OST to PST converter stand above the rest? Let us e…
In this post, we will learn to set up the Group Naming policy and will see how it is going to impact the Display Name and the Email addresses of the Group.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Suggested Courses

571 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question