Table Of Contents
Upgrading Exchange on the Cisco Unity System
Upgrading Exchange 2000 to Exchange 2003 for Cisco Unity 4.0(3) and Later Without Failover (Unified Messaging)
Downloading Software (Cisco Unity 4.0(3) and Later Without Failover)
Upgrading Exchange 2000 to Exchange 2003 (Cisco Unity 4.0(3) and Later Without Failover)
Reconfiguring Cisco Unity (Version 4.0(3) and Later Without Failover)
Upgrading Exchange 2000 to Exchange 2003 for Cisco Unity 4.0(3) and Later with Failover Configured (Unified Messaging)
Downloading Software (Cisco Unity 4.0(3) and Later with Failover Configured)
Upgrading Exchange 2000 to Exchange 2003 (Cisco Unity 4.0(3) and Later with Failover Configured)
Reconfiguring Cisco Unity (Version 4.0(3) and Later with Failover Configured)
Upgrading Exchange 5.5 with Active Directory to Exchange 2003 or Exchange 2000 for Cisco Unity 4.x Without Failover (Unified Messaging)
Preparing for the Upgrade (Cisco Unity 4.x Without Failover)
Upgrading Exchange 5.5 with Active Directory to Exchange 2003 or Exchange 2000 (Cisco Unity 4.x Without Failover)
Reconfiguring Cisco Unity (Version 4.x Without Failover)
Moving Mailboxes and Removing Exchange (Optional) (Cisco Unity 4.x Without Failover)
Upgrading Exchange 5.5 with Active Directory to Exchange 2003 or Exchange 2000 for Cisco Unity 4.x with Failover Configured (Unified Messaging)
Preparing for the Upgrade (Cisco Unity 4.x with Failover Configured)
Upgrading Exchange 5.5 to Exchange 2003 or Exchange 2000 (Cisco Unity 4.x with Failover Configured)
Reconfiguring Cisco Unity (Version 4.x with Failover Configured)
Moving Mailboxes and Removing Exchange (Optional) (Cisco Unity 4.x with Failover Configured)
Upgrading Exchange 5.5 with Active Directory to Exchange 2000 for Cisco Unity 3.1(5) Without Failover (Unified Messaging)
Preparing for the Upgrade (Cisco Unity 3.1(5) Without Failover)
Upgrading Exchange 5.5 with Active Directory to Exchange 2000 (Cisco Unity 3.1(5) Without Failover)
Reconfiguring Cisco Unity (Version 3.1(5) Without Failover)
Moving Mailboxes and Removing Exchange (Optional) (Cisco Unity 3.1(5) Without Failover)
Upgrading Exchange 5.5 with Active Directory to Exchange 2000 for Cisco Unity 3.1(5) with Failover Configured (Unified Messaging)
Preparing for the Upgrade (Cisco Unity 3.1(5) with Failover Configured)
Upgrading Exchange 5.5 with Active Directory to Exchange 2000 (Cisco Unity 3.1(5) with Failover Configured)
Reconfiguring Cisco Unity (Version 3.1(5) with Failover Configured)
Moving Mailboxes and Removing Exchange (Optional) (Cisco Unity 3.1(5) with Failover Configured)
Upgrading Exchange 5.5 to Exchange 2003 or Exchange 2000 for Cisco Unity Without Failover (Voice Messaging)
Upgrading Exchange 5.5 to Exchange 2003 or Exchange 2000 for Cisco Unity With Failover Configured (Voice Messaging)
Upgrading Exchange on the Cisco Unity System
This chapter contains the following sections:
•
Upgrading Exchange 2000 to Exchange 2003 for Cisco Unity 4.0(3) and Later Without Failover (Unified Messaging)
•Upgrading Exchange 2000 to Exchange 2003 for Cisco Unity 4.0(3) and Later with Failover Configured (Unified Messaging)
•Upgrading Exchange 5.5 with Active Directory to Exchange 2003 or Exchange 2000 for Cisco Unity 4.x Without Failover (Unified Messaging)
•Upgrading Exchange 5.5 with Active Directory to Exchange 2003 or Exchange 2000 for Cisco Unity 4.x with Failover Configured (Unified Messaging)
•Upgrading Exchange 5.5 with Active Directory to Exchange 2000 for Cisco Unity 3.1(5) Without Failover (Unified Messaging)
•Upgrading Exchange 5.5 with Active Directory to Exchange 2000 for Cisco Unity 3.1(5) with Failover Configured (Unified Messaging)
•Upgrading Exchange 5.5 to Exchange 2003 or Exchange 2000 for Cisco Unity Without Failover (Voice Messaging)
•Upgrading Exchange 5.5 to Exchange 2003 or Exchange 2000 for Cisco Unity With Failover Configured (Voice Messaging)
Note The procedures for Unified Messaging configurations can also be used for Voice Messaging configurations, but the Unified Messaging procedures require substantially more knowledge of Active Directory and Exchange.
Upgrading Exchange 2000 to Exchange 2003 for Cisco Unity 4.0(3) and Later Without Failover (Unified Messaging)
Note If Cisco Unity failover is configured, see the "Upgrading Exchange 2000 to Exchange 2003 for Cisco Unity 4.0(3) and Later with Failover Configured (Unified Messaging)" section to upgrade those servers.
The upgrade procedures in this section were tested in a configuration that included the following elements:
•A domain controller/global catalog server (DC/GC).
•A Cisco Unity 4.0(4) server (member server).
•An Exchange 2000 Server with Exchange 2000 Service Pack 3 (member server).
•A separate Exchange 2003 server that was added during the upgrade (member server).
Caution All testing was done with the old partner Exchange server, the new partner Exchange server, and the Cisco Unity server in the same Active Directory domain. Upgrading from one version of Exchange to another when the partner Exchange servers are in separate Active Directory domains has not been tested, and may fail.
The following subsections contain the instructions for upgrading a Cisco Unity 4.0(3) or later system without failover from Exchange 2000 to Exchange 2003:
•Downloading Software (Cisco Unity 4.0(3) and Later Without Failover)
•Upgrading Exchange 2000 to Exchange 2003 (Cisco Unity 4.0(3) and Later Without Failover)
•Reconfiguring Cisco Unity (Version 4.0(3) and Later Without Failover)
Note that if you are upgrading the existing partner server to Exchange 2003, Cisco Unity will continue to function after you do the procedures in the "Upgrading Exchange 2000 to Exchange 2003 (Cisco Unity 4.0(3) and Later Without Failover)" subsection, so you do not have to immediately do the procedures in the "Reconfiguring Cisco Unity (Version 4.0(3) and Later Without Failover)" subsection.
If you are replacing the existing physical server with a new server running Exchange 2003, do not decommission the existing partner Exchange 2000 server until you have completed all three subsections.
Note If the Cisco Unity server is running Cisco Unity 4.0(2) or earlier, upgrade to the shipping version before you upgrade to Exchange 2003. See the applicable chapter in this guide, and use the task list for upgrading Cisco Unity without failover:
•Chapter 1, "Upgrading Cisco Unity 4.x Software to the Shipping Version"
•Chapter 2, "Upgrading Cisco Unity 3.x Software to the Shipping Version"
Downloading Software (Cisco Unity 4.0(3) and Later Without Failover)
This subsection lists the software needed to reconfigure a Cisco Unity system for Exchange 2003. Note the following considerations:
•The downloads may total 200 MB or more. Use a computer with a high-speed Internet connection, and confirm that the computer has sufficient disk space or has access to a network drive with sufficient disk space.
•The downloads are all self-extracting executable files. When all downloads are complete, extract the updates, then delete the downloaded .exe files to free disk space.
•The documentation instructs you when to install the software you download.
Download the following software:
•Exchange 2003 Service Pack 1, available on the Microsoft website.
•The latest version of the Cisco Unity Directory Walker (DbWalker) utility, available at http://ciscounitytools.com/App_DirectoryWalker4.htm. Db Walker is used to check the consistency of and correct errors in the Cisco Unity database before the upgrade.
•The latest versions of the Cisco Unity Disaster Recovery tools (DiRT), available at http://ciscounitytools.com/App_DisasterRecoveryTools.htm. DiRT is used to back up Cisco Unity data before the upgrade and to restore Cisco Unity data, if necessary.
•The latest version of the Cisco Unity Permissions wizard, available at http://ciscounitytools.com/App_PW_403.htm.
Upgrading Exchange 2000 to Exchange 2003 (Cisco Unity 4.0(3) and Later Without Failover)
Before you begin the upgrade, note the following considerations:
•If you are upgrading an Exchange 2000 server to Exchange 2003, back up Exchange data before you upgrade.
•If you are upgrading the current partner Exchange 2000 server to Exchange 2003, Cisco Unity will continue to take messages during the upgrade and will store the messages in the Unity Message Repository (UMR) until Exchange 2003 is running. Subscribers will be able to retrieve voice messages that were left in the UMR after the Exchange upgrade began, but they will not be able to retrieve messages that are already in Exchange mailboxes on the Exchange server being upgraded until Exchange 2003 is running.
•If you are using the Cisco Unity Voice Connector for Microsoft Exchange and you are decommissioning an Exchange 2000 server on which the Voice Connector is installed, install the Voice Connector on another Exchange server before you decommission the old server.
If the Voice Connector is installed on an Exchange 2000 server that you are upgrading to Exchange 2003, you do not need to do anything special. The same Voice Connector is used for both Exchange 2000 and Exchange 2003, and it is not affected by the Exchange upgrade.
For Cisco Unity 4.0(2) and earlier, when the partner Exchange server was running Exchange 2000, Permissions Wizard automatically added the message store services account to the Exchange Domain Servers group. If you are upgrading from Exchange 2000 to Exchange 2003 on a Cisco Unity system that has been upgraded from 4.0(2) or earlier, do the following procedure to remove the Cisco Unity message store services account from the Exchange Domain Servers group, or message delivery will fail.
To Remove the Message Store Services Account from the Exchange Domain Servers Group (Selected Configurations Only)
Step 1 On the Windows Start menu, click Programs > Microsoft Exchange > Active Directory Users and Computers.
Step 2 In the left pane of Active Directory Users and Computers, expand the domain that contains the Cisco Unity server, and click Users.
Step 3 In the right pane, double-click Exchange Domain Servers.
Step 4 In the Exchange Domain Servers Properties dialog box, click the Members tab.
Step 5 In the Members list, click the name of the message store services account, and click Remove.
Step 6 Click Yes to confirm.
Step 7 Click OK to close the Exchange Domain Servers Properties dialog box.
Step 8 Close Active Directory Users and Computers.
To Upgrade from Exchange 2000 to Exchange 2003 (Cisco Unity 4.0(3) and Later Without Failover)
Step 1 Follow the Microsoft documentation either to install Exchange 2003 on at least one server or to upgrade an existing server to Exchange 2003. This is the server that you will use as the partner Exchange server. For more information on a partner server, see the "Choosing a Different Partner Exchange Server" section on page 6-1.
Step 2 Back up the Exchange 2003 server that you will use as the partner Exchange server and all Exchange 2003 servers that will home mailboxes for Cisco Unity subscribers.
Caution Microsoft recommends that you back up Exchange servers before you install Exchange 2003 Service Pack 1 because Service Pack 1 cannot be uninstalled.
Step 3 Install Exchange 2003 Service Pack 1 on the Exchange 2003 server that you will use as the partner Exchange server and on all Exchange 2003 servers that will home mailboxes for Cisco Unity subscribers.
Reconfiguring Cisco Unity (Version 4.0(3) and Later Without Failover)
This subsection contains five procedures. Do them in the order listed to reconfigure Cisco Unity after you have upgraded from Exchange 2000 to Exchange 2003.
If you are reconfiguring multiple Cisco Unity servers without failover, do all of the procedures on each server.
To Check the Consistency of the Cisco Unity Database (Cisco Unity 4.0(3) and Later Without Failover)
Step 1 On the Cisco Unity server, install the latest version of DbWalker, if it is not already installed.
Step 2 Run DbWalker, and correct all errors that the utility finds. Refer to DbWalker Help for detailed instructions on running the utility and on correcting errors in the database. (The Help file, DbWalker.htm, is in the same directory as DbWalker.exe.)
To Back Up Cisco Unity Data (Cisco Unity 4.0(3) and Later Without Failover)
Step 1 On the Cisco Unity server, install the latest versions of DiRT, if the tools are not already installed.
Step 2 Back up Cisco Unity data by using the Disaster Recovery Backup tool. Refer to DiRT Help for detailed instructions. (The Help file, UnityDisasterRecovery.htm, is in the same directory as UnityDisasterRecoveryBackup.exe.)
Caution Follow Help carefully. DiRT includes a variety of options that you must understand to use the tools successfully. In addition, the account you are logged on as when you back up Cisco Unity data must have sufficient permissions or the backup will fail.
To Upgrade Exchange Software on the Cisco Unity Server (Cisco Unity 4.0(3) and Later Without Failover)
Step 1 Exit the Cisco Unity software.
Step 2 Upgrade Exchange 2000 System Management Tools to Exchange 2003 System Management Tools. Refer to Exchange 2003 Help for more information.
Step 3 Install Exchange 2003 Service Pack 1.
In the next procedure, you run the Cisco Unity Permissions wizard. If you do not run the wizard, Cisco Unity will not function properly with Exchange 2003 Service Pack 1.
To Run the Cisco Unity Permissions Wizard (Cisco Unity 4.0(3) and Later Without Failover)
Step 1 On theCisco Unity server, install the latest version of the Cisco Unity Permissions wizard, if it is not already installed.
Step 2 Log on to the Cisco Unity server by using an account that meets the following criteria:
•Is a member of the Domain Admins group in the domain in which the Cisco Unity server is installed.
•Is either an Exchange Full Administrator or a member of the Domain Admins group in the domain in which Exchange mailboxes for Cisco Unity subscribers are homed. (If Exchange mailboxes are homed in multiple domains, the account that you log on with must be either an Exchange Full Administrator or a member of the Domain Admins group in a domain that contains all of the domains in which mailboxes are homed.)
Caution If you try to run the Permissions wizard by using an account that has less than the default permissions for a Domain Admin, the wizard may not be able to set all of the permissions required by the installation account and the service accounts. If the Permissions wizard cannot set all of the required permissions, Cisco Unity will not run properly.
Step 3 Run the Permissions wizard from the directory in which you installed it in Step 1. For more information, refer to Permissions wizard Help.
Caution If you are installing any new Exchange 2003 servers on which Cisco Unity subscriber mailboxes will be homed, remember to specify the mailstores on the servers when you run the Permissions wizard so that Cisco Unity has the necessary rights to the new servers. Otherwise, Cisco Unity subscribers whose Exchange mailboxes are homed on the servers will not be able to send or receive voice messages.
Step 4 Restart the Cisco Unity server.
Step 5 If you are upgrading the existing partner server and will continue to use the server as the partner server, you are finished with the upgrade. Do not do the last procedure.
If you are specifying a different partner server, do the following procedure, "To Configure Cisco Unity for Exchange 2003 (Cisco Unity 4.0(3) and Later Without Failover)."
To Configure Cisco Unity for Exchange 2003 (Cisco Unity 4.0(3) and Later Without Failover)
Step 1 Confirm that Exchange is running on the partner Exchange server that you chose in Step 1 of the "To Upgrade from Exchange 2000 to Exchange 2003 (Cisco Unity 4.0(3) and Later Without Failover)" procedure.
If Exchange is not running, configuring Cisco Unity for Exchange will fail.
Step 2 On the Cisco Unity server, log on to Windows by using the Cisco Unity installation account.
Step 3 Exit the Cisco Unity software.
Step 4 On the Windows Start menu, click Settings > Control Panel > Add/Remove Programs.
Step 5 In the list of currently installed programs, click Cisco Unity Message Store Configuration Wizard, and click Change/Remove.
Step 6 On the Cisco Unity Message Store Configuration Wizard Welcome screen, click Next.
Step 7 Enter the password for the installation account, and click Next.
Step 8 If an account does not exist for the Cisco Unity Administrator (Cisco Unity administration account), skip to Step 9.
If an account exists for the Cisco Unity Administrator, click Change, then in the Select User dialog box, double-click the name of the Cisco Unity administration account.
Step 9 Click Next.
Step 10 In the Select Partner Message Store dialog box, click Microsoft Exchange 2003, and click Next.
Step 11 In the Select Mailbox Location dialog box, specify the partner Exchange 2003 server and the mailbox store in which to create new mailboxes.
Step 12 Click Next.
Step 13 In the Select Active Directory Containers for New Objects dialog box, specify the domain in which you want Cisco Unity to create users and distribution lists.
Step 14 If custom organizational units were created for users or distribution lists, click the corresponding Change button to specify them.
Step 15 Click Next.
Step 16 Follow the on-screen prompts until message store configuration is complete.
Upgrading Exchange 2000 to Exchange 2003 for Cisco Unity 4.0(3) and Later with Failover Configured (Unified Messaging)
Note If there are one or more non-failover Cisco Unity servers in the forest, see the "Upgrading Exchange 2000 to Exchange 2003 for Cisco Unity 4.0(3) and Later Without Failover (Unified Messaging)" section to upgrade those servers.
The upgrade procedures in this section were tested in a configuration that included the following elements:
•A domain controller/global catalog server (DC/GC).
•A Cisco Unity 4.0(4) primary server (member server).
•A Cisco Unity 4.0(4) secondary server (member server).
•An Exchange 2000 Server with Exchange 2000 Service Pack 3 (member server).
•A separate Exchange 2003 server that was added during the upgrade (member server).
Caution All testing was done with the old partner Exchange server, the new partner Exchange server, and the Cisco Unity server in the same Active Directory domain. Upgrading from one version of Exchange to another when the partner Exchange servers are in separate Active Directory domains has not been tested, and may fail.
The following subsections contain the instructions for upgrading a Cisco Unity 4.0(3) or later system configured for failover from Exchange 2000 to Exchange 2003:
•Downloading Software (Cisco Unity 4.0(3) and Later with Failover Configured)
•Upgrading Exchange 2000 to Exchange 2003 (Cisco Unity 4.0(3) and Later with Failover Configured)
•Reconfiguring Cisco Unity (Version 4.0(3) and Later with Failover Configured)
Note that if you are upgrading the existing partner server to Exchange 2003, Cisco Unity will continue to function after you do the procedures in the "Upgrading Exchange 2000 to Exchange 2003 (Cisco Unity 4.0(3) and Later with Failover Configured)" subsection, so you do not have to immediately do the procedures in the "Reconfiguring Cisco Unity (Version 4.0(3) and Later with Failover Configured)" subsection.
If you are replacing the existing physical server with a new server running Exchange 2003, do not decommission the existing partner Exchange 2000 server until you have completed all three subsections.
Note If the Cisco Unity failover servers are running Cisco Unity 4.0(2) or earlier, upgrade to Cisco Unity 4.0(4) before you upgrade to Exchange 2003. See the applicable chapter in this guide, and use the task list for upgrading Cisco Unity without failover:
•Chapter 1, "Upgrading Cisco Unity 4.x Software to the Shipping Version"
•Chapter 2, "Upgrading Cisco Unity 3.x Software to the Shipping Version"
Downloading Software (Cisco Unity 4.0(3) and Later with Failover Configured)
This section lists the software needed to reconfigure a Cisco Unity system for Exchange 2003. Note the following considerations:
•The downloads may total 200 MB or more. Use a computer with a high-speed Internet connection, and confirm that the computer has sufficient disk space or has access to a network drive with sufficient disk space.
•The downloads are all self-extracting executable files. When all downloads are complete, extract the updates, then delete the downloaded .exe files to free disk space.
•The documentation instructs you when to install the software you download.
Download the following software:
•Exchange 2003 Service Pack 1, available on the Microsoft website.
•The latest version of the Cisco Unity Directory Walker (Db Walker) utility, available at http://ciscounitytools.com/App_DirectoryWalker4.htm. Db Walker is used to check the consistency of and correct errors in the Cisco Unity database before the upgrade.
•The latest version of the Cisco Unity Disaster Recovery Tools (DiRT), at http://ciscounitytools.com/App_DisasterRecoveryTools.htm. DiRT is used to back up the Cisco Unity server before the upgrade.
•The latest version of the Cisco Unity Permissions wizard, available at http://ciscounitytools.com/App_PW_403.htm.
Upgrading Exchange 2000 to Exchange 2003 (Cisco Unity 4.0(3) and Later with Failover Configured)
Before you begin the upgrade, note the following considerations:
•If you are upgrading an Exchange 2000 server to Exchange 2003, back up Exchange data before you upgrade.
•If you are upgrading the current partner Exchange 2000 server to Exchange 2003, Cisco Unity will continue to take messages during the upgrade and will store those messages in the Unity Message Repository (UMR) until Exchange 2003 is running. Subscribers will be able to retrieve voice messages that were left in the UMR after the Exchange upgrade began, but they will not be able to retrieve messages that are already in Exchange mailboxes on the Exchange server being upgraded until Exchange 2003 is running.
•If you are using the Cisco Unity Voice Connector for Microsoft Exchange and you are decommissioning an Exchange 2000 server on which the Voice Connector is installed, install the Voice Connector on another Exchange server before you decommission the old server.
If the Voice Connector is installed on an Exchange 2000 server that you are upgrading to Exchange 2003, you do not need to do anything special. The same Voice Connector is used for both Exchange 2000 and Exchange 2003, and it is not affected by the Exchange upgrade.
For Cisco Unity 4.0(2) and earlier, when the partner Exchange server was running Exchange 2000, Permissions Wizard automatically added the message store services account to the Exchange Domain Servers group. If you are upgrading from Exchange 2000 to Exchange 2003 on a Cisco Unity system that has been upgraded from 4.0(2) or earlier, do the following procedure to remove the Cisco Unity message store services account from the Exchange Domain Servers group, or message delivery will fail.
To Remove the Message Store Services Account from the Exchange Domain Servers Group (Selected Configurations Only)
Step 1 On the Windows Start menu, click Programs > Microsoft Exchange > Active Directory Users and Computers.
Step 2 In the left pane of Active Directory Users and Computers, expand the domain that contains the Cisco Unity server, and click Users.
Step 3 In the right pane, double-click Exchange Domain Servers.
Step 4 In the Exchange Domain Servers Properties dialog box, click the Members tab.
Step 5 In the Members list, click the name of the message store services account, and click Remove.
Step 6 Click Yes to confirm.
Step 7 Click OK to close the Exchange Domain Servers Properties dialog box.
Step 8 Close Active Directory Users and Computers.
To Upgrade from Exchange 2000 to Exchange 2003 (Cisco Unity 4.0(3) and Later with Failover Configured)
Step 1 Follow the Microsoft documentation either to install Exchange 2003 on at least one server or to upgrade an existing server to Exchange 2003. This is the server that you will use as the partner Exchange server. For more information on a partner server, see the "Choosing a Different Partner Exchange Server" section on page 6-1.
Step 2 Back up the Exchange 2003 server that you will use as the partner Exchange server and all Exchange 2003 servers that will home mailboxes for Cisco Unity subscribers.
Caution Microsoft recommends that you back up Exchange servers before you install Exchange 2003 Service Pack 1 because Service Pack 1 cannot be uninstalled.
Step 3 Install Exchange 2003 Service Pack 1 on the Exchange 2003 server that you will use as the partner Exchange server and on all Exchange 2003 servers that will home mailboxes for Cisco Unity subscribers.
Reconfiguring Cisco Unity (Version 4.0(3) and Later with Failover Configured)
This subsection contains 11 procedures. Do them in the order listed to reconfigure Cisco Unity after you have upgraded from Exchange 2000 to Exchange 2003.
To Check the Consistency of the Cisco Unity Database on the Primary Server (Cisco Unity 4.0(3) and Later with Failover Configured)
Step 1 On the primary server, install the latest version of DbWalker, if it is not already installed.
Step 2 Run DbWalker, and correct all errors that the utility finds. Refer to DbWalker Help for detailed instructions on running the utility and on correcting errors in the database. (The Help file, DbWalker.htm, is in the same directory as DbWalker.exe.)
To Back Up Cisco Unity Data on the Secondary Server (Cisco Unity 4.0(3) and Later with Failover Configured)
Step 1 On the secondary server, install the latest versions of DiRT, if the tools are not already installed.
Step 2 Back up Cisco Unity data by using the Disaster Recovery Backup tool. Refer to DiRT Help for detailed instructions. (The Help file, UnityDisasterRecovery.htm, is in the same directory as UnityDisasterRecoveryBackup.exe.)
Caution Follow Help carefully. DiRT includes a variety of options that you must understand to use the tools successfully. In addition, the account you are logged on as when you back up Cisco Unity data must have sufficient permissions or the backup will fail.
To Disable Automatic Failover, and Stop File and SQL Replication (Cisco Unity 4.0(3) and Later with Failover Configured)
Step 1 If the primary server is active, skip to Step 5.
If the primary server is not active, on the Windows Start menu on the secondary server, click Programs > Cisco Unity >Failover Monitor.
Step 2 Click Failback.
Step 3 Click OK to confirm that you want to fail back to the primary server.
Step 4 Close the Failover Monitor.
Step 5 On the primary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.
Step 6 Click Advanced.
Step 7 Check the Disable Automatic Failover and Failback check box.
Step 8 Click OK, and close the Failover Monitor.
Step 9 On the primary server, on the Windows Start menu, click Programs > Administrative Tools > Services.
Step 10 In the right pane, double-click AvCsNodeMgr.
Step 11 On the General tab, click Stop.
Step 12 In the Startup Type list, click Disabled.
Step 13 Click OK.
Step 14 Close the Services window.
Caution Because the Node Manager service is disabled, file replication stops. Replication is re-enabled when normal failover operation resumes.
Step 15 On the secondary server, on the Windows Start menu, click Programs > Administrative Tools > Services.
Step 16 In the right pane, double-click AvCsNodeMgr.
Step 17 On the General tab, click Stop.
Step 18 In the Startup Type list, click Disabled.
Step 19 Click OK.
Step 20 Close the Services window.
Step 21 On the primary server, on the Windows Start menu, click Programs > Microsoft SQL Server > Enterprise Manager.
Step 22 In the left pane of the Console Root window, browse to the Replication node for the primary server. Typically, the node is three levels under the Microsoft SQL Servers node.
Step 23 Right-click the Replication node, and click Disable Publishing. The Disable Publishing and Distribution wizard appears.
Step 24 On the Welcome page, click Next.
Step 25 On the Disable Publishing page, click Yes, then click Next.
Step 26 On the Confirm Dropping of Publications page, click Next.
Step 27 On the Completing page, click Finish.
Step 28 When the process is completed, click OK.
Step 29 Close the Console Root window.
Step 30 Exit Enterprise Manager.
To Upgrade Exchange Software on the Primary Server (Cisco Unity 4.0(3) and Later with Failover Configured)
Step 1 On the primary server, exit the Cisco Unity software.
Step 2 Upgrade Exchange 2000 System Management Tools to Exchange 2003 System Management Tools. Refer to Exchange 2003 Help for more information.
Step 3 Install Exchange 2003 Service Pack 1.
In the next procedure, you run the Cisco Unity Permissions wizard. If you do not run the wizard, Cisco Unity will not function properly with Exchange 2003 Service Pack 1. In this case, you run the Permissions wizard only on the primary server because the changes required for Exchange 2003 Service Pack 1 all appear in Active Directory.
To Run the Cisco Unity Permissions Wizard on the Primary Server (Cisco Unity 4.0(3) and Later with Failover Configured)
Step 1 On the primary server, install the latest version of the Cisco Unity Permissions wizard, if it is not already installed.
Step 2 Log on to the primary server by using an account that meets the following criteria:
•Is a member of the Domain Admins group in the domain in which the Cisco Unity server is installed.
•Is either an Exchange Full Administrator or a member of the Domain Admins group in the domain in which Exchange mailboxes for Cisco Unity subscribers are homed. (If Exchange mailboxes are homed in multiple domains, the account that you log on with must be either an Exchange Full Administrator or a member of the Domain Admins group in a domain that contains all of the domains in which mailboxes are homed.)
Caution If you try to run the Permissions wizard by using an account that has less than the default permissions for a Domain Admin, the wizard may not be able to set all of the permissions required by the installation account and the services accounts. If the Permissions wizard cannot set all of the required permissions, Cisco Unity will not run properly.
Step 3 Run the Permissions wizard from the directory in which you installed it in Step 1. For more information, refer to Permissions wizard Help.
Caution If you are installing any new Exchange 2003 servers on which Cisco Unity subscriber mailboxes will be homed, remember to specify the mailstores on the servers when you run Permissions wizard so that Cisco Unity has the necessary rights to the new servers. Otherwise, Cisco Unity subscribers whose Exchange mailboxes are homed on the servers will not be able to send or receive voice messages.
Step 4 Restart the primary server.
Step 5 If you are upgrading the existing partner server and will continue to use that server as the partner server, skip to the "To Upgrade Exchange Software on the Secondary Server (Cisco Unity 4.0(3) and Later with Failover Configured)" procedure.
If you want to specify a different partner server, do the following procedure, "To Configure the Primary Server for Exchange 2003 (Cisco Unity 4.0(3) and Later with Failover Configured)."
To Configure the Primary Server for Exchange 2003 (Cisco Unity 4.0(3) and Later with Failover Configured)
Step 1 Confirm that Exchange is running on the partner Exchange server that you chose in Step 1 of the "To Upgrade from Exchange 2000 to Exchange 2003 (Cisco Unity 4.0(3) and Later with Failover Configured)" section.
If Exchange is not running, configuring Cisco Unity for Exchange will fail.
Step 2 On the primary server, log on to Windows by using the Cisco Unity installation account.
Step 3 Exit the Cisco Unity software.
Step 4 On the Windows Start menu, click Settings > Control Panel > Add/Remove Programs.
Step 5 In the list of currently installed programs, click Cisco Unity Message Store Configuration Wizard, and click Change/Remove.
Step 6 On the Cisco Unity Message Store Configuration Wizard Welcome screen, click Next.
Step 7 Enter the password for the installation account, and click Next.
Step 8 If an account does not exist for the Cisco Unity Administrator (Cisco Unity administration account), skip to Step 9.
If an account exists for the Cisco Unity Administrator, click Change, then in the Select User dialog box, double-click the name of the Cisco Unity administration account.
Step 9 Click Next.
Step 10 In the Select Partner Message Store dialog box, click Microsoft Exchange 2003, and click Next.
Step 11 In the Select Mailbox Location dialog box, specify the partner Exchange 2003 server and the mailbox store in which to create new mailboxes.
Step 12 Click Next.
Step 13 In the Select Active Directory Containers for New Objects dialog box, specify the domain in which you want Cisco Unity to create users and distribution lists.
Step 14 If custom organizational units were created for users or distribution lists, click the corresponding Change button to specify them.
Step 15 Click Next.
Step 16 Follow the on-screen prompts until message store configuration is complete.
Step 17 Restart the primary server.
To Upgrade Exchange Software on the Secondary Server (Cisco Unity 4.0(3) and Later with Failover Configured)
Step 1 On the secondary server, exit the Cisco Unity software.
Step 2 Upgrade Exchange 2000 System Management Tools to Exchange 2003 System Management Tools. Refer to the Exchange 2003 Help for more information.
Step 3 Install Exchange 2003 Service Pack 1.
Step 4 If you are upgrading the existing partner server and will continue to use that server as the partner server, restart the secondary server, then skip to the "To Configure Failover on the Primary Server (Cisco Unity 4.0(3) and Later with Failover Configured)" procedure.
If you want to specify a different partner server, do the following procedure, "To Configure the Secondary Server for Exchange 2003 (Cisco Unity 4.0(3) and Later with Failover Configured)."
To Configure the Secondary Server for Exchange 2003 (Cisco Unity 4.0(3) and Later with Failover Configured)
Step 1 Confirm that Exchange is running on the partner Exchange server that you chose in Step 1 of the "To Upgrade from Exchange 2000 to Exchange 2003 (Cisco Unity 4.0(3) and Later with Failover Configured)" section.
If Exchange is not running, configuring Cisco Unity for Exchange will fail.
Step 2 On the secondary server, log on to Windows by using the Cisco Unity installation account.
Step 3 Exit the Cisco Unity software.
Step 4 Browse to the CommServer\ConfigurationSetup directory.
Step 5 Double-click Setup.exe to start the Cisco Unity Message Store Configuration wizard.
Step 6 On the Welcome screen, click Next.
Step 7 Enter the password for the installation account, and click Next.
Step 8 If an account does not exist for the Cisco Unity Administrator (Cisco Unity administration account), skip to Step 9.
If an account exists for the Cisco Unity Administrator, click Change, then in the Select User dialog box, double-click the name of the Cisco Unity administration account.
Step 9 Click Next.
Step 10 In the Select Partner Message Store dialog box, click Microsoft Exchange 2003, and click Next.
Step 11 In the Select Mailbox Location dialog box, choose the partner Exchange 2003 server and the mailbox store in which to create new mailboxes.
Step 12 Click Next.
Step 13 In the Select Active Directory Containers for New Objects dialog box, specify the domain in which you want Cisco Unity to create users and distribution lists.
Step 14 If custom organizational units were created for users or distribution lists, click the corresponding Change button to specify them.
Step 15 Click Next.
Step 16 Follow the on-screen prompts until message store configuration is complete.
Step 17 Restart the secondary server.
To Configure Failover on the Primary Server (Cisco Unity 4.0(3) and Later with Failover Configured)
Step 1 In Windows Explorer, browse to the CommServer directory.
Step 2 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.
Step 3 On the Welcome page, click Next.
Step 4 On the Specify Server Role page, click Primary Server, and click Next.
Step 5 On the Enter the Name of Your Server page, click Browse, select the name of the secondary server, and click OK. The IP address for the secondary server is filled in automatically.
Step 6 Click Next.
Step 7 On the Enter Failover Account Information page, click Browse, and double-click the name of the message store services account. This is the account that the failover service will log on as.
The account you select must have the right to act as part of the operating system and to log on as a service, and must be a member of the Local Administrators group.
Caution You must specify the same account on both the primary and secondary servers.
Step 8 In the Password field, enter the password for the account that the failover service will log on as, and click Next.
Step 9 On the Begin Configuring Your Server page, click Configure. The wizard verifies settings and configures failover on the primary server.
If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and click Configure again.
Step 10 On the Completing page, click Finish.
To Configure Failover on the Secondary Server (Cisco Unity 4.0(3) and Later with Failover Configured)
Step 1 On the Windows taskbar, double-click the system clock. The Date/Time Properties dialog box appears.
Step 2 Set the time to the same hour and minute as shown on the primary server, and click OK.
Step 3 In Windows Explorer, browse to the CommServer directory.
Step 4 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.
Step 5 On the Welcome page, click Next.
Step 6 On the Specify Server Role page, click Secondary Server, and click Next.
Step 7 On the Enter the Name of Your Server page, click Browse, select the name of the primary server, and click OK. The IP address for the primary server is filled in automatically.
Step 8 Click Next.
Step 9 On the Enter Failover Account Information page, click Browse, and double-click the name of the message store services account. This is the account that the failover service will log on as.
The account you select must have the right to act as part of the operating system and to log on as a service, and must be a member of the Local Administrators group.
Caution You must specify the same account on both the primary and secondary servers.
Step 10 In the Password field, enter the password for the account that the failover service will log on as, and click Next.
Step 11 On the Begin Configuring Your Server page, click Configure. The wizard verifies settings and configures failover on the secondary server.
If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and click Configure again.
Step 12 On the Completing page, click Finish.
Upgrading Exchange 5.5 with Active Directory to Exchange 2003 or Exchange 2000 for Cisco Unity 4.x Without Failover (Unified Messaging)
Caution Exchange 2003 is not supported with Cisco Unity 4.0(2) and earlier. If you are upgrading to Exchange 2003, you must upgrade to Cisco Unity 4.0(3) or later before you begin the Exchange upgrade.
Note If Cisco Unity failover is configured, see the "Upgrading Exchange 5.5 with Active Directory to Exchange 2003 or Exchange 2000 for Cisco Unity 4.x with Failover Configured (Unified Messaging)" section to upgrade those servers.
The upgrade procedures in this section were tested in a configuration that included the following elements:
•A domain controller/global catalog server (DC/GC).
•An Exchange 5.5 server.
•A Cisco Unity 4.0(2) server.
•A separate Exchange 2000 server that was added during the upgrade.
•A two-way Active Directory Connector configured between Exchange 5.5 and Active Directory.
Caution All testing was done with the old partner Exchange server, the new partner Exchange server, and the Cisco Unity server in the same Active Directory domain. Upgrading from one version of Exchange to another when the partner Exchange servers are in separate Active Directory domains has not been tested, and may fail.
The following subsections contain the instructions for upgrading a Cisco Unity 4.x system without failover from Exchange 5.5 with Active Directory to Exchange 2003 or Exchange 2000:
•Preparing for the Upgrade (Cisco Unity 4.x Without Failover)
•Upgrading Exchange 5.5 with Active Directory to Exchange 2003 or Exchange 2000 (Cisco Unity 4.x Without Failover)
•Reconfiguring Cisco Unity (Version 4.x Without Failover)
•Moving Mailboxes and Removing Exchange (Optional) (Cisco Unity 4.x Without Failover)
If there are multiple Cisco Unity servers in the forest, you must do some procedures on every Cisco Unity server in the forest before you can move on to the next procedure. Each procedure indicates on which server or servers it must be done.
Caution Before you begin moving mailboxes from Exchange 5.5 to Exchange 2003 or Exchange 2000, you must reconfigure all Cisco Unity servers to use an Exchange 2003 or Exchange 2000 server as the partner server. Otherwise, subscribers whose mailboxes are homed in Exchange 5.5 will not be able to send voice messages to subscribers whose mailboxes are homed in Exchange 2003 or Exchange 2000, and vice versa.
Preparing for the Upgrade (Cisco Unity 4.x Without Failover)
To Check the Consistency of the Cisco Unity Database and Back Up Cisco Unity Data (Cisco Unity 4.x Without Failover)
Step 1 On the Cisco Unity server, install the latest versions of the following applications:
•The Cisco Unity Directory Walker (DbWalker) utility, available at http://ciscounitytools.com/App_DirectoryWalker4.htm.
•The Cisco Unity Disaster Recovery tools (DiRT), available at http://ciscounitytools.com/App_DisasterRecoveryTools.htm.
Step 2 Run DbWalker, and correct all errors that the utility finds. Refer to DbWalker Help for detailed instructions on running the utility and on correcting errors in the database. (The Help file, DbWalker.htm, is in the same directory as DbWalker.exe.)
Step 3 Back up Cisco Unity data by using the Disaster Recovery Backup tool. Refer to DiRT Help for detailed instructions. (The Help file, UnityDisasterRecovery.htm, is in the same directory as UnityDisasterRecoveryBackup.exe.)
Caution Follow Help carefully. DiRT includes a variety of options that you must understand to use the tools successfully. In addition, the account you are logged on as when you back up Cisco Unity data must have sufficient permissions or the backup will fail.
Caution Cisco does not support downgrading from Exchange 2003 or Exchange 2000 to Exchange 5.5. If the upgrade fails and you want to revert to Exchange 5.5, you must restore Cisco Unity data from a DiRT backup. Without the backup, you will not be able to restore Cisco Unity data and have Cisco Unity function properly with Exchange 5.5.
Step 4 Repeat this procedure on any other Cisco Unity servers in the forest.
Upgrading Exchange 5.5 with Active Directory to Exchange 2003 or Exchange 2000 (Cisco Unity 4.x Without Failover)
If the system is not using Cisco Unity networking to connect multiple Cisco Unity servers or to allow Cisco Unity to communicate with another voice messaging system, skip the next procedure.
Do the next procedure to uninstall the Cisco Unity Voice Connector for Microsoft Exchange 5.5 only if you are using Cisco Unity networking and you are upgrading existing Exchange 5.5 servers to Exchange 2003 or Exchange 2000.
Caution After you uninstall the Voice Connector, Cisco Unity networking stops functioning.
If you are installing Exchange 2003 or Exchange 2000 on new servers instead of upgrading existing Exchange 5.5 servers, you can wait to uninstall the Voice Connector until later in the process.
To Uninstall the Voice Connector for Exchange 5.5 (Cisco Unity 4.x Without Failover)
Step 1 Log on to the Exchange server on which the Voice Connector is installed.
Step 2 On the Windows Start menu, click Control Panel > Settings > Add/Remove Programs.
Step 3 Select the Voice Connector.
Step 4 Follow the on-screen prompts to uninstall the Voice Connector.
To Set Up a Mixed-Messaging Environment (Cisco Unity 4.x Without Failover)
Step 1 Set up a mixed-messaging environment according to Microsoft recommendations. Note the following considerations:
•The Exchange 2003 and/or Exchange 2000 servers must be installed into one of the existing Exchange 5.5 sites.
•Microsoft does not support an in-place upgrade from Exchange 5.5 to Exchange 2003. For more information, refer to Microsoft Knowledge Base article 822942, Considerations When You Upgrade to Exchange Server 2003.
•The Exchange version of the Active Directory connector must be installed.
•A recipient connection agreement must be set up to replicate data between the Exchange 5.5 directory and Active Directory. (An Exchange organization that has multiple sites will have multiple Active Directory connectors and multiple connection agreements.) If you want to be able to use the Cisco Unity Administrator to add Cisco Unity subscribers who will be homed in Exchange 5.5, on the Advanced tab of the Properties dialog box for this connection agreement, you must check the This Is a Primary Connection Agreement for the Connected Exchange Organization check box.
Caution Do not make any Exchange 5.5 servers into domain controller/global catalog servers. Doing so during a migration to Exchange 2003 or Exchange 2000 is not supported by Microsoft, and Cisco Unity will not function properly in such a configuration.
Step 2 Install the current Exchange service pack and updates recommended for use with Cisco Unity on the following servers:
•On every Exchange 2003 or Exchange 2000 server on which Cisco Unity subscribers will be homed.
•On the partner Exchange server.
•On the Exchange server on which the Voice Connector, if any, is installed.
For a list of required and recommended service packs, refer to Recommended Service Packs and Updates for Use with Cisco Unity and the Cisco Unity Bridge at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/cmptblty/msupdate.htm.
With Exchange 2003 or Exchange 2000, several changes need to be made to the Active Directory schema for Cisco Unity to work properly. To see the changes that the schema update program makes, browse to the directory Schema\LdifScripts on Cisco Unity DVD 1 or CD 1, and view the file Avdirmonex2k.ldf.
Additional changes to the schema are required if you are setting up VPIM or a Cisco Unity Bridge. To see the changes that the schema update program makes for VPIM, view the file Vpimgateway.ldf. To see the changes for the Bridge, view the file Omnigateway.ldf.
To update the schema, use either the next procedure or any tool that applies LDIF scripts (for example, the Microsoft Ldifde utility).
You need to update the schema only once, regardless of how many Cisco Unity servers there are in the Active Directory forest. (For Cisco Unity Digital Networking, all servers must be in the same forest, so they use the same Active Directory schema.)
To Extend the Active Directory Schema (Cisco Unity 4.x Without Failover)
Step 1 Confirm that all domain controllers are on line before making the schema updates. Schema replication will occur only when all domain controllers are on line.
Step 2 On the domain controller that is the schema master, log on by using an account that is a member of the Schema Administrators group.
Step 3 On Cisco Unity DVD 1 or CD 1, or from the location to which you saved the downloaded Cisco Unity CD 1 image files, browse to the directory ADSchemaSetup, and double-click ADSchemaSetup.exe.
Step 4 In the dialog box, double-click a row to choose the language in which you will view ADSchemaSetup.
Step 5 In the Active Directory Schema Setup dialog box, check the Exchange 2000 Directory Monitor check box.
If you plan to use VPIM Networking or Bridge Networking, also check the applicable check boxes.
Step 6 When the LDAP Data Interchange Format (LDIF) scripts have finished running, click OK.
Step 7 When the schema extension has finished, Ldif.log and LDif.err files are saved to the desktop. View the contents of the files to confirm that the extension completed successfully.
Step 8 Wait for the changes to the schema to replicate throughout the forest before adding information to the primary location and to delivery locations. Changes to the schema may take 15 minutes or more to replicate.
Note To determine whether changes have replicated and to force replication if necessary, use the Replication Monitor, which is available when you install Support Tools from the Windows 2000 compact disc.
If the system is not using Cisco Unity networking, skip the next procedure.
Do the next procedure only if the system is using Cisco Unity networking and you have not yet uninstalled the Cisco Unity Voice Connector for Microsoft Exchange 5.5.
Caution After you uninstall the Voice Connector, Cisco Unity networking stops functioning.
To Uninstall the Voice Connector for Exchange 5.5 (Cisco Unity 4.x Without Failover)
Step 1 Log on to the Exchange server on which the Voice Connector is installed.
Step 2 On the Windows Start menu, click Control Panel > Settings > Add/Remove Programs.
Step 3 Select the Voice Connector.
Step 4 Follow the on-screen prompts to uninstall the Voice Connector.
Reconfiguring Cisco Unity (Version 4.x Without Failover)
To Remove the Current Message Store Configuration (Cisco Unity 4.x Without Failover)
Step 1 Exit the Cisco Unity software.
Step 2 On the Cisco Unity server, log on to Windows by using the Cisco Unity installation account.
Step 3 On the Windows Start menu, click Settings > Control Panel > Add/Remove Programs.
Step 4 Click Cisco Unity Message Store Configuration Wizard.
Step 5 Click Change/Remove.
Step 6 Follow the on-screen prompts to remove the Cisco Unity message store configuration.
Even when Exchange is not installed on the Cisco Unity server, Exchange administration software is required because it includes the Microsoft messaging API (MAPI), the application programming interface that Cisco Unity uses to communicate with Exchange for addressing, sending, and retrieving messages.
To Install Exchange 2003 System Manager or Exchange 2000 System Manager on the Cisco Unity Server (Cisco Unity 4.x Without Failover)
Step 1 On the Cisco Unity server, log on to Windows by using the Cisco Unity installation account.
Step 2 Install the applicable version of Exchange System Manager:
For Exchange 2003
|
Follow the Microsoft procedure for installing Exchange 2003 System Manager.
|
For Exchange 2000
|
a. Insert the Cisco Unity Message Store 2000 disc in the CD-ROM drive.
If the disc does not run automatically, browse to the root directory, and double-click Launch.exe.
b. Click Exchange Server Setup.
c. Follow the on-screen prompts until you are prompted to choose between installing Exchange 2000 System Manager and upgrading. Choose to upgrade.
d. When you are asked whether to replace a target file that is newer than the source file, click No to All.
|
Step 3 Install the current Exchange service pack and updates recommended for use with Cisco Unity.
For a list of required and recommended service packs, refer to Recommended Service Packs and Updates for Use with Cisco Unity and the Cisco Unity Bridge at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/cmptblty/msupdate.htm.
Step 4 Shut down and restart the Cisco Unity server.
Step 5 Repeat this procedure on any other Cisco Unity servers in the forest.
To Create Accounts and Set Rights and Permissions (Cisco Unity 4.x Without Failover)
If you have not done so already, create accounts and set rights and permissions as described in the "Creating Accounts for the Installation and Setting Rights and Permissions" chapter of the applicable Cisco Unity installation guide for your configuration at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
Note the following considerations:
•You can use the same accounts for every Cisco Unity server in the forest. (For example, you create only one installation account, not one installation account for every Cisco Unity server.)
•Some of the permissions that the Cisco Unity Permissions wizard sets are server specific, so you must run the Permissions wizard on every Cisco Unity server in the forest. In failover configurations, this includes both the primary and secondary servers.
•If you use the same accounts for every Cisco Unity server in the forest, you set Exchange permissions only once for the entire forest.
If you do not use the same accounts for every Cisco Unity server in the forest, you must run the Permissions wizard and set Exchange permissions on each of the accounts as required.
To Configure Cisco Unity Services on the Cisco Unity Server for Exchange 2003 or Exchange 2000 (Cisco Unity 4.x Without Failover)
Step 1 On the Cisco Unity server, log on to Windows by using the Cisco Unity installation account.
Step 2 On the Windows desktop, double-click the Cisco Unity Tools Depot icon.
Step 3 Expand Administration Tools, and double-click Service Configuration Wizard.
Step 4 Follow the on-screen prompts.
Step 5 Repeat this procedure on any other Cisco Unity servers in the forest.
To Configure the Cisco Unity Server for Exchange 2003 or Exchange 2000 (Cisco Unity 4.x Without Failover)
Step 1 Choose the new partner Exchange server. See the "Choosing a Different Partner Exchange Server" section on page 6-1.
Step 2 Confirm that Exchange is running on the new partner Exchange server. If Exchange is not running, configuring Cisco Unity for Exchange will fail.
Step 3 On the Cisco Unity server, log on to Windows by using the Cisco Unity installation account.
Step 4 Exit the Cisco Unity software.
Step 5 Browse to the CommServer\ConfigurationSetup directory.
Step 6 Double-click Setup.exe to start the Cisco Unity Message Store Configuration wizard.
Step 7 On the Welcome screen, click Next.
Step 8 Enter the password for the installation account, and click Next.
Step 9 If an account does not exist for the Cisco Unity Administrator (Cisco Unity administration account), skip to Step 10.
If an account exists for the Cisco Unity Administrator, click Change, then in the Select User dialog box, double-click the name of the Cisco Unity administration account.
Step 10 Click Next.
Step 11 In the Select Partner Message Store dialog box, click Microsoft Exchange 2003 or Microsoft Exchange 2000, depending on the version of Exchange installed on the partner Exchange server.
Step 12 Click Next.
Step 13 In the Select Mailbox Location dialog box, specify the partner Exchange server and the mailbox store in which to create new mailboxes,
Step 14 Click Next.
Step 15 In the Select Active Directory Containers for New Objects dialog box, specify the domain in which you want Cisco Unity to create users and distribution lists.
Step 16 If custom organizational units were created for users or distribution lists, click the corresponding Change button to specify them.
Step 17 Click Next.
Step 18 Follow the on-screen prompts until message store configuration is complete.
Step 19 Repeat this procedure on any other Cisco Unity servers in the forest.
If you still have mailboxes for some Cisco Unity subscribers homed in Exchange 5.5 and if those subscribers are having problems accessing their voice messages, do the next procedure. Otherwise, skip the procedure.
To Troubleshoot Problems Accessing Voice Messages in Mixed-Messaging Environments (Cisco Unity 4.x Without Failover)
Step 1 Confirm that the Unity_<servername> account, which is the account that Cisco Unity uses to send voice messages from outside callers, is visible as a recipient in Exchange 5.5 Administrator. If it is not, the Active Directory connector may need to be reconfigured to allow it to replicate to Exchange 5.5.
Step 2 Restart the Exchange 5.5 server.
If the system is not using AMIS Networking or SMTP Networking, skip the next procedure.
If the system is using AMIS Networking or SMTP Networking, do the next procedure to install the Cisco Unity Voice Connector for Microsoft Exchange 2000. Note that the Voice Connector for Exchange 2000 is also used for Exchange 2003.
To Install the Cisco Unity Voice Connector for Microsoft Exchange 2000 (Cisco Unity 4.x Without Failover)
If you are using AMIS Networking, install the Voice Connector by using the procedure in the "Setting Up the Voice Connector for Exchange 2000" subsection in the "Procedures for Setting Up Cisco Unity to Use AMIS" section in the "AMIS Networking" chapter of the Networking in Cisco Unity Guide, Release 4.0(5) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/net/net405/ex/index.htm.
If you are using SMTP Networking, install the Voice Connector by using the procedure in the "Setting Up the Voice Connector for Exchange 2000" subsection in the "Procedures: Setting Up Cisco Unity to Use SMTP Networking" section in the "SMTP Networking" chapter of the Networking in Cisco Unity Guide, Release 4.0(5) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/net/net405/ex/index.htm.
Moving Mailboxes and Removing Exchange (Optional) (Cisco Unity 4.x Without Failover)
To Move User Mailboxes from Exchange 5.5 to Exchange 2003 or Exchange 2000 (Optional) (Cisco Unity 4.x Without Failover)
Use Active Directory Users and Computers. Refer to the Microsoft documentation for detailed information.
To Remove Exchange 5.5 Administrator from a Cisco Unity Server (Optional) (Cisco Unity 4.x Without Failover)
Step 1 Insert the Cisco Unity Message Store 2000 disc in the CD-ROM drive.
If the disc does not run automatically, browse to the root directory, and double-click Launch.exe.
Step 2 Click Change, and follow the on-screen prompts to remove Exchange 5.5 Administrator.
Step 3 Shut down and restart the Cisco Unity server.
Step 4 Repeat this procedure on any other Cisco Unity servers in the forest.
To Remove Exchange 5.5 from the Environment (Optional) (Cisco Unity 4.x Without Failover)
Refer to the Microsoft documentation for information on removing Exchange 5.5 from the site, uninstalling the Exchange 5.5 server, and removing the Active Directory Connectors.
Upgrading Exchange 5.5 with Active Directory to Exchange 2003 or Exchange 2000 for Cisco Unity 4.x with Failover Configured (Unified Messaging)
Caution Exchange 2003 is not supported with Cisco Unity 4.0(2) and earlier. If you are upgrading to Exchange 2003, you must upgrade to Cisco Unity 4.0(3) or later before you begin the Exchange upgrade.
Note If there are one or more non-failover Cisco Unity servers in the forest, see the "Upgrading Exchange 5.5 with Active Directory to Exchange 2003 or Exchange 2000 for Cisco Unity 4.x Without Failover (Unified Messaging)" section to upgrade those servers.
The upgrade procedures in this section were tested in a configuration that included the following elements:
•A domain controller/global catalog server.
•A Cisco Unity 4.0(2) primary server (member server).
•A Cisco Unity 4.0(2) secondary server (member server).
•An Exchange 5.5 Server with Exchange 5.5 Service Pack 4 (member server).
•A separate Exchange 2000 server that was added during the upgrade.
•A two-way Active Directory Connector configured between Exchange 5.5 and Active Directory.
Caution All testing was done with the old partner Exchange server, the new partner Exchange server, and the Cisco Unity server in the same Active Directory domain. Upgrading from one version of Exchange to another when the partner Exchange servers are in separate Active Directory domains has not been tested, and may fail.
The following subsections contain the instructions for upgrading a Cisco Unity 4.x system with failover configured from Exchange 5.5 with Active Directory to Exchange 2003 or Exchange 2000:
•Preparing for the Upgrade (Cisco Unity 4.x with Failover Configured)
•Upgrading Exchange 5.5 to Exchange 2003 or Exchange 2000 (Cisco Unity 4.x with Failover Configured)
•Reconfiguring Cisco Unity (Version 4.x with Failover Configured)
•Moving Mailboxes and Removing Exchange (Optional) (Cisco Unity 4.x with Failover Configured)
Caution Before you begin moving mailboxes from Exchange 5.5 to Exchange 2003 or Exchange 2000, you must reconfigure all Cisco Unity servers to use an Exchange 2003 or Exchange 2000 server as the partner server. Otherwise, subscribers whose mailboxes are homed in Exchange 5.5 will not be able to send voice messages to subscribers whose mailboxes are homed in Exchange 2003 or Exchange 2000, and vice versa.
Preparing for the Upgrade (Cisco Unity 4.x with Failover Configured)
To Check the Consistency of the Cisco Unity Database on the Primary Server (Cisco Unity 4.x with Failover Configured)
Step 1 On the primary server, install the latest version of the Cisco Unity Directory Walker (DbWalker) utility, available at http://ciscounitytools.com/App_DirectoryWalker4.htm.
Step 2 Run DbWalker, and correct all errors that the utility finds. Refer to DbWalker Help for detailed instructions on running the utility and on correcting errors in the database. (The Help file, DbWalker.htm, is in the same directory as DbWalker.exe.)
To Back Up Cisco Unity Data on the Secondary Server (Cisco Unity 4.x with Failover Configured)
Step 1 On the secondary server, install the latest versions of the Cisco Unity Disaster Recovery tools (DiRT), available at http://ciscounitytools.com/App_DisasterRecoveryTools.htm.
Step 2 Back up Cisco Unity data by using the Disaster Recovery Backup tool. Refer to DiRT Help for detailed instructions. (The Help file, UnityDisasterRecovery.htm, is in the same directory as UnityDisasterRecoveryBackup.exe.)
Caution Follow Help carefully. DiRT includes a variety of options that you must understand to use the tools successfully. In addition, the account you are logged on as when you back up Cisco Unity data must have sufficient permissions or the backup will fail.
Caution Cisco does not support downgrading from Exchange 2003 or Exchange 2000 to Exchange 5.5. If the upgrade fails and you want to revert to Exchange 5.5, you must restore Cisco Unity data from a DiRT backup. Without the backup, you will not be able to restore Cisco Unity data and have Cisco Unity function properly with Exchange 5.5.
Upgrading Exchange 5.5 to Exchange 2003 or Exchange 2000 (Cisco Unity 4.x with Failover Configured)
If the system is not using Cisco Unity networking to connect multiple Cisco Unity servers or to allow Cisco Unity to communicate with another voice messaging system, skip the next procedure.
Do the next procedure to uninstall the Cisco Unity Voice Connector for Microsoft Exchange 5.5 only if you are using Cisco Unity networking and you are upgrading existing Exchange 5.5 servers to Exchange 2003 or Exchange 2000.
Caution After you uninstall the Voice Connector, Cisco Unity networking stops functioning.
If you are installing Exchange 2003 or Exchange 2000 on new servers instead of upgrading existing Exchange 5.5 servers, you can wait to uninstall the Voice Connector until later in the process.
To Uninstall the Voice Connector for Exchange 5.5 (Cisco Unity 4.x with Failover Configured)
Step 1 Log on to the Exchange server on which the Voice Connector is installed.
Step 2 On the Windows Start menu, click Control Panel > Settings > Add/Remove Programs.
Step 3 Select the Voice Connector.
Step 4 Follow the on-screen prompts to uninstall the Voice Connector.
To Set Up a Mixed-Messaging Environment (Cisco Unity 4.x with Failover Configured)
Step 1 Set up a mixed-messaging environment according to Microsoft recommendations. Note the following considerations:
•The Exchange 2003 and/or Exchange 2000 servers must be installed into one of the existing Exchange 5.5 sites.
•Microsoft does not support an in-place upgrade from Exchange 5.5 to Exchange 2003. For more information, refer to Microsoft Knowledge Base article 822942, Considerations When You Upgrade to Exchange Server 2003.
•The Exchange version of the Active Directory connector must be installed.
•A recipient connection agreement must be set up to replicate data between the Exchange 5.5 directory and Active Directory. (An Exchange organization that has multiple sites will have multiple Active Directory connectors and multiple connection agreements.) If you want to be able to use the Cisco Unity Administrator to add Cisco Unity subscribers who will be homed in Exchange 5.5, on the Advanced tab of the Properties dialog box for this connection agreement, you must check the This Is a Primary Connection Agreement for the Connected Exchange Organization check box.
Caution Do not make any Exchange 5.5 servers into domain controller/global catalog servers. Doing so during a migration to Exchange 2003 or Exchange 2000 is not supported by Microsoft, and Cisco Unity will not function properly in such a configuration.
Step 2 Install the current Exchange service pack and updates recommended for use with Cisco Unity on the following servers:
•On every Exchange 2003 or Exchange 2000 server on which Cisco Unity subscribers will be homed.
•On the partner Exchange server.
•On the Exchange server on which the Voice Connector, if any, is installed.
For a list of required and recommended service packs, refer to Recommended Service Packs and Updates for Use with Cisco Unity and the Cisco Unity Bridge at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/cmptblty/msupdate.htm.
With Exchange 2003 or Exchange 2000, several changes need to be made to the Active Directory schema for Cisco Unity to work properly. To see the changes that the schema update program makes, browse to the directory Schema\LdifScripts on Cisco Unity DVD 1 or CD 1, and view the file Avdirmonex2k.ldf.
Additional changes to the schema are required if you are setting up VPIM or a Cisco Unity Bridge. To see the changes that the schema update program makes for VPIM, view the file Vpimgateway.ldf. To see the changes for the Bridge, view the file Omnigateway.ldf.
To update the schema, use either the next procedure or any tool that applies LDIF scripts (for example, the Microsoft Ldifde utility).
You need to update the schema only once, regardless of how many Cisco Unity servers there are in the Active Directory forest. (For failover and for Cisco Unity Digital Networking, all servers must be in the same forest, so they use the same Active Directory schema.)
To Extend the Active Directory Schema (Cisco Unity 4.x with Failover Configured)
Step 1 Confirm that all domain controllers are on line before making the schema updates. Schema replication will occur only when all domain controllers are on line.
Step 2 On the domain controller that is the schema master, log on by using an account that is a member of the Schema Administrators group.
Step 3 On Cisco Unity DVD 1 or CD 1, or from the location to which you saved the downloaded Cisco Unity CD 1 image files, browse to the directory ADSchemaSetup, and double-click ADSchemaSetup.exe.
Step 4 In the dialog box, double-click a row to choose the language in which you will view ADSchemaSetup.
Step 5 In the Active Directory Schema Setup dialog box, check the Exchange 2000 Directory Monitor check box.
If you plan to use VPIM Networking or Bridge Networking, check the applicable check boxes.
Step 6 When the LDAP Data Interchange Format (LDIF) scripts have finished running, click OK.
Step 7 When the schema extension has finished, Ldif.log and LDif.err files are saved to the desktop. View the contents of the files to confirm that the extension completed successfully.
Step 8 Wait for the changes to the schema to replicate throughout the forest before adding information to the primary location and to delivery locations. Changes to the schema may take 15 minutes or more to replicate.
Note To determine whether changes have replicated and to force replication if necessary, use the Replication Monitor, which is available when you install Support Tools from the Windows 2000 compact disc.
If the system is not using Cisco Unity networking, skip the next procedure.
Do the next procedure only if the system is using Cisco Unity networking and you have not yet uninstalled the Cisco Unity Voice Connector for Microsoft Exchange 5.5.
Caution After you uninstall the Voice Connector, Cisco Unity networking stops functioning.
To Uninstall the Voice Connector for Exchange 5.5 (Cisco Unity 4.x with Failover Configured)
Step 1 Log on to the Exchange server on which the Voice Connector is installed.
Step 2 On the Windows Start menu, click Control Panel > Settings > Add/Remove Programs.
Step 3 Select the Voice Connector.
Step 4 Follow the on-screen prompts to uninstall the Voice Connector.
Reconfiguring Cisco Unity (Version 4.x with Failover Configured)
To Disable Failover and Stop Replication (Cisco Unity 4.x with Failover Configured)
Step 1 If the primary server is active, skip to Step 5.
If the primary server is not active, on the Windows Start menu on the secondary server, click Programs > Cisco Unity >Failover Monitor.
Step 2 Click Failback.
Step 3 Click OK to confirm that you want to fail back to the primary server.
Step 4 Close the Failover Monitor.
Step 5 On the primary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.
Step 6 Click Advanced.
Step 7 Check the Disable Automatic Failover and Failback check box.
Step 8 Click OK, and close the Failover Monitor.
Step 9 On the primary server, on the Windows Start menu, click Programs > Administrative Tools > Services.
Step 10 In the right pane, double-click AvCsNodeMgr.
Step 11 On the General tab, click Stop.
Step 12 In the Startup Type list, click Disabled.
Step 13 Click OK.
Step 14 Close the Services window.
Caution Because the Node Manager service is disabled, file replication stops. Replication is re-enabled when normal failover operation resumes.
Step 15 On the secondary server, on the Windows Start menu, click Programs > Administrative Tools > Services.
Step 16 In the right pane, double-click AvCsNodeMgr.
Step 17 On the General tab, click Stop.
Step 18 In the Startup Type list, click Disabled.
Step 19 Click OK.
Step 20 Close the Services window.
Step 21 On the primary server, on the Windows Start menu, click Programs > Microsoft SQL Server > Enterprise Manager.
Step 22 In the left pane of the Console Root window, browse to the Replication node for the primary server. Typically, the node is three levels under the Microsoft SQL Servers node.
Step 23 Right-click the Replication node, and click Disable Publishing. The Disable Publishing and Distribution wizard appears.
Step 24 On the Welcome page, click Next.
Step 25 On the Disable Publishing page, click Yes, then click Next.
Step 26 On the Confirm Dropping of Publications page, click Next.
Step 27 On the Completing page, click Finish.
Step 28 When the process is completed, click OK.
Step 29 Close the Console Root window.
Step 30 Exit Enterprise Manager.
To Remove the Current Message Store Configuration from the Secondary Server (Cisco Unity 4.x with Failover Configured)
Step 1 On the secondary Cisco Unity server, log on to Windows by using the Cisco Unity installation account.
Step 2 Exit the Cisco Unity software.
Step 3 On the Windows Start menu, click Settings > Control Panel > Add/Remove Programs.
Step 4 Click Cisco Unity Message Store Configuration Wizard.
Step 5 Click Change/Remove.
Step 6 Follow the on-screen prompts to remove the message store configuration.
Even when Exchange is not installed on the Cisco Unity server, Exchange administration software is required because it includes the Microsoft messaging API (MAPI), the application programming interface that Cisco Unity uses to communicate with Exchange for addressing, sending, and retrieving messages.
To Install Exchange 2003 System Manager or Exchange 2000 System Manager on the Secondary Server (Cisco Unity 4.x with Failover Configured)
Step 1 On the secondary server, log on to Windows by using the Cisco Unity installation account.
Step 2 Install the applicable version of Exchange System Manager:
For Exchange 2003
|
Follow the Microsoft procedure for installing Exchange 2003 System Manager.
|
For Exchange 2000
|
a. Insert the Cisco Unity Message Store 2000 disc in the CD-ROM drive.
If the disc does not run automatically, browse to the root directory, and double-click Launch.exe.
b. Click Exchange Server Setup.
c. Follow the on-screen prompts until you are prompted to choose between installing Exchange 2000 System Manager and upgrading. Choose to upgrade.
d. When you are asked whether to replace a target file that is newer than the source file, click No to All.
|
Step 3 Install the current Exchange service pack and updates recommended for use with Cisco Unity.
For a list of required and recommended service packs, refer to Recommended Service Packs and Updates for Use with Cisco Unity and the Cisco Unity Bridge at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/cmptblty/msupdate.htm.
Step 4 Shut down and restart the Cisco Unity server.
To Create Accounts and Set Rights and Permissions (Cisco Unity 4.x with Failover Configured)
If you have not done so already, create accounts and set rights and permissions as described in the "Creating Accounts for the Installation and Setting Rights and Permissions" chapter of the applicable Cisco Unity installation guide for your configuration at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
Note the following considerations:
•You can use the same accounts for every Cisco Unity server in the forest. (For example, you create only one installation account, not one installation account for every Cisco Unity server.)
•Some of the permissions that the Cisco Unity Permissions wizard sets are server specific, so you must run the Permissions wizard on every Cisco Unity server in the forest. In failover configurations, this includes both the primary and secondary servers.
•If you use the same accounts for every Cisco Unity server in the forest, you set Exchange permissions only once for the entire forest.
If you do not use the same accounts for every Cisco Unity server in the forest, you must run the Permissions wizard and set Exchange permissions on each of the accounts as required.
To Configure Cisco Unity Services on the Secondary Server for Exchange 2003 or Exchange 2000 (Cisco Unity 4.x with Failover Configured)
Step 1 On the secondary server, log on to Windows by using the Cisco Unity installation account.
Step 2 On the Windows desktop, double-click the Cisco Unity Tools Depot icon.
Step 3 Expand Administration Tools, and double-click Service Configuration Wizard.
Step 4 Follow the on-screen prompts.
To Configure the Secondary Server for Exchange 2003 or Exchange 2000 (Cisco Unity 4.x with Failover Configured)
Step 1 Choose the new partner Exchange server. See the "Choosing a Different Partner Exchange Server" section on page 6-1.
Step 2 Confirm that Exchange is running on the new partner Exchange server. If Exchange is not running, configuring Cisco Unity for Exchange will fail.
Step 3 On the secondary server, log on to Windows by using the Cisco Unity installation account.
Step 4 Exit the Cisco Unity software.
Step 5 Browse to the CommServer\ConfigurationSetup directory.
Step 6 Double-click Setup.exe to start the Cisco Unity Message Store Configuration wizard.
Step 7 On the Welcome screen, click Next.
Step 8 Enter the password for the installation account, and click Next.
Step 9 If an account does not exist for the Cisco Unity Administrator (Cisco Unity administration account), skip to Step 10.
If an account exists for the Cisco Unity Administrator, click Change, then in the Select User dialog box, double-click the name of the Cisco Unity administration account.
Step 10 Click Next.
Step 11 In the Select Partner Message Store dialog box, click Microsoft Exchange 2003 or Microsoft Exchange 2000, depending on the version of Exchange installed on the partner Exchange server.
Step 12 Click Next.
Step 13 In the Select Mailbox Location dialog box, specify the partner Exchange server and the mailbox store in which to create new mailboxes,
Step 14 Click Next.
Step 15 In the Select Active Directory Containers for New Objects dialog box, specify the domain in which you want Cisco Unity to create users and distribution lists.
Step 16 If custom organizational units were created for users or distribution lists, click the corresponding Change button to specify them.
Step 17 Click Next.
Step 18 Follow the on-screen prompts until message store configuration is complete.
If Cisco Unity subscribers will be homed in both Exchange 5.5 and in Exchange 2003 or Exchange 2000, do the following procedure. If no subscribers will be homed in Exchange 5.5, skip this procedure.
To Configure Permissions for Exchange 5.5 (Cisco Unity 4.x with Failover Configured)
Step 1 Run the Exchange 5.5 System Administrator.
Step 2 Click the name of the Exchange site.
Step 3 On the File menu, click Properties.
Step 4 Click the Permissions tab.
Step 5 Give the Exchange Domain Servers group Service Account Admin permissions at the site level.
Step 6 Give the Exchange Domain Servers group Service Account Admin permissions at the configuration level.
Step 7 Restart the Exchange 5.5 server.
To Remove the Current Message Store Configuration from the Primary Server (Cisco Unity 4.x with Failover Configured)
Step 1 On the primary server, log on to Windows by using the Cisco Unity installation account.
Step 2 Exit the Cisco Unity software.
Step 3 On the Windows Start menu, click Settings > Control Panel > Add/Remove Programs.
Step 4 Click Cisco Unity Message Store Configuration Wizard.
Step 5 Click Change/Remove.
Step 6 Follow the on-screen prompts to remove the message store configuration.
To Install Exchange 2003 System Manager or Exchange 2000 System Manager on the Primary Server (Cisco Unity 4.x with Failover Configured)
Step 1 On the primary server, log on to Windows by using the Cisco Unity installation account.
Step 2 Install the applicable version of Exchange System Manager:
For Exchange 2003
|
Follow the Microsoft procedure for installing Exchange 2003 System Manager.
|
For Exchange 2000
|
a. Insert the Cisco Unity Message Store 2000 disc in the CD-ROM drive.
If the disc does not run automatically, browse to the root directory, and double-click Launch.exe.
b. Click Exchange Server Setup.
c. Follow the on-screen prompts until you are prompted to choose between installing Exchange 2000 System Manager and upgrading. Choose to upgrade.
d. When you are asked whether to replace a target file that is newer than the source file, click No to All.
|
Step 3 Install the current Exchange service pack and updates recommended for use with Cisco Unity.
For a list of required and recommended service packs, refer to Recommended Service Packs and Updates for Use with Cisco Unity and the Cisco Unity Bridge at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/cmptblty/msupdate.htm.
Step 4 Shut down and restart the Cisco Unity server.
To Set Permissions on the Primary Server (Cisco Unity 4.x with Failover Configured)
On the primary server, run the Cisco Unity Permissions wizard. (Active Directory permissions have already been set for the new accounts, but some server-specific permissions must be set on the primary server.) Refer to Permissions wizard Help for detailed instructions.
To Configure Cisco Unity Services on the Primary Server for Exchange 2003 or Exchange 2000 (Cisco Unity 4.x with Failover Configured)
Step 1 On the primary server, log on to Windows by using the Cisco Unity installation account.
Step 2 On the Windows desktop, double-click the Cisco Unity Tools Depot icon.
Step 3 Expand Administration Tools, and double-click Service Configuration Wizard.
Step 4 Follow the on-screen prompts.
To Configure the Primary Server for Exchange 2003 or Exchange 2000 (Cisco Unity 4.x with Failover Configured)
Step 1 Confirm that Exchange is running on the new partner Exchange server. If Exchange is not running, configuring Cisco Unity for Exchange will fail.
Step 2 On the primary server, log on to Windows by using the Cisco Unity installation account.
Step 3 Exit the Cisco Unity software.
Step 4 Browse to the CommServer\ConfigurationSetup directory.
Step 5 Double-click Setup.exe to start the Cisco Unity Message Store Configuration wizard.
Step 6 On the Welcome screen, click Next.
Step 7 Enter the password for the installation account, and click Next.
Step 8 If an account does not exist for the Cisco Unity Administrator (Cisco Unity administration account), skip to Step 10.
If an account exists for the Cisco Unity Administrator, click Change, then in the Select User dialog box, double-click the name of the Cisco Unity administration account.
Step 9 Click Next.
Step 10 In the Select Partner Message Store dialog box, click Microsoft Exchange 2003 or Microsoft Exchange 2000, depending on the version of Exchange installed on the partner Exchange server.
Step 11 Click Next.
Step 12 In the Select Mailbox Location dialog box, specify the partner Exchange server and the mailbox store in which to create new mailboxes,
Step 13 Click Next.
Specify the same partner Exchange server that you specified when you configured the secondary server for Exchange.
Step 14 In the Select Active Directory Containers for New Objects dialog box, specify the domain in which you want Cisco Unity to create users and distribution lists.
Step 15 If custom organizational units were created for users or distribution lists, click the corresponding Change button to specify them.
Step 16 Click Next.
Step 17 Follow the on-screen prompts until message store configuration is complete.
To Configure Failover on the Primary Server (Cisco Unity 4.x with Failover Configured)
Step 1 In Windows Explorer, browse to the CommServer directory.
Step 2 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.
Step 3 On the Welcome page, click Next.
Step 4 On the Specify Server Role page, click Primary Server, and click Next.
Step 5 On the Enter the Name of Your Server page, click Browse, select the name of the secondary server, and click OK. The IP address for the secondary server is filled in automatically.
Step 6 Click Next.
Step 7 On the Enter Failover Account Information page, click Browse, and double-click the name of the message store services account. This is the account that the failover service will log on as.
The account you select must have the right to act as part of the operating system and to log on as a service, and must be a member of the Local Administrators group.
Caution You must specify the same account on both the primary and secondary servers.
Step 8 In the Password field, enter the password for the account that the failover service will log on as, and click Next.
Step 9 On the Begin Configuring Your Server page, click Configure. The wizard verifies settings and configures failover on the primary server.
If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and click Configure again.
Step 10 On the Completing page, click Finish.
To Configure Failover on the Secondary Server (Cisco Unity 4.x with Failover Configured)
Step 1 On the Windows taskbar, double-click the system clock. The Date/Time Properties dialog box appears.
Step 2 Set the time to the same hour and minute as shown on the primary server, and click OK.
Step 3 In Windows Explorer, browse to the CommServer directory.
Step 4 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.
Step 5 On the Welcome page, click Next.
Step 6 On the Specify Server Role page, click Secondary Server, and click Next.
Step 7 On the Enter the Name of Your Server page, click Browse, select the name of the primary server, and click OK. The IP address for the primary server is filled in automatically.
Step 8 Click Next.
Step 9 On the Enter Failover Account Information page, click Browse, and double-click the name of the message store services account. This is the account that the failover service will log on as.
The account you select must have the right to act as part of the operating system and to log on as a service, and must be a member of the Local Administrators group.
Caution You must specify the same account on both the primary and secondary servers.
Step 10 In the Password field, enter the password for the account that the failover service will log on as, and click Next.
Step 11 On the Begin Configuring Your Server page, click Configure. The wizard verifies settings and configures failover on the secondary server.
If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and click Configure again.
Step 12 On the Completing page, click Finish.
If the system is not using AMIS Networking, Cisco Unity Bridge, VPIM, or SMTP Networking, skip the next procedure.
If the system is using AMIS Networking, Cisco Unity Bridge, VPIM, or SMTP Networking, install the Cisco Unity Voice Connector for Microsoft Exchange 2000. Note that the Voice Connector for Exchange 2000 is also used for Exchange 2003.
To Install the Cisco Unity Voice Connector for Microsoft Exchange 2000 (Cisco Unity 4.x with Failover Configured)
If you are using AMIS Networking, install the Voice Connector by using the procedure in the "Setting Up the Voice Connector for Exchange 2000" subsection in the "Procedures for Setting Up Cisco Unity to Use AMIS" section in the "AMIS Networking" chapter of the Networking in Cisco Unity Guide, Release 4.0(5) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/net/net405/ex/index.htm.
If you are using SMTP Networking, install the Voice Connector by using the procedure in the "Setting Up the Voice Connector for Exchange 2000" subsection in the "Procedures: Setting Up Cisco Unity to Use SMTP Networking" section in the "SMTP Networking" chapter of the Networking in Cisco Unity Guide, Release 4.0(5) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/net/net405/ex/index.htm.
Moving Mailboxes and Removing Exchange (Optional) (Cisco Unity 4.x with Failover Configured)
To Move User Mailboxes From Exchange 5.5 to Exchange 2003 or Exchange 2000 (Optional) (Cisco Unity 4.x with Failover Configured)
Use Active Directory Users and Computers. Refer to the Microsoft documentation for detailed information.
To Remove Exchange 5.5 Administrator from the Cisco Unity Servers (Optional) (Cisco Unity 4.x with Failover Configured)
Step 1 On the secondary server, exit the Cisco Unity software.
Step 2 Insert the Cisco Unity Message Store 2000 disc in the CD-ROM drive.
If the disc does not run automatically, browse to the root directory, and double-click Launch.exe.
Step 3 Click Change, and follow the on-screen prompts to remove Exchange 5.5 Administrator.
Step 4 Shut down and restart the secondary server.
Step 5 On the primary server, manually initiate failover to the secondary server. For detailed instructions, refer to the applicable version of the Cisco Unity Failover Configuration and Administration Guide:
•For Cisco Unity 4.x, refer to the "Manually Initiating Failover or Failback" section in the "Monitoring and Maintaining Cisco Unity Failover" chapter of the guide at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/fail/fail401/ex/index.htm.
•For Cisco Unity 3.1, refer to the "Manually Failing Over or Failing Back" section in the "Maintaining Cisco Unity Failover" chapter of the guide at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/fail/fail31/index.htm.
Step 6 Repeat Step 1 through Step 4 on the primary server.
Step 7 On the secondary server, manually initiate failback to the primary server.
To Remove Exchange 5.5 from the Environment (Optional) (Cisco Unity 4.x with Failover Configured)
Refer to the Microsoft documentation for information on removing Exchange 5.5 from the site, uninstalling the Exchange 5.5 server, and removing the Active Directory Connectors.
Upgrading Exchange 5.5 with Active Directory to Exchange 2000 for Cisco Unity 3.1(5) Without Failover (Unified Messaging)
Note If Cisco Unity failover is configured, see the "Upgrading Exchange 5.5 with Active Directory to Exchange 2000 for Cisco Unity 3.1(5) with Failover Configured (Unified Messaging)" section to upgrade those servers.
The upgrade procedures in this section were tested in a configuration that included the following elements:
•A domain controller/global catalog server (DC/GC).
•An Exchange 5.5 server.
•A Cisco Unity 3.1(5) server.
•A separate Exchange 2000 server that was added during the upgrade.
•A two-way Active Directory Connector configured between Exchange 5.5 and Active Directory.
Caution Cisco Unity 3.x does not support Exchange 2003. To upgrade to Exchange 2003, you must first upgrade Cisco Unity to version 4.0(3) or later. With Cisco Unity 3.x, you cannot run Exchange 2003 Forestprep to begin an upgrade to Exchange 2003, you cannot have an Exchange 2003 server in the same Active Directory forest as a Cisco Unity server, and you cannot home Cisco Unity subscribers in Exchange 2003. If you run Exchange 2003 Forestprep, the changes that it makes to Active Directory will cause Cisco Unity 3.x to stop functioning.
Caution All testing was done with the old partner Exchange server, the new partner Exchange server, and the Cisco Unity server in the same Active Directory domain. Upgrading from one version of Exchange to another when the partner Exchange servers are in separate Active Directory domains has not been tested, and may fail.
The following subsections contain the instructions for upgrading a Cisco Unity 3.1(5) system without failover from Exchange 5.5 with Active Directory to Exchange 2000:
•Preparing for the Upgrade (Cisco Unity 3.1(5) Without Failover)
•Upgrading Exchange 5.5 with Active Directory to Exchange 2000 (Cisco Unity 3.1(5) Without Failover)
•Reconfiguring Cisco Unity (Version 3.1(5) Without Failover)
•Moving Mailboxes and Removing Exchange (Optional) (Cisco Unity 3.1(5) Without Failover)
If there are multiple Cisco Unity servers in the forest, you must do some procedures on every Cisco Unity server in the forest before you can move on to the next procedure. Each procedure indicates on which server or servers it must be done.
Caution Before you begin moving mailboxes from Exchange 5.5 to Exchange 2000, you must reconfigure all Cisco Unity servers to use an Exchange 2000 server as the partner server. Otherwise, subscribers whose mailboxes are homed in Exchange 5.5 will not be able to send voice messages to subscribers whose mailboxes are homed in Exchange 2000, and vice versa.
Preparing for the Upgrade (Cisco Unity 3.1(5) Without Failover)
To Check the Consistency of the Cisco Unity Database and Back Up the Server (Cisco Unity 3.1(5) Without Failover)
Step 1 On the Cisco Unity server, install the latest versions of the following applications:
•The Cisco Unity Directory Walker (DbWalker) utility, available at http://ciscounitytools.com/App_DirectoryWalker3.htm.
•The Cisco Unity Disaster Recovery tools (DiRT), available at http://ciscounitytools.com/App_DisasterRecoveryTools.htm.
Step 2 Run DbWalker, and correct all errors that the utility finds. Refer to DbWalker Help for detailed instructions on running the utility and on correcting errors in the database. (The Help file, DbWalker.htm, is in the same directory as DbWalker.exe.)
Step 3 Back up Cisco Unity data by using the Disaster Recovery Backup tool. Refer to DiRT Help for detailed instructions. (The Help file, UnityDisasterRecovery.htm, is in the same directory as UnityDisasterRecoveryBackup.exe.)
Caution Follow Help carefully. DiRT includes a variety of options that you must understand to use the tools successfully. In addition, the account you are logged on as when you back up Cisco Unity data must have sufficient permissions or the backup will fail.
Caution Cisco does not support downgrading from Exchange 2003 or Exchange 2000 to Exchange 5.5. If the upgrade fails and you want to revert to Exchange 5.5, you must restore Cisco Unity data from a DiRT backup. Without the backup, you will not be able to restore Cisco Unity data and have Cisco Unity function properly with Exchange 5.5.
Upgrading Exchange 5.5 with Active Directory to Exchange 2000 (Cisco Unity 3.1(5) Without Failover)
If the system is not using Cisco Unity networking to connect multiple Cisco Unity servers or to allow Cisco Unity to communicate with another voice messaging system, skip the next procedure.
Do the next procedure to uninstall the Cisco Unity Voice Connector for Microsoft Exchange 5.5 only if you are using Cisco Unity networking and you are upgrading existing Exchange 5.5 servers to Exchange 2000.
Caution After you uninstall the Voice Connector, Cisco Unity networking stops functioning.
If you are installing Exchange 2000 on new servers instead of upgrading existing Exchange 5.5 servers, you can wait to uninstall the Voice Connector until later in the process.
To Uninstall the Voice Connector for Exchange 5.5 (Cisco Unity 3.1(5) Without Failover)
Step 1 Log on to the Exchange server on which the Voice Connector is installed.
Step 2 On the Windows Start menu, click Control Panel > Settings > Add/Remove Programs.
Step 3 Select the Voice Connector.
Step 4 Follow the on-screen prompts to uninstall the Voice Connector.
To Set Up a Mixed-Messaging Environment (Cisco Unity 3.1(5) Without Failover)
Step 1 Set up a mixed-messaging environment according to Microsoft recommendations. Note the following considerations:
•The Exchange 2000 servers must be installed into one of the existing Exchange 5.5 sites.
•The Exchange version of the Active Directory connector must be installed.
•A recipient connection agreement must be set up to replicate data between the Exchange 5.5 directory and Active Directory. (An Exchange organization that has multiple sites will have multiple Active Directory connectors and multiple connection agreements.) If you want to be able to use the Cisco Unity Administrator to add Cisco Unity subscribers who will be homed in Exchange 5.5, on the Advanced tab of the Properties dialog box for this connection agreement, you must check the This Is a Primary Connection Agreement for the Connected Exchange Organization check box.
Caution Do not make any Exchange 5.5 servers into domain controller/global catalog servers. Doing so during a migration to Exchange 2000 is not supported by Microsoft, and Cisco Unity will not function properly in such a configuration.
Step 2 Install the current Exchange service pack and updates recommended for use with Cisco Unity on the following servers:
•On every Exchange 2000 server on which Cisco Unity subscribers will be homed.
•On the partner Exchange server.
•On the Exchange server on which the Voice Connector, if any, is installed.
For a list of required and recommended service packs, refer to Recommended Service Packs and Updates for Use with Cisco Unity and the Cisco Unity Bridge at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/cmptblty/msupdate.htm.
If the system is not using Cisco Unity networking, skip the next procedure.
Do the next procedure only if the system is using Cisco Unity networking and you have not yet uninstalled the Cisco Unity Voice Connector for Microsoft Exchange 5.5.
Caution After you uninstall the Voice Connector, Cisco Unity networking stops functioning.
To Uninstall the Voice Connector for Exchange 5.5 (Cisco Unity 3.1(5) Without Failover)
Step 1 Log on to the Exchange server on which the Voice Connector is installed.
Step 2 On the Windows Start menu, click Control Panel > Settings > Add/Remove Programs.
Step 3 Select the Voice Connector.
Step 4 Follow the on-screen prompts to uninstall the Voice Connector.
With Exchange 2000, several changes need to be made to the Active Directory schema for Cisco Unity to work properly. To see the changes that the schema update program makes, browse to the directory Schema\LdifScripts on Cisco Unity CD 1, and view the file Avdirmonex2k.ldf.
Additional changes to the schema are required if you are setting up a Cisco Unity Bridge. To see the changes that the schema update program makes for the Bridge, view the file Omnigateway.ldf.
To update the schema, use either the next procedure or any tool that applies LDIF scripts (for example, the Microsoft Ldifde utility).
You need to update the schema only once, regardless of how many Cisco Unity servers there are in the Active Directory forest. (For Cisco Unity Digital Networking, all servers must be in the same forest, so they use the same Active Directory schema.)
To Extend the Active Directory Schema (Cisco Unity 3.1(5) Without Failover)
Step 1 Confirm that all domain controllers are on line before making the schema updates. Schema replication will occur only when all domain controllers are on line.
Step 2 On the domain controller that is the schema master, log on by using an account that is a member of the Schema Administrators group.
Step 3 On Cisco Unity DVD 1 or CD 1, or from the location to which you saved the downloaded Cisco Unity CD 1 image files, browse to the directory ADSchemaSetup, and double-click ADSchemaSetup.exe.
Step 4 In the dialog box, double-click a row to choose the language in which you will view ADSchemaSetup.
Step 5 In the Active Directory Schema Setup dialog box, check the Exchange 2000 Directory Monitor check box.
If you plan to use Cisco Unity Bridge Networking, check the Exchange 2000 Bridge Connector check box.
Step 6 When the LDAP Data Interchange Format (LDIF) scripts have finished running, click OK.
Step 7 When the schema extension has finished, Ldif.log and LDif.err files are saved to the desktop. View the contents of the files to confirm that the extension completed successfully.
Step 8 Wait for the changes to the schema to replicate throughout the forest before adding information to the primary location and to delivery locations. Changes to the schema may take 15 minutes or more to replicate.
Note To determine whether changes have replicated and to force replication if necessary, use the Replication Monitor, which is available when you install Support Tools from the Windows 2000 compact disc.
Reconfiguring Cisco Unity (Version 3.1(5) Without Failover)
To Remove the Current Message Store Configuration (Cisco Unity 3.1(5) Without Failover)
Step 1 Exit the Cisco Unity software.
Step 2 On the Cisco Unity server, log on to Windows by using the Cisco Unity installation account.
Step 3 On the Windows Start menu, click Settings > Control Panel > Add/Remove Programs.
Step 4 Click Cisco Unity Message Store Configuration Wizard.
Step 5 Click Change/Remove.
Step 6 Follow the on-screen prompts to remove the message store configuration.
Even when Exchange is not installed on the Cisco Unity server, Exchange administration software is required because it includes the Microsoft messaging API (MAPI), the application programming interface that Cisco Unity uses to communicate with Exchange for addressing, sending, and retrieving messages.
To Install Exchange 2000 System Manager on the Cisco Unity Server (Cisco Unity 3.1(5) Without Failover)
Step 1 On the Cisco Unity server, log on to Windows by using the Cisco Unity installation account.
Step 2 Insert the Cisco Unity Message Store 2000 disc in the CD-ROM drive.
If the disc does not run automatically, browse to the root directory, and double-click Launch.exe.
Step 3 Click Exchange Server Setup.
Step 4 Follow the on-screen prompts until you are prompted to choose between installing Exchange 2000 System Manager and upgrading. Choose to upgrade.
Step 5 When you are asked whether to replace a target file that is newer than the source file, click No to All.
Step 6 Install the current Exchange service pack and updates recommended for use with Cisco Unity.
For a list of required and recommended service packs, refer to Recommended Service Packs and Updates for Use with Cisco Unity and the Cisco Unity Bridge at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/cmptblty/msupdate.htm.
Step 7 Shut down and restart the Cisco Unity server.
Step 8 Repeat this procedure on any other Cisco Unity servers in the forest.
To Create Accounts and Set Rights and Permissions (Cisco Unity 3.1(5) Without Failover)
If you have not done so already, create accounts and set rights and permissions as described in the following sections in the "Installing the Cisco Unity System" chapter of the Cisco Unity installation guide, Release 3.1:
•"About the Accounts Required for the Cisco Unity Installation"
•"Creating the Accounts"
•"Adding the Cisco Unity Administration Account to an Admins Group"
•"Setting Rights and Permissions with the Cisco Unity Permissions Wizard"
•"Setting Exchange Permissions"
This guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/inst/inst31/index.htm.
Note the following considerations:
•You can use the same accounts for every Cisco Unity server in the forest. (For example, you create only one installation account, not one installation account for every Cisco Unity server.)
•Some of the permissions that the Cisco Unity Permissions wizard sets are server specific, so you must run the Permissions wizard on every Cisco Unity server in the forest. In failover configurations, this includes both the primary and secondary servers.
•If you use the same accounts for every Cisco Unity server in the forest, you set Exchange permissions only once for the entire forest.
If you do not use the same accounts for every Cisco Unity server in the forest, you must run the Permissions wizard and set Exchange permissions on each of the accounts as required.
To Configure Cisco Unity for Exchange 2000 (Cisco Unity 3.1(5) Without Failover)
Step 1 Choose the new partner Exchange server. See the "Choosing a Different Partner Exchange Server" section on page 6-1.
Step 2 Confirm that Exchange is running on the new partner Exchange server. If Exchange is not running, configuring Cisco Unity for Exchange will fail.
Step 3 On the Cisco Unity server, log on to Windows by using the Cisco Unity installation account.
Step 4 Exit the Cisco Unity software.
Step 5 Browse to the CommServer\ConfigurationSetup directory.
Step 6 Double-click Setup.exe to start the Cisco Unity Message Store Configuration wizard.
Step 7 On the Welcome screen, click Next.
Step 8 Enter the password for the installation account, and click Next.
Step 9 In the Select Partner Message Store dialog box, click Microsoft Exchange 2000, and click Next.
Step 10 In the Select Mailbox Location dialog box, specify the partner Exchange server and the mailbox store in which to create new mailboxes.
Step 11 Click Next.
Step 12 In the Select Active Directory Containers for New Objects dialog box, specify the domain in which you want Cisco Unity to create users and distribution lists.
Step 13 If custom organizational units were created for users or distribution lists, click the corresponding Modify button to specify them.
Step 14 Click Next.
Step 15 Follow the on-screen prompts until message store configuration is complete.
Step 16 Repeat this procedure on any other Cisco Unity servers in the forest.
If the system is not using AMIS Networking, Cisco Unity Bridge, or SMTP Networking, skip the next procedure.
If the system is using AMIS Networking, Cisco Unity Bridge, or SMTP Networking, install the Cisco Unity Voice Connector for Microsoft Exchange 2000. The following referenced sections appear in the Cisco Unity 4.0(5) version of the Networking in Cisco Unity Guide, but they also apply to Cisco Unity 3.1.
To Install the Cisco Unity Voice Connector for Microsoft Exchange 2000 (Cisco Unity 3.1(5) Without Failover)
If you are using AMIS Networking, install the Voice Connector by using the procedure in the "Setting Up the Voice Connector for Exchange 2000" subsection in the "Procedures for Setting Up Cisco Unity to Use AMIS" section in the "AMIS Networking" chapter of the Networking in Cisco Unity Guide, Release 4.0(5) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/net/net405/ex/index.htm.
If you are using SMTP Networking, install the Voice Connector by using the procedure in the "Setting Up the Voice Connector for Exchange 2000" subsection in the "Procedures: Setting Up Cisco Unity to Use SMTP Networking" section in the "SMTP Networking" chapter of the Networking in Cisco Unity Guide, Release 4.0(5) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/net/net405/ex/index.htm.
Moving Mailboxes and Removing Exchange (Optional) (Cisco Unity 3.1(5) Without Failover)
To Move User Mailboxes from Exchange 5.5 to Exchange 2000 (Optional) (Cisco Unity 3.1(5) Without Failover)
Use Active Directory Users and Computers. Refer to the Microsoft documentation for detailed information.
To Remove Exchange 5.5 Administrator from the Cisco Unity Servers (Cisco Unity 3.1(5) Without Failover)
Step 1 Insert the Cisco Unity Message Store 2000 disc in the CD-ROM drive.
If the disc does not run automatically, browse to the root directory, and double-click Launch.exe.
Step 2 Click Change, and follow the on-screen prompts to remove Exchange 5.5 Administrator.
Step 3 Shut down and restart the Cisco Unity server.
Step 4 Repeat this procedure on any other Cisco Unity servers in the forest.
To Remove Exchange 5.5 from the Environment (Optional) (Cisco Unity 3.1(5) Without Failover)
Refer to the Microsoft documentation for information on removing Exchange 5.5 from the site, uninstalling the Exchange 5.5 server, and removing the Active Directory Connectors.
Upgrading Exchange 5.5 with Active Directory to Exchange 2000 for Cisco Unity 3.1(5) with Failover Configured (Unified Messaging)
Note If there are one or more non-failover Cisco Unity servers in the forest, see the "Upgrading Exchange 5.5 with Active Directory to Exchange 2000 for Cisco Unity 3.1(5) Without Failover (Unified Messaging)" section to upgrade those servers.
The upgrade procedures in this section were tested in a configuration that included the following elements:
•A domain controller/global catalog server.
•A Cisco Unity 3.1(5) primary server (member server).
•A Cisco Unity 3.1(5) secondary server (member server).
•An Exchange 5.5 server with Exchange 5.5 Service Pack 4 (member server).
•A separate Exchange 2000 server that was added during the upgrade.
•A two-way Active Directory Connector configured between Exchange 5.5 and Active Directory.
Caution Cisco Unity 3.x does not support Exchange 2003. To upgrade to Exchange 2003, you must first upgrade Cisco Unity to version 4.0(3) or later. With Cisco Unity 3.x, you cannot run Exchange 2003 Forestprep to begin an upgrade to Exchange 2003, you cannot have an Exchange 2003 server in the same Active Directory forest as a Cisco Unity server, and you cannot home Cisco Unity subscribers in Exchange 2003. If you run Exchange 2003 Forestprep, the changes that it makes to Active Directory will cause Cisco Unity 3.x to stop functioning.
Caution All testing was done with the old partner Exchange server, the new partner Exchange server, and the Cisco Unity server in the same Active Directory domain. Upgrading from one version of Exchange to another when the partner Exchange servers are in separate Active Directory domains has not been tested, and may fail.
The following subsections contain the instructions for upgrading a Cisco Unity 3.1(5) system with failover configured from Exchange 5.5 with Active Directory to Exchange 2000:
•Preparing for the Upgrade (Cisco Unity 3.1(5) with Failover Configured)
•Upgrading Exchange 5.5 with Active Directory to Exchange 2000 (Cisco Unity 3.1(5) with Failover Configured)
•Reconfiguring Cisco Unity (Version 3.1(5) with Failover Configured)
•Moving Mailboxes and Removing Exchange (Optional) (Cisco Unity 3.1(5) with Failover Configured)
Caution Before you begin moving mailboxes from Exchange 5.5 to Exchange 2000, you must reconfigure all Cisco Unity servers to use an Exchange 2000 server as the partner server. Otherwise, subscribers whose mailboxes are homed in Exchange 5.5 will not be able to send voice messages to subscribers whose mailboxes are homed in Exchange 2000, and vice versa.
Preparing for the Upgrade (Cisco Unity 3.1(5) with Failover Configured)
To Check the Consistency of the Cisco Unity Database on the Primary Server (Cisco Unity 3.1(5) with Failover Configured)
Step 1 On the primary server, install the latest version of the Cisco Unity Directory Walker (DbWalker) utility, available at http://ciscounitytools.com/App_DirectoryWalker3.htm.
Step 2 Run DbWalker, and correct all errors that the utility finds. Refer to DbWalker Help for detailed instructions on running the utility and on correcting errors in the database. (The Help file, DbWalker.htm, is in the same directory as DbWalker.exe.)
To Back Up Cisco Unity Data on the Secondary Server (Cisco Unity 3.1(5) with Failover Configured)
Step 1 On the secondary server, install the latest versions of the Cisco Unity Disaster Recovery tools (DiRT), available at http://ciscounitytools.com/App_DisasterRecoveryTools.htm.
Step 2 Back up Cisco Unity data by using the Disaster Recovery Backup tool. Refer to DiRT Help for detailed instructions. (The Help file, UnityDisasterRecovery.htm, is in the same directory as UnityDisasterRecoveryBackup.exe.)
Caution Follow Help carefully. DiRT includes a variety of options that you must understand to use the tools successfully. In addition, the account you are logged on as when you back up Cisco Unity data must have sufficient permissions or the backup will fail.
Caution Cisco does not support downgrading from Exchange 2003 or Exchange 2000 to Exchange 5.5. If the upgrade fails and you want to revert to Exchange 5.5, you must restore Cisco Unity data from a DiRT backup. Without the backup, you will not be able to restore Cisco Unity data and have Cisco Unity function properly with Exchange 5.5.
Upgrading Exchange 5.5 with Active Directory to Exchange 2000 (Cisco Unity 3.1(5) with Failover Configured)
If the system is not using Cisco Unity networking to connect multiple Cisco Unity servers or to allow Cisco Unity to communicate with another voice messaging system, skip the next procedure.
Do the next procedure to uninstall the Cisco Unity Voice Connector for Microsoft Exchange 5.5 only if you are using Cisco Unity networking and you are upgrading existing Exchange 5.5 servers to Exchange 2000.
Caution After you uninstall the Voice Connector, Cisco Unity networking stops functioning.
If you are installing Exchange 2000 on new servers instead of upgrading existing Exchange 5.5 servers, you can wait to uninstall the Voice Connector until later in the process.
To Uninstall the Voice Connector for Exchange 5.5 (Cisco Unity 3.1(5) with Failover Configured)
Step 1 Log on to the Exchange server on which the Voice Connector is installed.
Step 2 On the Windows Start menu, click Control Panel > Settings > Add/Remove Programs.
Step 3 Select the Voice Connector.
Step 4 Follow the on-screen prompts to uninstall the Voice Connector.
To Set Up a Mixed-Messaging Environment (Cisco Unity 3.1(5) with Failover Configured)
Step 1 Set up a mixed-messaging environment according to Microsoft recommendations. Note the following considerations:
•The Exchange 2000 servers must be installed into one of the existing Exchange 5.5 sites.
•The Exchange version of the Active Directory connector must be installed.
•A recipient connection agreement must be set up to replicate data between the Exchange 5.5 directory and Active Directory. (An Exchange organization that has multiple sites will have multiple Active Directory connectors and multiple connection agreements.) If you want to be able to use the Cisco Unity Administrator to add Cisco Unity subscribers who will be homed in Exchange 5.5, on the Advanced tab of the Properties dialog box for this connection agreement, you must check the This Is a Primary Connection Agreement for the Connected Exchange Organization check box.
Caution Do not make any Exchange 5.5 servers into domain controller/global catalog servers. Doing so during a migration to Exchange 2000 is not supported by Microsoft, and Cisco Unity will not function properly in such a configuration.
Step 2 Install the current Exchange service pack and updates recommended for use with Cisco Unity on the following servers:
•On every Exchange 2000 server on which Cisco Unity subscribers will be homed.
•On the partner Exchange server.
•On the Exchange server on which the Voice Connector, if any, is installed.
For a list of required and recommended service packs, refer to Recommended Service Packs and Updates for Use with Cisco Unity and the Cisco Unity Bridge at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/cmptblty/msupdate.htm.
If the system is not using Cisco Unity networking, skip the next procedure.
Do the next procedure only if the system is using Cisco Unity networking and you have not yet uninstalled the Cisco Unity Voice Connector for Microsoft Exchange 5.5.
Caution After you uninstall the Voice Connector, Cisco Unity networking stops functioning.
To Uninstall the Voice Connector for Exchange 5.5 (Cisco Unity 3.1(5) with Failover Configured)
Step 1 Log on to the Exchange server on which the Voice Connector is installed.
Step 2 On the Windows Start menu, click Control Panel > Settings > Add/Remove Programs.
Step 3 Select the Voice Connector.
Step 4 Follow the on-screen prompts to uninstall the Voice Connector.
With Exchange 2000, several changes need to be made to the Active Directory schema for Cisco Unity to work properly. To see the changes that the schema update program makes, browse to the directory Schema\LdifScripts on Cisco Unity CD 1, and view the file Avdirmonex2k.ldf.
Additional changes to the schema are required if you are setting up a Cisco Unity Bridge. To see the changes that the schema update program makes for the Bridge, view the file Omnigateway.ldf.
To update the schema, use either the next procedure or any tool that applies LDIF scripts (for example, the Microsoft Ldifde utility).
You need to update the schema only once, regardless of how many Cisco Unity servers there are in the Active Directory forest. (For failover and for Cisco Unity Digital Networking, all servers must be in the same forest, so they use the same Active Directory schema.)
To Extend the Active Directory Schema (Cisco Unity 3.1(5) with Failover Configured)
Step 1 Confirm that all domain controllers are on line before making the schema updates. Schema replication will occur only when all domain controllers are on line.
Step 2 On the domain controller that is the schema master, log on by using an account that is a member of the Schema Administrators group.
Step 3 On Cisco Unity DVD 1 or CD 1, or from the location to which you saved the downloaded Cisco Unity CD 1 image files, browse to the directory ADSchemaSetup, and double-click ADSchemaSetup.exe.
Step 4 In the dialog box, double-click a row to choose the language in which you will view ADSchemaSetup.
Step 5 In the Active Directory Schema Setup dialog box, check the Exchange 2000 Directory Monitor check box.
If you plan to use Cisco Unity Bridge Networking, check the Exchange 2000 Bridge Connector check box.
Step 6 When the LDAP Data Interchange Format (LDIF) scripts have finished running, click OK.
Step 7 When the schema extension has finished, Ldif.log and LDif.err files are saved to the desktop. View the contents of the files to confirm that the extension completed successfully.
Step 8 Wait for the changes to the schema to replicate throughout the forest before adding information to the primary location and to delivery locations. Changes to the schema may take 15 minutes or more to replicate.
Note To determine whether changes have replicated and to force replication if necessary, use the Replication Monitor, which is available when you install Support Tools from the Windows 2000 compact disc.
Reconfiguring Cisco Unity (Version 3.1(5) with Failover Configured)
To Disable Automatic Failover, and Stop File and SQL Replication (Cisco Unity 3.1(5) with Failover Configured)
Step 1 If the primary server is active, skip to Step 5.
If the primary server is not active, on the Windows Start menu on the secondary server, click Programs > Cisco Unity >Failover Monitor.
Step 2 Click Failback.
Step 3 Click OK to confirm that you want to fail back to the primary server.
Step 4 Close the Failover Monitor.
Step 5 On the primary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.
Step 6 Click Advanced.
Step 7 Check the Disable Automatic Failover and Failback check box.
Step 8 Click OK, and close the Failover Monitor.
Step 9 On the primary server, on the Windows Start menu, click Programs > Administrative Tools > Services.
Step 10 In the right pane, double-click AvCsNodeMgr.
Step 11 On the General tab, click Stop.
Step 12 In the Startup Type list, click Disabled.
Step 13 Click OK.
Step 14 Close the Services window.
Caution Because the Node Manager service is disabled, file replication stops. Replication is re-enabled when normal failover operation resumes.
Step 15 On the secondary server, on the Windows Start menu, click Programs > Administrative Tools > Services.
Step 16 In the right pane, double-click AvCsNodeMgr.
Step 17 On the General tab, click Stop.
Step 18 In the Startup Type list, click Disabled.
Step 19 Click OK.
Step 20 Close the Services window.
Step 21 On the primary server, on the Windows Start menu, click Programs > Microsoft SQL Server > Enterprise Manager.
Step 22 In the left pane of the Console Root window, browse to the Replication node for the primary server. Typically, the node is three levels under the Microsoft SQL Servers node.
Step 23 Right-click the Replication node, and click Disable Publishing. The Disable Publishing and Distribution wizard appears.
Step 24 On the Welcome page, click Next.
Step 25 On the Disable Publishing page, click Yes, then click Next.
Step 26 On the Confirm Dropping of Publications page, click Next.
Step 27 On the Completing page, click Finish.
Step 28 When the process is completed, click OK.
Step 29 Close the Console Root window.
Step 30 Exit Enterprise Manager.
To Remove the Current Message Store Configuration from the Secondary Server (Cisco Unity 3.1(5) with Failover Configured)
Step 1 On the secondary Cisco Unity server, log on to Windows by using the Cisco Unity installation account.
Step 2 Exit the Cisco Unity software.
Step 3 On the Windows Start menu, click Settings > Control Panel > Add/Remove Programs.
Step 4 Click Cisco Unity Message Store Configuration Wizard.
Step 5 Click Change/Remove.
Step 6 Follow the on-screen prompts to remove the message store configuration.
Even when Exchange is not installed on the Cisco Unity server, Exchange administration software is required because it includes the Microsoft messaging API (MAPI), the application programming interface that Cisco Unity uses to communicate with Exchange for addressing, sending, and retrieving messages.
To Install Exchange 2000 System Manager on the Secondary Server (Cisco Unity 3.1(5) with Failover Configured)
Step 1 On the secondary server, log on to Windows by using the Cisco Unity installation account.
Step 2 Insert the Cisco Unity Message Store 2000 disc in the CD-ROM drive.
If the disc does not run automatically, browse to the root directory, and double-click Launch.exe.
Step 3 Click Exchange Server Setup.
Step 4 Follow the on-screen prompts until you are prompted to choose between installing Exchange 2000 System Manager and upgrading. Choose to upgrade.
Step 5 When you are asked whether to replace a target file that is newer than the source file, click No to All.
Step 6 Install the current Exchange service pack and updates recommended for use with Cisco Unity.
For a list of required and recommended service packs, refer to Recommended Service Packs and Updates for Use with Cisco Unity and the Cisco Unity Bridge at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/cmptblty/msupdate.htm.
Step 7 Shut down and restart the Cisco Unity server.
To Create Accounts and Set Rights and Permissions (Cisco Unity 3.1(5) with Failover Configured)
If you have not done so already, create accounts and set rights and permissions as described in the following sections in the "Installing the Cisco Unity System" chapter of the Cisco Unity installation guide, Release 3.1:
•"About the Accounts Required for the Cisco Unity Installation"
•"Creating the Accounts"
•"Adding the Cisco Unity Administration Account to an Admins Group"
•"Setting Rights and Permissions with the Cisco Unity Permissions Wizard"
•"Setting Exchange Permissions"
This guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/inst/inst31/index.htm.
Note the following considerations:
•You can use the same accounts for every Cisco Unity server in the forest. (For example, you create only one installation account, not one installation account for every Cisco Unity server.)
•Some of the permissions that the Cisco Unity Permissions wizard sets are server specific, so you must run the Permissions wizard on every Cisco Unity server in the forest. In failover configurations, this includes both the primary and secondary servers.
•If you use the same accounts for every Cisco Unity server in the forest, you set Exchange permissions only once for the entire forest.
If you do not use the same accounts for every Cisco Unity server in the forest, you must run the Permissions wizard and set Exchange permissions on each of the accounts as required.
To Configure the Secondary Server for Exchange 2000 (Cisco Unity 3.1(5) with Failover Configured)
Step 1 Choose the new partner Exchange server. See the "Choosing a Different Partner Exchange Server" section on page 6-1.
Step 2 Confirm that Exchange is running on the new partner Exchange server. If Exchange is not running, configuring Cisco Unity for Exchange will fail.
Step 3 On the secondary server, log on to Windows by using the Cisco Unity installation account.
Step 4 Exit the Cisco Unity software.
Step 5 Browse to the CommServer\ConfigurationSetup directory.
Step 6 Double-click Setup.exe to start the Cisco Unity Message Store Configuration wizard.
Step 7 On the Welcome screen, click Next.
Step 8 Enter the password for the installation account, and click Next.
Step 9 In the Select Partner Message Store dialog box, click Microsoft Exchange 2000, and click Next.
Step 10 In the Select Mailbox Location dialog box, specify the partner Exchange server and the mailbox store in which to create new mailboxes.
Step 11 Click Next.
Step 12 In the Select Active Directory Containers for New Objects dialog box, specify the domain in which you want Cisco Unity to create users and distribution lists.
Step 13 If custom organizational units were created for users or distribution lists, click the corresponding Modify button to specify them.
Step 14 Click Next.
Step 15 Follow the on-screen prompts until message store configuration is complete.
To Remove the Current Message Store Configuration from the Primary Server (Cisco Unity 3.1(5) with Failover Configured)
Step 1 On the primary server, log on to Windows by using the Cisco Unity installation account.
Step 2 Exit the Cisco Unity software.
Step 3 On the Windows Start menu, click Settings > Control Panel > Add/Remove Programs.
Step 4 Click Cisco Unity Message Store Configuration Wizard.
Step 5 Click Change/Remove.
Step 6 Follow the on-screen prompts to remove the message store configuration.
Even when Exchange is not installed on the Cisco Unity server, Exchange administration software is required because it includes the Microsoft messaging API (MAPI), the application programming interface that Cisco Unity uses to communicate with Exchange for addressing, sending, and retrieving messages.
To Install Exchange 2000 System Manager on the Primary Server (Cisco Unity 3.1(5) with Failover Configured)
Step 1 On the primary server, log on to Windows by using the Cisco Unity installation account.
Step 2 Insert the Cisco Unity Message Store 2000 disc in the CD-ROM drive.
If the disc does not run automatically, browse to the root directory, and double-click Launch.exe.
Step 3 Click Exchange Server Setup.
Step 4 Follow the on-screen prompts until you are prompted to choose between installing Exchange 2000 System Manager and upgrading. Choose to upgrade.
Step 5 When you are asked whether to replace a target file that is newer than the source file, click No to All.
Step 6 Install the current Exchange service pack and updates recommended for use with Cisco Unity.
For a list of required and recommended service packs, refer to Recommended Service Packs and Updates for Use with Cisco Unity and the Cisco Unity Bridge at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/cmptblty/msupdate.htm.
Step 7 Shut down and restart the Cisco Unity server.
To Configure the Primary Server for Exchange 2000 (Cisco Unity 3.1(5) with Failover Configured)
Step 1 Confirm that Exchange is running on the new partner Exchange server. If Exchange is not running, configuring Cisco Unity for Exchange will fail.
Step 2 On the primary server, log on to Windows by using the Cisco Unity installation account.
Step 3 Exit the Cisco Unity software.
Step 4 Browse to the CommServer\ConfigurationSetup directory.
Step 5 Double-click Setup.exe to start the Cisco Unity Message Store Configuration wizard.
Step 6 On the Welcome screen, click Next.
Step 7 Enter the password for the installation account, and click Next.
Step 8 In the Select Partner Message Store dialog box, click Microsoft Exchange 2000, and click Next.
Step 9 In the Select Mailbox Location dialog box, specify the partner Exchange server and the mailbox store in which to create new mailboxes.
Specify the same partner Exchange server that you specified when you configured the secondary server for Exchange.
Step 10 Click Next.
Step 11 In the Select Active Directory Containers for New Objects dialog box, specify the domain in which you want Cisco Unity to create users and distribution lists.
Step 12 If custom organizational units were created for users or distribution lists, click the corresponding Modify button to specify them.
Step 13 Click Next.
Step 14 Follow the on-screen prompts until message store configuration is complete.
To Configure Failover on the Primary Server (Cisco Unity 3.1(5) with Failover Configured)
Step 1 In Windows Explorer, browse to the directory where Cisco Unity is installed (the default directory is CommServer).
Step 2 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.
Step 3 Click Next.
Step 4 Click Browse, select the name of the secondary server, and click OK. The IP address for the secondary server is filled in automatically.
Step 5 If the system is running Cisco Unity 3.1(2), skip to Step 6.
If the system is running Cisco Unity 3.1(3) or later and you want the switch file for the selected phone system to replicate during the wizard, check the Copy Switch Files from Primary Server to Secondary Server check box.
Note The switch file is replicated only during the failover configuration wizard. If you select a different phone system after you run the wizard, the new switch file is not replicated to the secondary server. In addition, changes to phone system settings are not replicated between the primary and secondary servers. If you change phone system settings after you run the failover configuration wizard, you must manually change values on both servers.
Step 6 Click Next.
Step 7 If you did not create a Cisco Unity failover account, skip to Step 8.
If you created a Cisco Unity failover account, click Browse, and double-click the name of the account.
Caution You must specify the same account on both the primary and secondary servers.
Step 8 Enter the password for the account that the failover service will log on as.
Step 9 Click Next.
Step 10 Click Configure. The wizard verifies settings and configures failover on the primary server.
If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and click Configure again.
Step 11 On the Completing page, click Finish.
Step 12 Exit and restart the Cisco Unity software.
To Configure Failover on the Secondary Server (Cisco Unity 3.1(5) with Failover Configured)
Step 1 In Windows Explorer, browse to the directory where Cisco Unity is installed (the default directory is CommServer).
Step 2 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.
Step 3 Click Next.
Step 4 Click Browse, select the name of the primary server, and click OK. The IP address for the primary server is filled in automatically.
Step 5 If the system is running Cisco Unity 3.1(2), skip to Step 6.
If the system is running Cisco Unity 3.1(3) or later, and you want the switch file for the selected phone system to replicate during the wizard, check the Copy Switch Files from Primary Server to Secondary Server check box.
Note The switch file is replicated only during the failover configuration wizard. If you select a different phone system after you run the wizard, the new switch file is not replicated to the secondary server. In addition, changes to phone system settings are not replicated between the primary and secondary servers. If you change phone system settings after you run the failover configuration wizard, you must manually change values on both servers.
Step 6 Click Next.
Step 7 If you did not create a Cisco Unity failover account, skip to Step 8.
If you created a Cisco Unity failover account, click Browse, and double-click the name of the account.
Caution You must specify the same account on both the primary and secondary servers.
Step 8 Enter the password for the account that the failover service will log on as.
Step 9 Click Next.
Step 10 Click Configure. The wizard verifies settings and configures failover on the secondary server.
If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and click Configure again.
Step 11 On the Completing page, click Finish.
Step 12 Exit and restart the Cisco Unity software.
If the system is not using AMIS Networking, Cisco Unity Bridge, or SMTP Networking, skip the next procedure.
If the system is using AMIS Networking, Cisco Unity Bridge, or SMTP Networking, install the Cisco Unity Voice Connector for Microsoft Exchange 2000. The following referenced sections appear in the Cisco Unity 4.0(5) version of the Networking in Cisco Unity Guide, by they also apply to Cisco Unity 3.1.
To Install the Cisco Unity Voice Connector for Microsoft Exchange 2000 (Cisco Unity 3.1(5) with Failover Configured)
If you are using AMIS Networking, install the Voice Connector by using the procedure in the "Setting Up the Voice Connector for Exchange 2000" subsection in the "Procedures for Setting Up Cisco Unity to Use AMIS" section in the "AMIS Networking" chapter of the Networking in Cisco Unity Guide, Release 4.0(5) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/net/net405/ex/index.htm.
If you are using SMTP Networking, install the Voice Connector by using the procedure in the "Setting Up the Voice Connector for Exchange 2000" subsection in the "Procedures: Setting Up Cisco Unity to Use SMTP Networking" section in the "SMTP Networking" chapter of the Networking in Cisco Unity Guide, Release 4.0(5) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/net/net405/ex/index.htm.
Moving Mailboxes and Removing Exchange (Optional) (Cisco Unity 3.1(5) with Failover Configured)
To Move User Mailboxes from Exchange 5.5 to Exchange 2000 (Optional) (Cisco Unity 3.1(5) with Failover Configured)
Use Active Directory Users and Computers. Refer to the Microsoft documentation for detailed information.
To Remove Exchange 5.5 Administrator from the Cisco Unity Servers (Optional) (Cisco Unity 3.1(5) with Failover Configured)
Step 1 On the secondary server, exit the Cisco Unity software.
Step 2 Insert the Cisco Unity Message Store 2000 disc in the CD-ROM drive.
If the disc does not run automatically, browse to the root directory, and double-click Launch.exe.
Step 3 Click Change, and follow the on-screen prompts to remove Exchange 5.5 Administrator.
Step 4 Shut down and restart the secondary server.
Step 5 On the primary server, manually initiate failover to the secondary server. For detailed instructions, refer to the applicable version of the Cisco Unity Failover Configuration and Administration Guide:
•For Cisco Unity 4.x, refer to the "Manually Initiating Failover or Failback" section in the "Monitoring and Maintaining Cisco Unity Failover" chapter of the guide at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/fail/fail401/ex/index.htm.
•For Cisco Unity 3.1, refer to the "Manually Failing Over or Failing Back" section in the "Maintaining Cisco Unity Failover" chapter of the guide at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/fail/fail31/index.htm.
Step 6 Repeat Step 1 through Step 4 on the primary server.
Step 7 On the secondary server, manually initiate failback to the primary server.
To Remove Exchange 5.5 from the Environment (Optional) (Cisco Unity 3.1(5) with Failover Configured)
Refer to the Microsoft documentation for information on removing Exchange 5.5 from the site, uninstalling the Exchange 5.5 server, and removing the Active Directory Connectors.
Upgrading Exchange 5.5 to Exchange 2003 or Exchange 2000 for Cisco Unity Without Failover (Voice Messaging)
Do the procedure in this section to upgrade from Exchange 5.5 to Exchange 2003 or Exchange 2000.
If the current version of Cisco Unity is 2.x, do the procedures in the "Upgrading a Cisco Unity 2.x System to the Shipping Version" chapter instead. The procedures in that chapter give you the opportunity to upgrade to Exchange 2003 or Exchange 2000.
Caution Do not use the procedure in this section if Cisco Unity is configured as Unified Messaging, or the upgrade will fail. Instead, use the procedures in the applicable Unified Messaging section elsewhere in this chapter.
Caution The procedure in this section only works if you simultaneously upgrade all Exchange servers in the Exchange organization and reinstall all software on all Cisco Unity servers. Cisco Unity will not function properly until you have finished the entire procedure. If you want to upgrade in stages, you must use the procedures in the applicable Unified Messaging section elsewhere in this chapter.
Caution When you reinstall software, you must install the exact version of Cisco Unity that was installed when you backed up the server. The Disaster Recovery Restore tool can restore data only to the exact version of Cisco Unity that was backed up.
Caution Do the procedure only if the Cisco Unity server is the only server in the domain or if it is a member server. If the Cisco Unity server is the domain controller and it is not the only server in the domain, refer to Microsoft documentation for information on installing Active Directory on another server in the domain, transferring roles from the Cisco Unity server to the new domain controller, and other applicable tasks before you rename the Cisco Unity server or move it to another domain.
To Upgrade from Exchange 5.5 to Exchange 2003 or Exchange 2000 for Cisco Unity (Without Failover)
Step 1 If Cisco Unity is at version 3.0(x), use the procedures in the "Upgrading Cisco Unity 3.x Software to the Shipping Version" chapter to upgrade to Cisco Unity 4.0(5), then return to this procedure. Cisco Unity 4.0(5) software is available at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-40.
While you are upgrading to Cisco Unity 4.0(5), skip the "Extending the Active Directory Schema for Cisco Unity" section. You cannot extend the Active Directory schema until Exchange 2003 or Exchange 2000 has been installed.
You must upgrade Cisco Unity from version 3.0(x) because you need the Cisco Unity Disaster Recovery tools (DiRT) to upgrade from Exchange 5.5, and DiRT is only available only for Cisco Unity 3.1(1) and later. Do not try to upgrade to Cisco Unity 4.2(1) or later; Cisco Unity 4.2(1) Setup fails when Exchange 5.5 is the message store.
Note You can also upgrade to Cisco Unity 4.1(1), but version 4.1(1) is only available in U.S. English.
Step 2 Recommend that the customer have users reduce the number of voice messages in their inbox as much as possible, especially voice messages to distribution lists.
The Disaster Recovery Backup tool backs up messages using the Microsoft Exchange ExMerge utility, and ExMerge does not retain single-instance messaging. (In single-instance messaging, when you send a message to a distribution list, only one copy is saved in the Exchange database, not one copy per recipient.) When you back up using ExMerge, for every message sent to a distribution list, ExMerge saves one copy of that message for every recipient. As a result, the backup of the messages database may be so large that you cannot restore the entire database to the Cisco Unity server.
Step 3 Confirm that you have all of the disks necessary to reinstall the version of Cisco Unity currently installed on the Cisco Unity server. When you use DiRT to back up and restore Cisco Unity data, you must restore to the same version of Cisco Unity that you backed up.
Step 4 Download the latest versions of the following applications to a network drive:
•The Cisco Unity Directory Walker (DbWalker) utility. The version for Cisco Unity 4.x is available at http://ciscounitytools.com/App_DirectoryWalker4.htm. The version for Cisco Unity 3.1(x) is available at http://ciscounitytools.com/App_DirectoryWalker3.htm.
•The Cisco Unity Disaster Recovery Backup tool and Disaster Recovery Restore tool, available at http://ciscounitytools.com/App_DisasterRecoveryTools.htm.
Step 5 On all Cisco Unity servers, install the versions of DbWalker and the Disaster Recovery Backup tool that you downloaded in Step 4.
Note Do not install the Disaster Recovery Restore tool now. When you reinstall the operating system, you delete all partitions, which deletes all data and applications.
Step 6 Run DbWalker, and correct all errors that the utility finds. Refer to DbWalker Help for detailed instructions on running the utility and on correcting errors in the database. (The Help file, DbWalker.htm, is in the same directory as DbWalker.exe.)
Step 7 On all Cisco Unity servers, back up Cisco Unity data and voice messages by using the Disaster Recovery Backup tool. Refer to DiRT Help for detailed instructions. (The Help file, UnityDisasterRecovery.htm, is in the same directory as UnityDisasterRecoveryBackup.exe.)
Caution Follow Help carefully. DiRT includes a variety of options that you must understand to use the tools successfully. In addition, the account you are logged on as when you back up Cisco Unity data must have sufficient permissions or the backup will fail.
Caution Choose the option to back up voice messages, or all voice messages will be lost. In
Step 8, you reinstall all software on all Cisco Unity servers and on all Exchange servers that are used as message stores for Cisco Unity voice messages, if any. Reinstalling all software will delete all applications and data on those servers.
Step 8 Reinstall all software, including the operating system, on:
•All Cisco Unity servers
•If Cisco Unity voice messages are stored on separate Exchange servers, all Exchange servers.
Caution This procedure is intended only for use with the Cisco Unity Voice Messaging configuration. Do not reinstall software on Exchange servers where e-mail, faxes, or other messages are stored.
Follow the instructions in the applicable Cisco Unity installation guide for your configuration at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
Caution You must install the same version of Cisco Unity that was previously installed. Otherwise, the Disaster Recovery Restore tool cannot restore the data that you backed up earlier in this procedure.
Note the following:
•If you use a retail Windows disk to install Windows, delete and recreate all partitions to ensure that old applications and data are deleted.
•When you configure Windows, if there is more than one Cisco Unity server in the Active Directory forest, give each Cisco Unity server a name that is unique in the first 14 characters, or Cisco Unity will have problems communicating with the Active Directory accounts created by Cisco Unity. For example, the following names would cause communication problems: CiscoUnitySrvr1 and CiscoUnitySrvr2.
•If you are not replacing the phone system, you can skip the task on setting up or programming the phone system.
•If you are not replacing the Cisco Unity server, you can skip the task on setting up the Cisco Unity server.
•On each Cisco Unity server, install the same version of Cisco Unity that was running when you backed up Cisco Unity data. DiRT Restore can only restore data to the same version of Cisco Unity that you backed up.
•If you are installing Cisco Unity 4.2(1) or later, and if you are making the Cisco Unity server a member server in an existing domain, add the server to a Windows 2000 Server domain or Windows Server 2003 domain. Beginning with Cisco Unity 4.2(1), adding the Cisco Unity server to a Windows NT domain is not supported.
•When you reinstall Exchange, install Exchange Server 2003 or Exchange 2000 Server.
Step 9 On each Cisco Unity server, install the version of the Disaster Recovery Restore tool that you downloaded in Step 4.
Step 10 On each Cisco Unity server, restore Cisco Unity data and Exchange voice messages by using the Disaster Recovery Restore tool and the backup that you made earlier. Refer to DiRT Help for detailed instructions. (The Help file, UnityDisasterRecovery.htm, is in the same directory as UnityDisasterRecoveryRestore.exe.)
Caution Follow Help carefully. DiRT includes a variety of options that you must understand to use the tools successfully.
Step 11 Reapply any non-Cisco Unity custom registry settings. (DiRT backs up and restores Cisco Unity registry settings.)
Upgrading Exchange 5.5 to Exchange 2003 or Exchange 2000 for Cisco Unity With Failover Configured (Voice Messaging)
Do the 11 procedures in this section in the order listed to upgrade from Exchange 5.5 to Exchange 2003 or Exchange 2000 when the Cisco Unity system is configured for failover. When you configure failover on the primary and secondary servers, there are two procedures for each server: one for a server running Cisco Unity version 4.x and one for a server running version 3.1(x). Do the applicable procedure for your version.
Note that Exchange Server 2003 is supported as the message store in a Voice Messaging configuration only with Cisco Unity 4.0(5) and later.
Caution Do not use the procedures in this section if Cisco Unity is configured as Unified Messaging, or the upgrade will fail. Instead, use the procedures in the applicable Unified Messaging section elsewhere in this chapter.
Caution The procedures in this section work only if you simultaneously upgrade all Exchange servers in the Exchange organization and reinstall all software on all primary and secondary Cisco Unity servers. Cisco Unity will not function properly until you have finished all procedures. If you want to upgrade in stages, you must use the procedures in the applicable Unified Messaging section elsewhere in this chapter.
Caution When you reinstall software, you must install the exact version of Cisco Unity that was installed when you backed up the server. The Disaster Recovery Restore tool can restore data only to the exact version of Cisco Unity that was backed up.
To Prepare for the Upgrade
Step 1 If Cisco Unity is at version 3.1(x) or later, skip to Step 2.
If Cisco Unity is at version 3.0(x), use the procedures in the "Upgrading Cisco Unity 3.x Software to the Shipping Version" chapter to upgrade to Cisco Unity 4.0(5), then return to this procedure. Cisco Unity 4.0(5) software is available at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-40. (You can also upgrade to Cisco Unity 4.1(1), but version 4.1(1) is available only in U.S. English.)
While you are upgrading to Cisco Unity 4.0(5), skip the "Extending the Active Directory Schema for Cisco Unity" section. You cannot extend the Active Directory schema until Exchange 2003 or Exchange 2000 has been installed.
You must upgrade Cisco Unity from version 3.0(x) because you need the Cisco Unity Disaster Recovery tools (DiRT) to upgrade from Exchange 5.5, and DiRT is available only for Cisco Unity 3.1(1) and later.
Caution Do not try to upgrade to Cisco Unity 4.2(1) or later; Cisco Unity 4.2(1) Setup fails when Exchange 5.5 is the message store.
Step 2 Recommend that the customer have users reduce the number of voice messages in their inboxes as much as possible, especially voice messages to distribution lists.
The Disaster Recovery Backup tool backs up messages by using the Microsoft Exchange ExMerge utility, and ExMerge does not retain single-instance messaging. (In single-instance messaging, when you send a message to a distribution list, only one copy is saved in the Exchange database, not one copy per recipient.) When you back up using ExMerge, for every message sent to a distribution list, ExMerge saves one copy of that message for every recipient. As a result, the backup of the messages database may be so large that you cannot restore the entire database to the Cisco Unity server.
Step 3 Confirm that you have the following software and documentation:
•Software for reinstalling the primary and secondary Cisco Unity servers (must be the same versions installed on both servers).
•The applicable Cisco Unity installation guide for your configuration, available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
Step 4 Download the latest versions of the following applications to a network drive:
•The Cisco Unity Directory Walker (DbWalker) utility. The version for Cisco Unity 4.x is available at http://ciscounitytools.com/App_DirectoryWalker4.htm. The version for Cisco Unity 3.1(x) is available at http://ciscounitytools.com/App_DirectoryWalker3.htm.
•The Cisco Unity Disaster Recovery Backup tool and Disaster Recovery Restore tool, available at http://ciscounitytools.com/App_DisasterRecoveryTools.htm.
To Manually Initiate Failover to the Secondary Server and Disable Automatic Failback
Step 1 If the primary server is not active, skip to Step 4.
If the primary server is active, on the primary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.
Step 2 Click Failover.
Step 3 Click OK to confirm that you want to fail over to the secondary server. The primary server becomes inactive, and the secondary server becomes active.
Step 4 On the secondary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.
Step 5 Click Configure.
Step 6 In the Failback Type field of the Failover Configuration dialog box, click Manual.
Step 7 Click OK to close the Failover Configuration dialog box.
To Stop File Replication on the Secondary and Primary Servers
Step 1 On the secondary server, on the Windows Start menu, click Programs > Administrative Tools > Services.
Step 2 In the right pane, double-click AvCsNodeMgr.
Step 3 On the General tab, click Stop.
Step 4 In the Startup Type list, click Disabled.
Step 5 Click OK.
Step 6 Close the Services window.
Caution Because the Node Manager service is disabled, file replication stops. Replication is re-enabled when normal failover operation resumes.
Step 7 On the primary server, on the Windows Start menu, click Programs > Administrative Tools > Services.
Step 8 In the right pane, double-click AvCsNodeMgr.
Step 9 On the General tab, click Stop.
Step 10 In the Startup Type list, click Disabled.
Step 11 Click OK.
Step 12 Close the Services window.
To Stop SQL Replication on the Primary Server
Step 1 On the primary server, on the Windows Start menu, click Programs > Microsoft SQL Server > Enterprise Manager.
Step 2 In the left pane of the Console Root window, browse to the Replication node for the primary server. Typically, the node is three levels under the Microsoft SQL Servers node.
Step 3 Right-click the Replication node, and click Disable Publishing. The Disable Publishing and Distribution wizard appears.
Step 4 On the Welcome page, click Next.
Step 5 On the Disable Publishing page, click Yes, then click Next.
Step 6 On the Confirm Dropping of Publications page, click Next.
Step 7 On the Completing page, click Finish.
Step 8 When the process is completed, click OK.
Step 9 Close the Console Root window.
Step 10 Exit Enterprise Manager.
To Check the Consistency of the Cisco Unity Database on the Secondary Server
Step 1 On the secondary server, install the latest version of DbWalker, if it is not already installed.
Step 2 Run DbWalker, and correct all errors that the utility finds. Refer to DbWalker Help for detailed instructions on running the utility and on correcting errors in the database. (The Help file, DbWalker.htm, is in the same directory as DbWalker.exe.)
To Back Up Cisco Unity Data on the Secondary Server to a Network Storage Location
Step 1 On the secondary server, install the latest version of the Disaster Recovery Backup tool, if it is not already installed.
Step 2 Back up Cisco Unity data by using the Disaster Recovery Backup tool. Refer to DiRT Help for detailed instructions. (The DiRT Help file, UnityDisasterRecovery.htm, is in the same directory as UnityDisasterRecoveryBackup.exe.)
Caution Follow Help carefully. DiRT includes a variety of options that you must understand to use the tools successfully. In addition, the account you are logged on as when you back up Cisco Unity data must have sufficient permissions or the backup will fail.
Caution Choose the option to back up voice messages, or all voice messages will be lost. Later in this section, you reinstall all software on all Cisco Unity servers and on all Exchange servers that are used as message stores for Cisco Unity voice messages, if any. Reinstalling all software will delete all applications and data on those servers.
Step 3 Save the Cisco Unity data to a network storage location.
To Remove the Primary and Secondary Servers from the Environment
Step 1 On the primary server, log on to Windows as a Cisco Unity administrator.
Step 2 Right-click the Cisco Unity icon in the status area of the taskbar.
(If the Cisco Unity icon is not in the taskbar, browse to the CommServer directory and double-click AvCsTrayStatus.exe.)
Step 3 Click Stop Cisco Unity. Cisco Unity stops running when all calls are finished, and an "X" appears in the Cisco Unity icon.
Step 4 Right-click the SQL Server icon in the status area of the taskbar.
Step 5 Click MSSQLServer - Stop.
Step 6 Disconnect the network cable from the primary server.
Step 7 On the secondary server, repeat Step 1 through Step 6.
Step 8 Remove the computer accounts from the domain, depending on the operating system:
Windows 2003
|
Remove the primary and secondary servers from Active Directory Users and Computers.
|
Windows 2000
|
Remove the primary and secondary servers from Active Directory Users and Computers.
|
Windows NT
|
Remove the primary and secondary servers from the primary domain controller.
|
To Reinstall All Software on the Primary, Secondary, and Exchange Servers
Step 1 Reinstall all software, including the operating system, on all Exchange servers on which mailboxes for Cisco Unity subscribers are homed. When you reinstall Exchange, install Exchange Server 2003 or Exchange 2000 Server.
Caution This procedure is intended for use only with the Cisco Unity Voice Messaging configuration. Do not reinstall software on Exchange servers where e-mail, faxes, or other messages are stored.
Step 2 Follow the instructions in the applicable Cisco Unity installation guide for your configuration to reinstall all software on the primary and secondary Cisco Unity servers:
•For Cisco Unity 4.x, refer to "Part 1: Installing and Configuring the Cisco Unity Server" and "Part 2: Installing the Secondary Server for Cisco Unity Failover" in the "Overview of Mandatory Tasks for Installing Cisco Unity" chapter.
•For Cisco Unity 3.1(x), refer to "Part 1: Installing and Configuring the Cisco Unity Server" in the "Overview of Mandatory Tasks for Installing Cisco Unity" chapter.
Cisco Unity installation guides are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
Note the following considerations:
•If you use a retail Windows disc to install Windows, delete and recreate all partitions to ensure that old applications and data are deleted.
•When you configure Windows, give each Cisco Unity server a name that is unique in the first 14 characters, or Cisco Unity will have problems communicating with the Active Directory accounts created by Cisco Unity. (For example, the following names would cause communication problems: CiscoUnitySrvr1 and CiscoUnitySrvr2.)
•If you are not replacing the phone system, you can skip the task on setting up or programming the phone system.
•If you are not replacing the Cisco Unity servers, you can skip the task on setting up the server.
•On the primary and secondary Cisco Unity servers, install the same version of Cisco Unity that was running when you backed up Cisco Unity data. DiRT Restore can restore data only to the same version of Cisco Unity that you backed up.
To Restore Cisco Unity Data on the Primary Server from the Network Storage Location
Step 1 On the primary server, install the latest version of the Disaster Recovery Restore tool, if it is not already installed.
Step 2 Restore Cisco Unity data and Exchange voice messages by using the Disaster Recovery Restore tool and the backup that you made earlier. Refer to DiRT Help for detailed instructions. (The Help file, UnityDisasterRecovery.htm, is in the same directory as UnityDisasterRecoveryRestore.exe.)
Caution Follow Help carefully. DiRT includes a variety of options that you must understand to use the tools successfully.
Step 3 Reapply any non-Cisco Unity custom registry settings. (DiRT backs up and restores Cisco Unity registry settings.)
The next procedure applies to a Cisco Unity version 4.x primary server. (If the server is running 3.1(x), see the "To Configure Failover on the Primary Server—Version 3.1(x)" procedure instead.) Note that after the procedure is finished, the primary server is active and handles calls.
To Configure Failover on the Primary Server—Version 4.x
Step 1 In Windows Explorer, browse to the CommServer directory.
Step 2 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.
Step 3 On the Welcome page, click Next.
Step 4 On the Specify Server Role page, click Primary Server, and click Next.
Step 5 On the Enter the Name of Your Server page, click Browse, select the name of the secondary server, and click OK. The IP address for the secondary server is filled in automatically.
Step 6 Click Next.
Step 7 On the Enter Failover Account Information page, click Browse, and double-click the name of the message store services account. This is the account that the failover service will log on as.
The account you select must have the right to act as part of the operating system and to log on as a service, and must be a member of the Local Administrators group.
Caution You must specify the same account on both the primary and secondary servers.
Step 8 In the Password field, enter the password for the account that the failover service will log on as, and click Next.
Step 9 On the Begin Configuring Your Server page, click Configure. The wizard verifies settings and configures failover on the primary server.
If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and click Configure again.
Step 10 On the Completing page, click Finish.
The next procedure applies to a Cisco Unity version 3.1(x) primary server. (If the server is running 4.x, see the "To Configure Failover on the Primary Server—Version 4.x" procedure instead.) Note that after the procedure is finished, the primary server is active and handles calls.
To Configure Failover on the Primary Server—Version 3.1(x)
Step 1 In Windows Explorer, browse to the directory where Cisco Unity is installed (the default directory is CommServer).
Step 2 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.
Step 3 Click Next.
Step 4 Click Browse, select the name of the secondary server, and click OK. The IP address for the secondary server is filled in automatically.
Step 5 If the system is running Cisco Unity 3.1(2), skip to Step 6.
If the system is running Cisco Unity 3.1(3) or later and you want the switch file for the selected phone system to replicate during the wizard, check the Copy Switch Files from Primary Server to Secondary Server check box.
Note The switch file is replicated only during the failover configuration wizard. If you select a different phone system after you run the wizard, the new switch file is not replicated to the secondary server. In addition, changes to phone system settings are not replicated between the primary and secondary servers. If you change phone system settings after you run the failover configuration wizard, you must manually change values on both servers.
Step 6 Click Next.
Step 7 If you did not create a Cisco Unity failover account, skip to Step 8.
If you created a Cisco Unity failover account, click Browse, and double-click the name of the account.
Caution You must specify the same account on both the primary and secondary servers.
Step 8 Enter the password for the account that the failover service will log on as.
Step 9 Click Next.
Step 10 Click Configure. The wizard verifies settings and configures failover on the primary server.
If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and click Configure again.
Step 11 On the Completing page, click Finish.
Step 12 Exit and restart the Cisco Unity software.
The next procedure applies to a Cisco Unity version 4.x secondary server. (If the server is running 3.1(x), see the "To Configure Failover on the Secondary Server—Version 3.1(x)" procedure instead.)
To Configure Failover on the Secondary Server—Version 4.x
Step 1 On the Windows taskbar, double-click the system clock. The Date/Time Properties dialog box appears.
Step 2 Set the time to the same hour and minute as shown on the primary server, and click OK.
Step 3 In Windows Explorer, browse to the CommServer directory.
Step 4 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.
Step 5 On the Welcome page, click Next.
Step 6 On the Specify Server Role page, click Secondary Server, and click Next.
Step 7 On the Enter the Name of Your Server page, click Browse, select the name of the primary server, and click OK. The IP address for the primary server is filled in automatically.
Step 8 Click Next.
Step 9 On the Enter Failover Account Information page, click Browse, and double-click the name of the message store services account. This is the account that the failover service will log on as.
The account you select must have the right to act as part of the operating system and to log on as a service, and must be a member of the Local Administrators group.
Caution You must specify the same account on both the primary and secondary servers.
Step 10 In the Password field, enter the password for the account that the failover service will log on as, and click Next.
Step 11 On the Begin Configuring Your Server page, click Configure. The wizard verifies settings and configures failover on the secondary server.
If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and click Configure again.
Step 12 On the Completing page, click Finish.
The next procedure applies to a Cisco Unity version 3.1(x) secondary server. (If the server is running 4.x, see the "To Configure Failover on the Secondary Server—Version 4.x" procedure instead.)
To Configure Failover on the Secondary Server—Version 3.1(x)
Step 1 In Windows Explorer, browse to the directory where Cisco Unity is installed (the default directory is CommServer).
Step 2 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.
Step 3 Click Next.
Step 4 Click Browse, select the name of the primary server, and click OK. The IP address for the primary server is filled in automatically.
Step 5 If the system is running Cisco Unity 3.1(2), skip to Step 6.
If the system is running Cisco Unity 3.1(3) or later, and you want the switch file for the selected phone system to replicate during the wizard, check the Copy Switch Files from Primary Server to Secondary Server check box.
Note The switch file is replicated only during the failover configuration wizard. If you select a different phone system after you run the wizard, the new switch file is not replicated to the secondary server. In addition, changes to phone system settings are not replicated between the primary and secondary servers. If you change phone system settings after you run the failover configuration wizard, you must manually change values on both servers.
Step 6 Click Next.
Step 7 If you did not create a Cisco Unity failover account, skip to Step 8.
If you created a Cisco Unity failover account, click Browse, and double-click the name of the account.
Caution You must specify the same account on both the primary and secondary servers.
Step 8 Enter the password for the account that the failover service will log on as.
Step 9 Click Next.
Step 10 Click Configure. The wizard verifies settings and configures failover on the secondary server.
If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and click Configure again.
Step 11 On the Completing page, click Finish.
Step 12 Exit and restart the Cisco Unity software.
Feedback
