BenyG
asked on
Mailbox migrate from Exchange 2003 to Exchange 2007 requires local profile update
Previously when doing migrations from 2003 to 2003, or 2000 to 2003 it was possible to migrate a users mailbox without editing a users profile. I have found that the issue is due to the additional administrative group that the Ex2007 server are located in.
I have found the Exchange Profile Update Tool (exprofre) can address this, however I have found that when Exchange is in native-mode the legacyExchangeDN is not changed when the migrate crosses a AG boundary: http://support.microsoft.com/kb/873214
When testing I have had erratic results when migrating mailboxes - sometimes the Outlook profile needs to be updated and sometimes I get 'disconnected' after the mailbox-move it can resolve itself after the Outlook client has been open for ~15 mins.
Does anyone have any recommendations or experiences from encountering these issues? Should a 2003 to 2007 native-mode migrate be as seamless as a 2003-to-2003 migrate?
I have found the Exchange Profile Update Tool (exprofre) can address this, however I have found that when Exchange is in native-mode the legacyExchangeDN is not changed when the migrate crosses a AG boundary: http://support.microsoft.com/kb/873214
When testing I have had erratic results when migrating mailboxes - sometimes the Outlook profile needs to be updated and sometimes I get 'disconnected' after the mailbox-move it can resolve itself after the Outlook client has been open for ~15 mins.
Does anyone have any recommendations or experiences from encountering these issues? Should a 2003 to 2007 native-mode migrate be as seamless as a 2003-to-2003 migrate?
ASKER
jawad1481: It should be but during my testing I found problems. Sometimes the Outlook profile needs to be updated and sometimes I get 'disconnected' after the mailbox-move it can resolve itself after the Outlook client has been open for ~15 mins.
Hi!
Could you check the application log and System log on the Exchange server and DC.
I am sure that there is some AD replication problem at your end.
Thanks,
Jawad
Could you check the application log and System log on the Exchange server and DC.
I am sure that there is some AD replication problem at your end.
Thanks,
Jawad
HI!
Do you still facing the issue ?
Let me know if you need any help.
Thanks.
Jawad.
Do you still facing the issue ?
Let me know if you need any help.
Thanks.
Jawad.
ASKER
I have check the logs and cannot see any evidence of replication problems.
I have found more details regarding the symptom: The issue can be rectified by just rentering the user's name and clicking 'check names' within Outlook. This must mean that Outlook is not updating itself with the new details for some reason, or it is incorrectly using cached details Although this issue does not occur with 2003 to 2003 mailbox migrations.
I have also checed that the legacyexchangeDN does not change as it should with native-mode cross-AG moves. - Mixed-mode cross-AG moves result in the legacyexchangeDN being changed to reflect the new AG and the issue I am having would be by design.
I have found more details regarding the symptom: The issue can be rectified by just rentering the user's name and clicking 'check names' within Outlook. This must mean that Outlook is not updating itself with the new details for some reason, or it is incorrectly using cached details Although this issue does not occur with 2003 to 2003 mailbox migrations.
I have also checed that the legacyexchangeDN does not change as it should with native-mode cross-AG moves. - Mixed-mode cross-AG moves result in the legacyexchangeDN being changed to reflect the new AG and the issue I am having would be by design.
ASKER
increased to 500
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
i agree with you, that when we move mailbox within the same AG we dont have to reconfigure profile.
i think in your case the move mailbox from e2k3 to e2k7 should be similat to maove mailbox from e2k3 to e2k3.