locked
Cross-Forest Migration Questions RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I was hoping someone could help me shed a little bit of light on some cross-forest linked mailbox details. Specifically:

    1. If the target Forest already has contact objects in it created manually representing the pre-migration source mailboxes, does the new-move request handle that or will the existing contact objects need to be removed? If they need to be removed as mailboxes are migrated, would a PS script or something suffice to automate the task?

    2. I assume the suspendwhenready switch works cross-forest. Are there any particular gotchas or does it work as expected?

    3. If the source company goes by %S,%G but the new company goes by %G,%S is there an easy way to transition the naming during the migration and update the GAL as well?

    4. Conference Rooms. What is the best way to deal with conference rooms over an extended migration?

    Thank you in advance!

    :)


    Thursday, June 27, 2013 2:32 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    1. It’s recommended to firstly backup and remove the contacts before the migration.

    Simon Wu
    TechNet Community Support

    @Simon_Wu
    Is that your personal opinion or is it specified in any documentation from Microsoft (never seen that)?

    The reason I ask is that Prepare-Moverequest does a great job in converting MailContacts to MailUsers when run with the parameter UserLocalObject and keeps all exchange related exchange attributes, including LegacyExchangeDN


    @ABCFED

    1. No you don't need to remove the MailContacts
    2. SuspendWhenreadyToComplete works super and I am a big fan of that parameter :)
    3. Its all about Email Address Policies.
    4. If you create a receive connectors with the permission "Externally Secured" between the two ORGs, users can book rooms.

    Martina Miskovic


    Friday, June 28, 2013 8:19 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    1. It’s recommended to firstly backup and remove the contacts before the migration.

    2. “You can only use the SuspendWhenReadyToComplete switch for online mailbox moves and when moving mailboxes from Exchange Server 2007 or Exchange 2010 mailbox databases.”

    http://technet.microsoft.com/en-us/library/dd351123(v=exchg.150).aspx

    3. You can refer to: http://social.technet.microsoft.com/Forums/en-US/2592bc14-87aa-4bad-a3b2-edbaab547f3c/cross-forest-migration-mail-flow-between-exchange-2007-and-2010

    4. http://technet.microsoft.com/en-us/library/ee633491(v=exchg.150).aspx

    Thanks,

    If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com

    Simon Wu
    TechNet Community Support

    Friday, June 28, 2013 7:55 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    1. It’s recommended to firstly backup and remove the contacts before the migration.

    Simon Wu
    TechNet Community Support

    @Simon_Wu
    Is that your personal opinion or is it specified in any documentation from Microsoft (never seen that)?

    The reason I ask is that Prepare-Moverequest does a great job in converting MailContacts to MailUsers when run with the parameter UserLocalObject and keeps all exchange related exchange attributes, including LegacyExchangeDN


    @ABCFED

    1. No you don't need to remove the MailContacts
    2. SuspendWhenreadyToComplete works super and I am a big fan of that parameter :)
    3. Its all about Email Address Policies.
    4. If you create a receive connectors with the permission "Externally Secured" between the two ORGs, users can book rooms.

    Martina Miskovic


    Friday, June 28, 2013 8:19 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Martina,

    THANK YOU!!!!!!!

    :)

    1. I'll test running the prepare move request with the "userlocalobject" option.

    2. Perfect! I agree. It makes migration windows a snap to manage.

    3. I was referring more to the AD object properties itself, but I think I'll migrate the users then simply run another script to rename the AD properties correctly after they are moved into an OU.

    4. So, if the forest trusts are currently in place with two Exchange 2007sp2+ Orgs I can simply create 2 receive connectors allowing each Exchange server to "talk" and set the permissions tab to "externally secured". Okay. But how do you migrate the conference rooms from the one org to the other while maintaining the ability for appointment bookings and such with little/no interruptions during the transition process? 

    Again, thank you!


    • Edited by ABCFED Friday, June 28, 2013 11:33 AM Some Reason
    Friday, June 28, 2013 11:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Martina,

    It’s not from the documentation from Microsoft.

    As a support engineer, to avoiding any unexpected issues, we always recommend our customer to firstly backup their data in case of data loss.

    Thanks,

    If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com

    Simon Wu
    TechNet Community Support

    Monday, July 1, 2013 3:01 AM