Migrating Exch5.5 mailboxes to Exch2K3 - wizard failing  
Author Message
Rossetoecioccolato





PostPosted: Wed Dec 24 15:49:06 CST 2003 Top

Exchange Servers Admin >> Migrating Exch5.5 mailboxes to Exch2K3 - wizard failing

The Servers;

Old - Win2K (upgraded from NT4), AD, DC, Exchange 5.5
New - Win2K3, AD, DC, Exchange 2K3

We have successfully prepped the servers for Win2K3 AD environment
and replicated AD information to the new server (which is also a DC for
the domain). This all seems fine (with the exception of 1058 errors
relating to the Group Policy replication, but we don't think that's
relevant). Exchange 5.5 on the old server is set to LDAP port 390, and
the ADC Connection Agreement has (I think) been set up correctly on
the new server to replicate AD users to the new Exchange recipients
group.

The problem? Mailbox migration has us stumped - we cannot get
accounts to migrate to the new server. When we run the migration
wizard (from either Exchange System Manager or AD Users &
Computers) it hangs at "Connecting to the Source Server" and
must be forcibly quit. The event log says that the wizard could not find
the Exchange Server. Changing the Exchange 5.5 LDAP port back to
389 causes the wizard to complete almost immediately, but with an
error which states that the Directory Service type was not expected
(Windows Directory Services instead of Exchange). This seems to be
because Exch5.5 and Win2K AD both listen for LDAP requests on port
389.

In addition, no user mailboxes exist on the new Exch2K3 server yet -
should these have been created by the ADC replication process, or do
they show up only after migrating mailboxes?

Extensive newsgroup searches have revealed no absolute answers, even
though it seems many others have run into the problem. Questions:

1. Would it make sense to run dcpromo on the old server to demote it
from DC status, thus leaving only Exchange listening on LDAP port 389?
We want to take this server out of rotation anyhow, and we have two
other DC's in place already.

2. Is it possible to manually specify the Exch2K3 migration wizard LDAP
port, or somehow cause it to auto-detect port 390 (instead of 389) on
the Exch5.5 server?

3. What is the proper ADC Connection Agreement configuration?
Nowhere have we found exactly what it should be. What do the
"destination" fields in both the "From Windows" and "From Exchange"
tabs actually refer to?

4. Upgrade Exchange 5.5 to Exch2K3 using the in-place method
*before* migrating mailboxes. Possible? Difficult?

5. Would using Exmerge be the path of least resistance here? Anyone
have experience with this? Do mailboxes need to be created on the
Exch2K3 server before the .pst's are imported? If so, how?

Thanks for any answers you can give.

-Doug

Exchange Server39  
 
 
ibre34





PostPosted: Wed Dec 24 15:49:06 CST 2003 Top

Exchange Servers Admin >> Migrating Exch5.5 mailboxes to Exch2K3 - wizard failing Are the Windows 2000 and Windows 2003 server part of the same domain or
forest?
Are the Exchange 5.5 and Exchange 2003 server part of the same organization?



> The Servers;
>
> Old - Win2K (upgraded from NT4), AD, DC, Exchange 5.5
> New - Win2K3, AD, DC, Exchange 2K3
>
> We have successfully prepped the servers for Win2K3 AD environment
> and replicated AD information to the new server (which is also a DC for
> the domain). This all seems fine (with the exception of 1058 errors
> relating to the Group Policy replication, but we don't think that's
> relevant). Exchange 5.5 on the old server is set to LDAP port 390, and
> the ADC Connection Agreement has (I think) been set up correctly on
> the new server to replicate AD users to the new Exchange recipients
> group.
>
> The problem? Mailbox migration has us stumped - we cannot get
> accounts to migrate to the new server. When we run the migration
> wizard (from either Exchange System Manager or AD Users &
> Computers) it hangs at "Connecting to the Source Server" and
> must be forcibly quit. The event log says that the wizard could not find
> the Exchange Server. Changing the Exchange 5.5 LDAP port back to
> 389 causes the wizard to complete almost immediately, but with an
> error which states that the Directory Service type was not expected
> (Windows Directory Services instead of Exchange). This seems to be
> because Exch5.5 and Win2K AD both listen for LDAP requests on port
> 389.
>
> In addition, no user mailboxes exist on the new Exch2K3 server yet -
> should these have been created by the ADC replication process, or do
> they show up only after migrating mailboxes?
>
> Extensive newsgroup searches have revealed no absolute answers, even
> though it seems many others have run into the problem. Questions:
>
> 1. Would it make sense to run dcpromo on the old server to demote it
> from DC status, thus leaving only Exchange listening on LDAP port 389?
> We want to take this server out of rotation anyhow, and we have two
> other DC's in place already.
>
> 2. Is it possible to manually specify the Exch2K3 migration wizard LDAP
> port, or somehow cause it to auto-detect port 390 (instead of 389) on
> the Exch5.5 server?
>
> 3. What is the proper ADC Connection Agreement configuration?
> Nowhere have we found exactly what it should be. What do the
> "destination" fields in both the "From Windows" and "From Exchange"
> tabs actually refer to?
>
> 4. Upgrade Exchange 5.5 to Exch2K3 using the in-place method
> *before* migrating mailboxes. Possible? Difficult?
>
> 5. Would using Exmerge be the path of least resistance here? Anyone
> have experience with this? Do mailboxes need to be created on the
> Exch2K3 server before the .pst's are imported? If so, how?
>
> Thanks for any answers you can give.
>
> -Doug