Cross Forest Migration using ADMT 3.1, Mailboxes moved but cannot reply to emails from Exchange 2010

  • Thread starter busbar
  • Start date Views 2,337
Status
Not open for further replies.
B

busbar

Hi,

I have a customer who is looking to move from 1 forest with E2003 to new forest with E2010, they are running SLD on the old forest this is why we are moving to a new forest.

I am setting up a lab to test the migration, I have setup 1 forest with SLD and Exchange 2003, configuration email to create domain.com email address policy.

created a new forest windows 2008 with Exchange 2010 RU2, setup accepted domain for domain.com and email address policy, used ADMT to move mailboxes and sync passwords, used the prepare move request script and steps listed here http://msexchangehelp.wordpress.com/2010/03/13/cross-forest-move-mailbox-request-from-exchange-2003-to-2010/, things went fine, now I logged on to OWA and found emails sent and received to users when they where on Exchange 2003, but when I try to reply to one of those emails I get an NDR, when I double click on a user that is in the to field in an email object in the OWA it gived me that it cannot access directory services object, in the NDR it tells me that it tries to send the email to /o-first organization/OU=first administrative group/CN=recipients/cn=user1

any advice, have anyone did a cross forest e2003 to e14 move.

Regards, Mahmoud Magdy http://busbar.blogspot.com http://ingazat.wordpress.com
 
A

Anıl ERDURAN - MVP

That's why of legacyexchangedn attribute.After a migration if you want to reply old mails, exchange will try to send this mail using legacyexchangedn of old user.And /o-first organization/OU=first administrative group/CN=recipients/cn=user1 is legacyexchangedn of user1.On the other hand if one of your users try to send using nk2 cache of outlook, he will get same error message.

To prevent this problem you have to add this old legacyexchangedn's to the users as x500 address.You can do this with powershell or admodify tool.But firstly you have to check legacyexchangedn'S.Todo this, on old exchange server ,run the follewing command;

csvde -f report.csv -r objectCategory=user -l " mail,legacyExchangeDN"
this will give you legacyexchangedn of all old users to report.csv.

After that add x500 custom address of this legacyexchangedn's to the target users.I suggest you to use admodify.With this tool, select all users and on the custom tab(http://i.technet.microsoft.com/Aa996216.02b34b8f-8d26-4956-9daa-d8e3a9f6872a(en-us,EXCHG.65).gif)

attributename: proxyaddresses

attribute value: x500:/o-first organization/OU=first administrative group/CN=recipients/cn=user1

After that you must reply old mails and send with using outlook cache.

If you want to use variable for cn=user1 you can use %'mailnickname'% - %'samaccountname'% or something like that %1'givenName'%.%'sn'%
 
B

busbar

Hi Anil,

Thanks for the tip, I will try that now, so shall I add the legacydn before or after the migration, the problem that I have various client types like OWA, POP3 and RPC/HTTP client so I want to make sure that the migration will flow nicely without any problems and minimize the user's impact to 0.

If I followed your step users will be able to reply from OWA and outlook correctly right? I was wondering are there a way to prevent Exchange to reply to the legacydn and use the STMP address instead, I wonder if that is possible.

Regards, Mahmoud Magdy http://busbar.blogspot.com http://ingazat.wordpress.com
 
A

Anıl ERDURAN - MVP

Whats your plan for address lists? I mean, when you migrate 20 users to the target exchange, how will they sent e-mail using their new address list of exchange 2010? You can do this with creating contacts.Firstly create for all old exchange users as contact on target exchange 2010(you can do this clearly with powershell script) after that when you move 20 users to the target forest delete this 20 contact object from target active directory.So this 20 users can see other users as contacts on address list and will able to sent mail.

If you do so, before migration, add loegacyexchangedn's to the this target contacts objects.So after migration there will be no problem about this situation.

And of course, if your legacy exchange organization has external contact objects, you have to create these too, and add legacyexchangedn's.Be careful that external contacts may have different forms of legacyexchangedn.(cn=aaa.bbb.ccc) so export all legacyexchangedn and add these to the target contact objects as x500 address.
 
B

busbar

Hi Anil,

I have tried your solution and it worked great, due to infrastructure and some issues the migration will not be phases, the mail system is planed to be taken down for the migration for 36 hours, we have about 1100 users that most of them are using POP3, so the mailbox DB is small I expect if I can go with 5 GB/hour to finish within 18 hours.

so I don't have to coexist the 2 system, the mail will move from one system to the other, I totally agree with you that I have to plan very well if I have to co-exist.

I have one question, although that I have a pretty solid experience with Exchange, I don't understand why E14 didn't place the legacyexchangedn attribute, my quess that it uses x500 which has been removed since E12.

one note to the above steps, if you move the mailboxes and apply the legacyDN to it, you will have to re-apply your email address policy to add the SMTP address again since they are removed and then you will be fine.

Thanks a lot Anil.

Regards, Mahmoud Magdy http://busbar.blogspot.com http://ingazat.wordpress.com
 
F

Fazal Muhammad Khan_

After the Migration has taken place and the Servers have been demoted. So do we need to Remove this legacy DN Attribute from Exchange Users ?

Regards
Fazal Muhammad Khan | MCT, MCSE, MCSA, MCTS | Infrastructure Consultant, Technology Services | CDC Pakistan Ltd. | https://fazalmkhan.spaces.live.com | OFFICE: +92 21 111 111 500 Ext: 1402 | +5 GMT
 
Status
Not open for further replies.
Top