Exchange 2003-2007 moving mailboxes & permissions

Posted on 2009-04-19
Last Modified: 2012-05-06
Our environment has many shared mailboxes, resource mailboxes, mailboxes opened as secondary (admins for execs, etc.).    I noticed that, when moving a shared mailbox from Exchange 2003 - 2007, the user who opens that mailbox as a secondary mailbox cannot access it until I set the mailbox permissions through the Exchange 2007 admin console.   I would have thought that these permissions were purely in AD.  Could someone shed some insight on this please?  This greatly complicates our mailbox migration plan as now we need to document each and every user that has a secondary mailbox and assign permissions immediately post-move.  
Question by:44
    LVL 65

    Accepted Solution

    That shouldn't happen. The permissions should come across.
    However do note that if you have shared mailboxes in place, and the primary mailbox is moved, Outlook will NOT update the location of the shared mailbox as well as the primary mailbox.
    If you move the shared mailbox as well, then it will continue to work. Otherwise you have to remove the shared mailbox and then put it back in so that Outlook knows the shared mailbox is on another server.


    Author Comment

    Thanks Simon.   One strategy will be to move all mailboxes on each server over one weekend vs. 50 or so per night to limit this complication.  

    For whatever reason, the permissions are not coming across and I need to set permissions through Exchange 2007 "manage full access permissions" if the primary mailbox is the one moved but secondary remains 2003.  

    I've tested with just two mailboxes and moving simultaneously does preserve functionality.  Do you foresee any issues as long as we move all mailboxes over one weekend and these users do not access Outlook until Monday morning?
    LVL 65

    Expert Comment

    As long as both the old and the new server are available when the users come in, it shouldn't be a problem. I have moved 1000s of mailboxes, and have had at most a handful of issues. The few problems I have had were usually not caused by the mailbox move at all, but by a configuration error on the client and would have come out whether I moved 1 or 100 mailboxes.


    Author Comment

    Thanks for your suggestion.  We will try a mass migration over a weekend.  Moving all of them together I've encountered no issues with delegates, shared calendars, etc.   We will try to move 900 mailboxes over a weekend -- hopefully enough time with the high-end hardware and RAID 10 disk config we have.  

    Featured Post

    6 Surprising Benefits of Threat Intelligence

    All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

    Join & Write a Comment

    "Migrate" an SMTP relay receive connector to a new server using info from an old server.
    Outlook Free & Paid Tools
    Get people started with the process of using Access VBA to control Outlook using automation, Microsoft Access can control other applications. An example is the ability to programmatically talk to Microsoft Outlook. Using automation, an Access applic…
    In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…

    745 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

    Need Help in Real-Time?

    Connect with top rated Experts

    16 Experts available now in Live!

    Get 1:1 Help Now