Exchange 2003 to 2007: Mailbox and User

Posted on 2010-11-29
Last Modified: 2012-05-10

1) There are Exchange 2003 in 2 domains; Boba and DingDong Domain
2) I want to migrate to Exchange 2007
3) There are suggestion (from the Experts from EE) that i have to move the Mailbox and also  move the user
4) I am confused (related to this); per my understanding the Users are at Active Directory and Nothing to do with the Microsoft Exchange
5) Per my experience of moving exchange 2003 to exchange 2007 (only one domain); i do NOT need to move the User
6) Would experts explain why i have to move the users (if it is more than one domain)?
7) Thank you
Question by:tjie
  • 2
  • 2
LVL 11

Assisted Solution

by:Renato Montenegro Rustice
Renato Montenegro Rustice earned 375 total points
ID: 34235589
I would like to recommend the following document. There's no big deal in moving mailboxes in this scenario.

Let us know if this is the case.

Moving Mailboxes (Scenarios for Moving Mailboxes)
LVL 11

Accepted Solution

Renato Montenegro Rustice earned 375 total points
ID: 34235628
Additional information from (Planning for Coexistence):

Mailbox Server Coexistence

The Mailbox server role can coexist with Exchange Server 2003 and Microsoft Exchange 2000 Server mailbox servers. For Exchange 2007 and Exchange 2000 Server or Exchange Server 2003 mailbox servers to coexist, you must be able to send mail among the mailboxes. Exchange 2007 uses the Hub Transport server to send mail. A Hub Transport server must be deployed in each Active Directory site that contains an Exchange 2007 Mailbox server.

You can move mailboxes among Exchange 2000 Server, Exchange Server 2003, and Exchange 2007. For information about how to move mailboxes, see Moving Mailboxes.

If you move a mailbox from Exchange 2000 Server or Exchange Server 2003 to Exchange 2007, and the mailbox is part of an e-mail address policy, the e-mail addresses for that mailbox is automatically updated based on the configuration of the e-mail address policy. If the mailbox had a primary SMTP address that differs from the e-mail address that is enforced by the e-mail address policy, that SMTP address becomes a secondary SMTP address and the e-mail address generated by the e-mail address policy becomes the primary SMTP address.

This behavior differs from Exchange 2003 and Exchange 2000. In Exchange 2003 and Exchange 2000 , the e-mail address policy is not applied to a mailbox when it is moved. To prevent accidentally changing the primary SMTP address of a mailbox in an Exchange 2007 environment, you must configure the mailbox so that is does not automatically update e-mail addresses based on e-mail address policy.

To configure Exchange 2003 or Exchange 2000 mailboxes, in Active Directory Users and Computers, right-click the recipient, and select Properties. On the E-mail Addresses tab, clear the Automatically update e-mail addresses based on e-mail address policy check box.

You can replicate public folder data between Exchange 2007 and Exchange 2000 Server or Exchange Server 2003 public folder databases. To do this, you must create a replica of the public folder using either the Exchange 2000 Server or Exchange Server 2003 versions of Exchange System Manager. The routing group connector between Exchange 2007 and Exchange 2003 can be configured to enable public folder referrals.

Author Comment

ID: 34235693
1) Please read it above
2) I repeat; my question is " Why do i have to move the Users (if migrating from Exchange 2003 to Exchange 2007; where there are more than 1 Domain)?
3) Thank you

Assisted Solution

Shack-Daddy earned 125 total points
ID: 34235875
You aren't getting a good answer because you haven't created a very clear question.

Exchange is extremely reliant on Active Directory. You can't have mailboxes without users. If you have set up a new domain and installed Exchange into it, you don't have to have the users in it, but you'd have to have a trust relationship between the new AD domain and the old user AD domains. If there is a trust relationship, you can assign users in your existing domains to resources in your "resource domain" that is hosting Exchange.

So when you refer to a "domain" are you talking about DNS domains or AD domains? If they are DNS domains, then your answer will be different.

In general, you will want to keep things as simple as possible for the future even if that means doing a little more work in the short term, which means you will have a flat (single) domain structure as your goal if possible.

Author Closing Comment

ID: 34249489
The answers help partially

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

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

This article explains how to install and use the NTBackup utility that comes with Windows Server.
In-place Upgrading Dirsync to Azure AD Connect
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…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

830 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