Unified Messaging Guide for Cisco Unity Connection Release 9.x
Moving Microsoft Exchange Mailboxes for Cisco Unity Connection 9.x Unified Messaging Users
Downloads: This chapterpdf (PDF - 92.0KB) The complete bookPDF (PDF - 928.0KB) | Feedback

Table of Contents

Moving Microsoft Exchange Mailboxes for Cisco Unity Connection 9.x Unified Messaging Users

Determine Updating When Unity Connection User Settings Manually After Moving Exchange Mailboxes

Moving Exchange Mailboxes to a New Exchange Server for Unity Connection

Replacing Unity Connection Unified Messaging Accounts After Moving Exchange Mailboxes

Determine Updating When Unity Connection User Settings Manually After Moving Exchange Mailboxes

Revised May 29, 2013

If you create one or more unified messaging services for Exchange, as described in the “Configuring Cisco Unity Connection 9.x with Microsoft Exchange for Unified Messaging” chapter, one of the settings identifies the Exchange servers that Unity Connection communicates with:

  • If you choose to allow Unity Connection to search for Exchange servers, Unity Connection can automatically detect when you move mailboxes from one version of Exchange to another and can automatically update Unity Connection user settings.
  • If you choose a specific Exchange server, Unity Connection can sometimes detect when you move mailboxes from one Exchange server to another, and can automatically update hidden Unity Connection user settings. When Unity Connection cannot detect mailbox moves, you must manually replace the unified messaging account that accesses the old Exchange server with a unified messaging account that accesses the new server. Table 4-1 identifies when Unity Connection can and cannot automatically detect mailbox moves between Exchange servers.

 

Table 4-1 When Unity Connection Can Detect Mailbox Moves Between Exchange servers

If you choose a specific
Unity Connection can automatically detect mailbox moves between the following Exchange versions
2003 and 2003
2003 and 2007
2003 and 2010
2007 and 2007
2007 and 2010
2010 and 2010
2007 and 2013
2010 and 2013
2013 and 2013

Exchange 2003 server

No

No

No

No

No

No

No

No

No

Exchange 2007 server

No

No

No

Yes

No

No

No

No

No

Exchange 2010 server

No

No

No

Yes

Yes

Yes

No

No

No

Exchange 2013 server

No

No

No

Yes

Yes

Yes

Yes

Yes

Yes

If Unity Connection cannot automatically detect mailbox moves, do the procedure in the “Replacing Unity Connection Unified Messaging Accounts After Moving Exchange Mailboxes” section.

Moving Exchange Mailboxes to a New Exchange Server for Unity Connection

If you add an Exchange server to the Exchange organization, you want to move Exchange mailboxes to the new server, and the Exchange mailboxes are associated with Unity Connection users who are configured for single inbox, you must grant the permissions that Unity Connection requires before you move the mailboxes. Otherwise, Unity Connection users will not be able to access their voice messages in the new location. This is true regardless of whether you allow Unity Connection to search for Exchange servers or you configure Unity Connection to communicate with a specific Exchange server.

For information on granting the necessary permissions, see the “Creating Unified Messaging Services Account in Active Directory and Granting Permissions” section. Note that creating a new unified messaging services account for the new Exchange server is not necessary; you can also grant an existing unified messaging services account the permissions required to access the new Exchange server.

Replacing Unity Connection Unified Messaging Accounts After Moving Exchange Mailboxes

When Unity Connection cannot detect Exchange mailbox moves and, therefore, cannot automatically update the location of the Exchange mailbox for a Unity Connection user, you must manually create a new unified messaging account that accesses the new mailbox location and delete the unified messaging account that accessed the old mailbox location.


Caution Between the time that you move Exchange mailboxes and the time that you update Unity Connection settings for the affected users, Unity Connection will not synchronize voice messages with the corresponding Exchange mailboxes.

To Replace Unity Connection Unified Messaging Accounts After You Move Exchange Mailboxes


Step 1 Review the “Determine Updating When Unity Connection User Settings Manually After Moving Exchange Mailboxes” section to determine whether Unity Connection can automatically detect mailbox moves for your Exchange configuration and Unity Connection settings:

    • If Unity Connection can detect mailbox moves, skip the rest of this procedure.
    • If Unity Connection cannot detect mailbox moves, continue with Step 2.

Step 2 If you moved the Exchange mailbox to an Exchange server for which there is currently no Unity Connection unified messaging service, create the service. For more information, see the “Configuring Unified Messaging in Unity Connection” section.

Step 3 Create a new unified messaging account for the user, and choose a unified messaging service that accesses the Exchange server to which the mailbox was moved. For more information, see the “Creating Unified Messaging Accounts to Link Unity Connection Users to Exchange Mailboxes” section.

Step 4 Delete the unified messaging account that accessed the Exchange server from which the mailbox was moved:

a. In Cisco Unity Connection Administration, expand Users , then select Users .

b. On the Search Users page, select the alias of a user.

c. On the Edit User Basics page, on the Edit menu, select Unified Messaging Accounts .

d. On the Unified Messaging Accounts page, check the check box to the left of the unified messaging account that you want to delete.

e. Select Delete Selected .

Step 5 Repeat Step 2 through Step 4 for the other Unity Connection users whose Exchange mailboxes you moved.