Cisco Support Community
Community Member

Unity 5.01 Update


Unity 5.01 with voicemail (no Unified Messaging)

Partner Exchange server: Exchange 2003

Mail store: the same partner Exchange 2003 server

Email Server: Exchange 2010, no integration with Unity

Current Issue:

The Unity server stops taking calls. The issue has happened twice in the past two week. When calling AA number or VM pilot, the call just rings forever. Checking Unity and partner Exchange when the issue is happening, don't see any problem with memory, CPU or hard drive and no error messages in the Event Viewer. We had to reboot Unity and partner Exchange server to fix the issue for the time being.

We opened a TAC case for this and was instructed to patch the Unity server to the supported confuguration with Exchange 2010. The procedure provided is as follows. We are asked to perform all 20 steps. But I have concerns after double checking the procedure.

My questions:

1) Can we continue using Exchange 2003 as partner server and mailstore after Exchange 2010 is installed in the same domain?

2) If answer is yes to Q1, do I need to perform setp 13, 14, 16, 17, 19 and 20 in the procudure below? Since we don't use Exchange 2010 as partner server or mailstore, why do I need to do these steps related to Exchange 2010?

Thanks in advance.


Update Procedure:

Step 1

Download the applicable Cisco Unity engineering specials ES89.

a. Go to the Voice and Unified Communications Downloads page at b. In the tree control on the Downloads page, expand Unified Communications Applications > Voice Mail and Unified Messaging > Cisco Unity, and click Cisco Unity Version <version>.

c. Click Cisco Unity System Software, and follow the on-screen prompts to download the latest ES.

d. Click the Readme for <version>ESxx link and save a copy of the file. You need it later in the process.

e. If you are using more than one version of Cisco Unity, repeat Step a through Step d to download the engineering specials for the applicable versions.

Step 2 Download the latest version of the Cisco Unity Permissions wizard 5.01+ from

Step 3 Download the latest version of the Cisco Unity Server Updates wizard.

Step 4 Download the following software from the Microsoft website:

Update Rollup 3 or later for Exchange Server 2010.

ExchangeMapiCdo.exe, available on the "Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1" page.

Step 5 If Exchange 2003 System Management Tools is installed on the Cisco Unity server: Locate an Exchange Server 2003 disc. You will need the disc later in the process.

Step 6 Install Update Rollup 3 or later for Exchange Server 2010 on every Exchange 2010 server in the Exchange organization

Step 7 Copy the ES to a hard disk on the Cisco Unity server.

Step 8 Install the ES and additional patches. See the instructions in the readme file you saved in Step 1d.

Step 9 Restart the Cisco Unity server when prompted.

Step 10 Run the latest Server Updates wizard to install the patches that are described in the following Microsoft Knowledge Base articles:

KB957593, "Error message if you use the NON_CONTENT_INDEXED_SEARCH flag in an MAPI-based application: `Error :0x80040106 MAPI_E_UNKNOWN_FLAGS' "

KB948496, "An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computers"

(As with all patches installed by the Server Updates wizard, the patches are installed only when applicable.)

Step 11 Right-click the Cisco Unity icon in the Windows taskbar, and click Stop Cisco Unity.

Step 12 In the Services MMC, stop the CuMDBStoreMonitorStore service.

Step 13 On the Cisco Unity server, uninstall the applicable Exchange software:

Exchange Server 2003
System Management Tools

Uninstall by using the Windows Add/Remove Software Control Panel. Requires the Exchange 2003 installation disc.

Exchange Server 2007 MAPI

Uninstall by using the Windows Add/Remove Software Control Panel.

Step 14 On the Cisco Unity server, install ExchangeMapiCdo.exe, which you downloaded in Step 4.

Step 15 On the Cisco Unity server, install the version of the Permissions wizard that you downloaded in Step 2.

Step 16 Run the Permissions wizard, and select the Exchange 2010 message stores in which mailboxes for Cisco Unity subscribers will be homed.

Step 17 At the end of the Permissions wizard, on the You Have Completed the Cisco Unity Permissions Wizard page, click Granting Microsoft Exchange Administrator Rights, and do the procedure in the Help file to add the installation and directory services accounts to the Exchange 2010 Organization Management role group.

Step 18 Restart the Cisco Unity server.

Step 19 Move or create a mailbox for the Cisco Unity message store services account (typically UnityMsgStoreSvc), as applicable:

Exchange 2003 or Exchange 2007
mailbox already exists

Move the mailbox for the account to Exchange 2010.

No mailbox

Create a mailbox for the account in Exchange 2010.

Step 20 Remove the Exchange 2010 RPC limit for the message store services account by creating and applying a new mailbox policy to the message store services account:

a. Open an Exchange 2010 Management Shell window.

b. Create a new policy with unlimited RPC connections, for example:

new-throttlingpolicy -name "Unity Exchange 2010 Policy" -RCAMaxConcurrency $null

c. Apply the new policy to the message store services account, for example:

set-mailbox -identity "UnityMsgStoreSvc" -throttlingpolicy "Unity Exchange 2010 Policy"

d. Confirm that the mailbox is using the new policy, for example:

get-mailbox -identity "UnityMsgStoreSvc" | fl | findstr "Throttling Policy"

e. If you have more than one Cisco Unity server: Repeat Step c and Step d for every message store services account in the forest.

We recommend that you apply the policy to all message store service accounts, even the accounts for Cisco Unity servers for which you do not currently intend to home subscriber mailboxes in Exchange 2010 message stores. Applying the policy does not affect Cisco Unity performance, and it ensures that you will not encounter problems if you later move mailboxes to an Exchange 2010 server.

f. On each Exchange 2010 server with the CAS role, restart the Microsoft Exchange RPC Client Access service.

CreatePlease to create content