Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

SBS 2003 Exchange Migration wizard will not connect to Exchange 5.5

Posted on 2004-09-11
1
Medium Priority
?
295 Views
Last Modified: 2008-02-01
Any one had a similar experience?

New server SBS2003

I have an old Windows 2000 server with exchange 5.5. I already used ADMT to import all user, group and computer accounts. Next step in the Whitepaper is opening the 'Exchange Migration Wizard' which would open the old source servers exchange, and pull out data. So I did, ran it, selected Microsoft Exchange, ticked 'Exchange 5.5' and gave the same working credentials as with ADMT of the old domain. 'Could not connect , verify Port, username and password'.


Checked LDAP on the source server, it is running on port 389 (standard no?)

Kan I use a tool to see the ldap directory. How should I troubleschoot it?


thanks
0
Comment
Question by:ezjurgen
1 Comment
 
LVL 12

Accepted Solution

by:
BNettles73 earned 500 total points
ID: 12037072


Check out this article - http://blogs.msdn.com/exchange/archive/2004/07/29/200795.aspx by Kahren Allakhverdyan.

a.      Start with checking the permissions of the account you use to run the Migration Wizard. Account running Migration Wizard must be a target domain account. Make sure this account is a member of the target domain admin group. Migration Wizard need these permissions for various R/W operations across the target forest while matching on user object and cleaning contacts(next time I will go through the Migration Wizard matching criteria).

b.      Make sure that the account you specify with "/a:" option has admin rights on the source mail system. If you perform migration from Exchange verify that this account also has Full Exchange Administrator rights delegated in the source Exchange org. To delegate the role use Exchange Administration Delegation Wizard from ESM.

c.      If your source is Exchange 55 server you will need Service Account Admin rights delegated to this account. Use Exchange 55 Admin to delegate this role.

d.      Next, check the command line string you entered. Make sure that your "/a:" option is correct.  If your source is the Exchange server, make sure that you entered this value in the "<domain>\< account>" format.

e.      You can skip the "<domain>" part if you entered it in control file with the "Postoffice" key: "<domain>\<exchange server>". With Exchange 2003 SP1 you no longer need to expose password, just use the "/p:*" option.

f.      Next check your control file. Make sure you entered the value for "ExchStoreDN" key correctly. This key as well as the "Container" key requires FQDN of the store where you want the mailbox to be created. I always use LDP to get these values for the control file. If the target Exchange org has plane structure with one storage group you can use "ExchStore" key assigning cn of mailbox store to it.

g.      Also, if this error appears while using command line, to help find the cause, you may switch to the Wizard in UI mode and go from screen to screen. If it works in UI mode check the key values in the control file and the command line string.

0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

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

With so many activities to perform, Exchange administrators are always busy in organizations. If everything, including Exchange Servers, Outlook clients, and Office 365 accounts work without any issues, they can sit and relax. But unfortunately, it…
Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Suggested Courses

926 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