Reconfiguration and Upgrade Guide for Cisco Unity Release 8.x (With Microsoft Exchange)
Upgrading Cisco Unity to the Shipping 8.x Version
Downloads: This chapterpdf (PDF - 437.0KB) The complete bookPDF (PDF - 7.03MB) | Feedback

Upgrading Cisco Unity to the Shipping 8.x Version

Table Of Contents

Upgrading Cisco Unity to the Shipping 8.x Version

Tool Considerations for Moving or for Backing Up and Restoring Cisco Unity Data for an Upgrade to 8.x

Backing Up and Restoring Using DiRT

Moving Data Using Only GSM

Moving Data Using Only COBRAS

Moving Data Using GSM and COBRAS Together

Task List for Upgrading Cisco Unity Without Failover to the Shipping 8.x Version

Task List for a Simultaneous Upgrade of Both Cisco Unity Failover Servers to the Shipping 8.x Version

Task List for a Rolling Upgrade of a Cisco Unity Failover System to the Shipping 8.x Version

Task List for Upgrading Cisco Unity to the Shipping 8.x Version When the Cisco Unity Bridge Is Configured

Obtaining Cisco Unity License 8.x Files

Downloading Software for the Upgrade to Cisco Unity 8.x

Extending the Active Directory Schema for Cisco Unity 8.x

Installing Exchange 2003 Service Pack 2 for Cisco Unity 8.x

Checking the Consistency of the Cisco Unity Database for the Upgrade to 8.x

Backing Up Cisco Unity Data for the Upgrade to 8.x

Disabling the TUI Menu Option for Changing Subscriber Settings in Custom Conversations for the Upgrade to 8.x

Manually Failing Over, and Disabling Automatic Failover and Failback for the Upgrade to 8.x

Stopping and Disabling the World Wide Web Publishing Services on the Primary and Secondary Servers for the Upgrade to 8.x

Setting Permissions on an Active Directory Location by Using the Permissions Wizard for the Upgrade to 8.x

Disabling Antivirus and Cisco Security Agent Services for the Upgrade to 8.x

Installing Software Prerequisites and Verifying Network Prerequisites for the Upgrade to 8.x

Upgrading and Configuring Cisco Unity 8.x Software

Installing the Latest Microsoft Service Packs for Cisco Unity 8.x

Installing Microsoft Updates and Cisco Security Agent for Cisco Unity for 8.x

Re-enabling Antivirus and Cisco Security Agent Services for Cisco Unity 8.x

Configuring Internet Explorer to Display the Cisco Unity Administrator in 8.x

Enabling and Starting the World Wide Web Publishing Services on the Primary and Secondary Servers for Cisco Unity 8.x

Re-enabling the TUI Menu Option for Changing Subscriber Settings in Custom Conversations for Cisco Unity 8.x

Securing the Example Administrator and Example Subscriber Accounts Against Toll Fraud in Cisco Unity 8.x

Hardening the Cisco Unity 8.x Server

Redesignating the Bridgehead Server for Cisco Unity 8.x


Upgrading Cisco Unity to the Shipping 8.x Version


The task lists and procedures in this chapter apply only to upgrading the Cisco Unity software from version 4.2 or later to the currently shipping version. Note that the lists contain some tasks that reference instructions in other Cisco Unity documentation.

For information on adding Cisco Unity features, see the "Adding Features to the Cisco Unity 8.x System" chapter after you have finished upgrading the software.

This chapter contains the following sections:

Tool Considerations for Moving or for Backing Up and Restoring Cisco Unity Data for an Upgrade to 8.x

Task List for Upgrading Cisco Unity Without Failover to the Shipping 8.x Version

Task List for a Simultaneous Upgrade of Both Cisco Unity Failover Servers to the Shipping 8.x Version

Task List for a Rolling Upgrade of a Cisco Unity Failover System to the Shipping 8.x Version

Task List for Upgrading Cisco Unity to the Shipping 8.x Version When the Cisco Unity Bridge Is Configured

Obtaining Cisco Unity License 8.x Files

Downloading Software for the Upgrade to Cisco Unity 8.x

Extending the Active Directory Schema for Cisco Unity 8.x

Installing Exchange 2003 Service Pack 2 for Cisco Unity 8.x

Checking the Consistency of the Cisco Unity Database for the Upgrade to 8.x

Backing Up Cisco Unity Data for the Upgrade to 8.x

Disabling the TUI Menu Option for Changing Subscriber Settings in Custom Conversations for the Upgrade to 8.x

Manually Failing Over, and Disabling Automatic Failover and Failback for the Upgrade to 8.x

Stopping and Disabling the World Wide Web Publishing Services on the Primary and Secondary Servers for the Upgrade to 8.x

Setting Permissions on an Active Directory Location by Using the Permissions Wizard for the Upgrade to 8.x

Disabling Antivirus and Cisco Security Agent Services for the Upgrade to 8.x

Installing Software Prerequisites and Verifying Network Prerequisites for the Upgrade to 8.x

Upgrading and Configuring Cisco Unity 8.x Software

Installing the Latest Microsoft Service Packs for Cisco Unity 8.x

Installing Microsoft Updates and Cisco Security Agent for Cisco Unity for 8.x

Re-enabling Antivirus and Cisco Security Agent Services for Cisco Unity 8.x

Configuring Internet Explorer to Display the Cisco Unity Administrator in 8.x

Enabling and Starting the World Wide Web Publishing Services on the Primary and Secondary Servers for Cisco Unity 8.x

Re-enabling the TUI Menu Option for Changing Subscriber Settings in Custom Conversations for Cisco Unity 8.x

Securing the Example Administrator and Example Subscriber Accounts Against Toll Fraud in Cisco Unity 8.x

Hardening the Cisco Unity 8.x Server

Redesignating the Bridgehead Server for Cisco Unity 8.x

Tool Considerations for Moving or for Backing Up and Restoring Cisco Unity Data for an Upgrade to 8.x

For upgrades to Cisco Unity 8.x that require you to replace the Cisco Unity server or to reinstall all software on the existing server, this chapter documents using the Cisco Unity Disaster Recovery tools (DiRT) to move data between servers or to back up and restore data on the same server. However, two other tools, Cisco Object Backup and Restore Application Suite (COBRAS) and the Global Subscriber Manager (GSM), have some advantages over DiRT that may make them more useful in some situations. This section summarizes the features of DiRT, GSM, and COBRAS so you can assess whether a tool other than DiRT would be more useful for your upgrade.

Backing Up and Restoring Using DiRT

DiRT backs up most of the data in the Cisco Unity SQL Server database and most of the registry entries in the Active Voice (Cisco Unity) hive of the Windows registry.

DiRT can back up data in one Active Directory forest and restore data to a Cisco Unity server in another forest, with the same server name or a different name.

DiRT can only back up all of the data on one server and restore all data on another server. You cannot back up or restore a subset of subscribers or other objects.

DiRT cannot merge data from multiple Cisco Unity servers onto another server.

Backing up and restoring messages is only necessary if you are moving data to a Cisco Unity server in another forest. DiRT can back up and restore secure messages.

If you back up data on one Cisco Unity server and restore it on another server in the same forest, you must either uninstall Cisco Unity on the old server or disconnect the old server from the network. (Simply disconnecting the old server from the network leaves orphaned data about the old server in Active Directory.)

When restoring data from a DiRT backup, you must restore to the same version of Cisco Unity that you backed up.

Moving Data Using Only GSM

GSM moves subscriber data between Cisco Unity servers in the same Active Directory forest. You must configure Digital Networking before you can use GSM.

GSM moves only top-level subscriber data, for example, alias, display name, extension, TUI password, and recorded voice name.

GSM allows you to move subscriber data between a server running one version of Cisco Unity and a server running the same version or a later version of Cisco Unity.

GSM allows you to move a subset of Cisco Unity subscribers from one server to another server for migrations or load balancing.

GSM allows you to move subscribers from multiple Cisco Unity servers onto one server.

After GSM creates a subscriber account on the new server, GSM automatically deletes the corresponding account from the old server.

Because very little subscriber data is moved and no non-subscriber data is moved, GSM prompts you to specify the template to use for the subscribers you are moving, and prompts you how to resolve references, for example, to call handlers that exist on one server and not the other.

Moving Data Using Only COBRAS

COBRAS moves much more data than GSM but less data than DiRT. For information on which data is moved and which is not moved, see the COBRAS help at http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.

COBRAS allows you to move subscriber data between a server running one version of Cisco Unity and a server running the same version or a later version of Cisco Unity.

COBRAS allows you to move a subset of Cisco Unity subscribers and other objects from one server to another server for migrations or load balancing.

COBRAS allows you to merge data from multiple Cisco Unity servers onto one server.

Backing up and restoring messages is only necessary if you are moving data to a Cisco Unity server in another forest. COBRAS cannot back up secure messages.

If you back up data on one Cisco Unity server, before you can restore it on another server in the same forest, you must manually delete subscribers from the old server, wait for Active Directory replication to replicate the changes, and wait for Cisco Unity on the new server to remove references to the deleted subscribers.

Moving Data Using GSM and COBRAS Together

COBRAS moves much more data than GSM but less data than DiRT. For information on which data is moved and which is not moved, see the COBRAS help at http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html. (The data that GSM moves is a subset of the data that COBRAS backs up and restores.)

GSM requires that the Cisco Unity servers be in the same Active Directory forest. You must configure Digital Networking before you can use GSM.

When using GSM and COBRAS together, you first use COBRAS to back up all data on the old server, then use GSM to move subscriber data between servers, and finally use COBRAS to restore additional subscriber data and to move other Cisco Unity objects.

After GSM creates a subscriber account on the new server, GSM automatically deletes the corresponding account from the old server.

Using GSM and COBRAS together allows you to move subscriber data between a server running one version of Cisco Unity and a server running the same version or a later version of Cisco Unity.

Using GSM and COBRAS together allows you to move a subset of Cisco Unity subscribers and other objects from one server to another server for migrations or load balancing.

Using GSM and COBRAS together allows you to move and merge data from multiple Cisco Unity servers onto one server.

For more information, see:

DiRT Help and training videos at http://ciscounitytools.com/Applications/Unity/DIRT/DIRT.html.

GSM Help and training videos at http://ciscounitytools.com/Applications/Unity/GSM/GSM.html.

COBRAS Help and training videos at http://ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.

Task List for Upgrading Cisco Unity Without Failover to the Shipping 8.x Version

The Cisco Unity server will be out of service while the Cisco Unity software is upgraded.

1. If the Cisco Unity server is running a version earlier than 4.2(1): Upgrade to Cisco Unity 4.2(1). Upgrading from a version of Cisco Unity earlier that 4.2(1) directly to version 8.0 is not supported.

Do not upgrade to Cisco Unity 5.x or 7.x, either of which would require interim license files in addition to the Cisco Unity 8.x license files.

For more information on upgrading to version 4.2, see the applicable chapter in the Cisco Unity Reconfiguration and Upgrade Guide at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/42/upgrade/guide/ex/ex.html.

2. Obtain the license file(s) for the upgrade to Cisco Unity 8.x. See the "Obtaining Cisco Unity License 8.x Files" section.

3. Refer to Release Notes for Cisco Unity Release <Version> for additional information on upgrading to the shipping version of Cisco Unity. In particular, note the items in the sections "Installation and Upgrade Notes" and "Limitations and Restrictions." Release notes are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

4. Download software for the upgrade. See the "Downloading Software for the Upgrade to Cisco Unity 8.x" section.

5. If you are upgrading from Cisco Unity 4.2: Update the Active Directory schema. See the "Extending the Active Directory Schema for Cisco Unity 8.x" section.

If you are upgrading from Cisco Unity 5.x or later, you do not need to update the Active Directory schema because there have been no additional schema extensions.

6. If the Cisco Unity server is running Windows 2000 Server: Upgrade to Windows Server 2003. For more information, see the "Replacing or Converting a Cisco Unity 8.x Server, or Upgrading to Windows 2003" chapter.

If Exchange 2000 is installed on the Cisco Unity server and if you want Exchange to be installed on the upgraded Cisco Unity server, you must install Exchange Server 2003 or Exchange Server 2003 System Manager while you are reinstalling software. If you do not want Exchange to be installed on the Cisco Unity server at the end of the upgrade, see the "Separating Cisco Unity 8.x and Exchange" chapter.

If Exchange 2000 System Manager is installed on the Cisco Unity server, you must install Exchange Server 2003 System Manager while you are reinstalling software.


Caution For Cisco Unity 8.0 and later, Windows 2000 Server is not supported on the Cisco Unity server, and Exchange 2000 Server is not supported on the Cisco Unity server or on the partner Exchange server.

7. If you upgraded to Windows Server 2003 or replaced the servers in Task 6., and if Cisco Unity is integrated with the phone system using PIMG or TIMG: If you changed the name of the Cisco Unity server when re-installing the operating system, and if the PIMG or TIMG devices are configured to communicate with Cisco Unity by using the Cisco Unity server name instead of the IP address, on each PIMG or TIMG device, update the "Host List" setting under the "VoIP Host Group Settings" to reflect the new Cisco Unity server name.

In addition, confirm that the following values match for each port:

In the PIMG administration application, the value of VoIP Endpoint ID on the Gateway Routing tab.

On the Cisco Unity server, in the Unity Telephone Integration Manager (UTIM), the value of Contact Line Name on the Sip Info tab.

For more information, see the applicable integration guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.

8. If the partner Exchange server is a separate server running Exchange 2000 Server: Upgrade Exchange. Do the procedures in the applicable section in the "Upgrading Exchange on the Cisco Unity 8.x System or Before an Upgrade to 8.x" chapter.


Caution For Cisco Unity 8.0 and later, Exchange 2000 Server is not supported on the partner Exchange server.

9. If you are using Exchange Server 2003: When Exchange 2003 or Exchange 2003 System Manager is running on the Cisco Unity server, or when Exchange 2003 is running on the partner Exchange server or any Exchange server on which Cisco Unity subscriber mailboxes are homed, install Exchange 2003 Service Pack 2. See the "Installing Exchange 2003 Service Pack 2 for Cisco Unity 8.x" section.

10. If SMTP Networking is configured: Migrate to VPIM Networking. Beginning with Cisco Unity 5.0(1), SMTP Networking is no longer supported. See the "Migrating from SMTP Networking to VPIM Networking" chapter of the Networking in Cisco Unity Guide (With Microsoft Exchange), Release 4.0(5) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/405/networking/guide/ex/ex.html.


Caution You must migrate from SMTP Networking to VPIM Networking before you begin the upgrade to Cisco Unity 8.x, or SMTP subscribers will stop functioning.

11. Check the consistency of the Cisco Unity database by using the Cisco Unity Directory Walker (DbWalker) utility. See the "Checking the Consistency of the Cisco Unity Database for the Upgrade to 8.x" section.

12. Back up Cisco Unity data by using the Cisco Unity Disaster Recovery Backup tool. See the "Backing Up Cisco Unity Data for the Upgrade to 8.x" section.

13. Required if you are upgrading from Cisco Unity 4.2, optional if you are upgrading from Cisco Unity 5.0 or later: Run the Permissions wizard.

If you downloaded the latest version of the Permissions wizard from CiscoUnityTools.com, install and run that version. Otherwise, run the version that appears in the Utilities\PermissionsWizard directory on the shipping Cisco Unity 8.x DVD. For more information, refer to the Permissions wizard Help file, PWHelp_<language>.htm.

We recommend that you run the Cisco Unity Permissions wizard during off-peak hours unless Cisco Unity is configured as Voice Messaging and subscriber accounts are not stored in the corporate directory.

When the Permissions wizard completes, the Lsass.exe process updates the Active Directory database with the new permissions. While Lsass.exe is processing the updates, it uses 100 percent of available processor time on a domain controller that:

Hosts the domain to which the Cisco Unity server belongs.

Has been specified to respond to requests from the site.

Other domain controllers in the domain and other global catalog servers in the forest are also affected, but the impact is less significant. The updates take a few minutes to several hours, depending on the size of the database. Except when the Cisco Unity server is the domain controller and the Lsass.exe process slows the screen refresh, you may continue with the Cisco Unity upgrade while Lsass.exe is processing changes.

14. If Cisco Unity is configured to automatically create Bridge or VPIM subscribers in a different AD location than regular subscribers: Rerun the Permissions wizard, and specify the domain and location on the Set Active Directory Containers for New Objects page. See the "Setting Permissions on an Active Directory Location by Using the Permissions Wizard for the Upgrade to 8.x" section.

15. If antivirus software is installed on the Cisco Unity server: Disable antivirus services. See the "Disabling Antivirus and Cisco Security Agent Services for the Upgrade to 8.x" section.

16. Run the Cisco Unity System Setup Assistant to install the software required by Cisco Unity 8.x and to verify network requirements. Cisco Unity System Setup Assistant updates the required Windows components and browser, and installs the Windows and the SQL Server or MSDE service packs required by the current Cisco Unity Setup. See the "Installing Software Prerequisites and Verifying Network Prerequisites for the Upgrade to 8.x" section.


Caution Do not install the latest service packs that are recommended for use with Cisco Unity yet. Any service packs qualified for use with the current version of Cisco Unity after the current version was released have not been tested with Cisco Unity Setup and may cause Setup to fail. In addition, do not run the latest Cisco Unity Server Updates wizard, which installs updates only for the latest recommended service packs.

17. If you are using Cisco Unity voice recognition: Turn off the voice-recognition server.

Cisco Unity 8.0 and later cannot be integrated with a Cisco Unity 5.x to 7.x voice-recognition server. If you want to use voice recognition with Cisco Unity 8.x, you must install new software on the voice-recognition server. The task list alerts you when to install and configure voice-recognition software.

18. Run the Cisco Unity System Setup Assistant to upgrade and configure the Cisco Unity software. See the "Upgrading and Configuring Cisco Unity 8.x Software" section.

19. Install the latest Microsoft service packs qualified for use with Cisco Unity, if any. See the "Installing the Latest Microsoft Service Packs for Cisco Unity 8.x" section.

20. Run the Cisco Unity Server Updates wizard to install Microsoft security updates and, optionally, Cisco Security Agent for Cisco Unity. See the "Installing Microsoft Updates and Cisco Security Agent for Cisco Unity for 8.x" section.

21. If antivirus software is installed on the Cisco Unity server: Re-enable antivirus services. See the "Re-enabling Antivirus and Cisco Security Agent Services for Cisco Unity 8.x" section.

22. Review the substitute objects on the System > Configuration > Settings page of the Cisco Unity Administrator. The objects are Substitute Recipient, Substitute Owner, Substitute After Message Call Handler, and Substitute Exit Call Handler. Cisco Unity uses the objects to substitute references to any subscriber that is deleted by using the Cisco Unity Administrator without first reassigning such references (for example, ownership of a call handler or distribution list). For new installations, the Example Administrator is configured as the Substitute Recipient and Substitute Owner, and the Goodbye call handler is configured as the Substitute After Message Call Handler and Substitute Exit Call Handler. For upgrades, any changes made to the defaults will not be overwritten. However, we recommend that you review these settings now and update them if you wish to use different substitute objects. Refer to Cisco Unity Administrator Help for a description of each object and where it applies.

23. If you want to use Cisco Unity 8.x voice recognition: Install and configure voice-recognition software. See the "Installing and Configuring a Cisco Unity 8.x Voice-Recognition Server" appendix of the applicable Cisco Unity installation guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

24. Update Internet Explorer security settings. See the "Configuring Internet Explorer to Display the Cisco Unity Administrator in 8.x" section.

25. Secure the Example Administrator and Example Subscriber accounts against toll fraud. See the "Securing the Example Administrator and Example Subscriber Accounts Against Toll Fraud in Cisco Unity 8.x" section.

26. Harden the Cisco Unity server. See the "Hardening the Cisco Unity 8.x Server" section.

27. If the system is using the AMIS or VPIM networking options: Refer to the applicable "Upgrading with <Networking Option>" section in the "Upgrading and Uninstalling Networking Options in Cisco Unity 8.x" chapter of the Networking Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/networking/guide/8xcunetx.html.

Task List for a Simultaneous Upgrade of Both Cisco Unity Failover Servers to the Shipping 8.x Version

If you want to upgrade a Cisco Unity failover system faster than with a rolling upgrade—roughly half of the duration of a rolling upgrade because you are upgrading both servers simultaneously—and you do not care that Cisco Unity functionality is not available during the upgrade, use this task list.

If you want to upgrade a Cisco Unity failover system and retain most Cisco Unity functionality for the duration of the upgrade, use the "Task List for a Rolling Upgrade of a Cisco Unity Failover System to the Shipping 8.x Version" section.

1. If the Cisco Unity server is running a version earlier than 4.2(1): Upgrade both Cisco Unity servers to Cisco Unity 4.2(1). Upgrading from a version of Cisco Unity earlier that 4.2(1) directly to version 8.0 is not supported.

Do not upgrade to Cisco Unity 5.x or 7.x, either of which would require interim license files in addition to the Cisco Unity 8.x license files.

For more information on upgrading to version 4.2, see the applicable chapter in the Cisco Unity Reconfiguration and Upgrade Guide at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/42/upgrade/guide/ex/ex.html.

2. Obtain the license file(s) for the upgrade to Cisco Unity 8.x. See the "Obtaining Cisco Unity License 8.x Files" section.

3. Refer to Release Notes for Cisco Unity Release <Version> for additional information on upgrading to the shipping version of Cisco Unity. In particular, note the items in the sections "Installation and Upgrade Notes" and "Limitations and Restrictions." Release notes are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

4. Download software for the upgrade. See the "Downloading Software for the Upgrade to Cisco Unity 8.x" section.

5. If you are upgrading from Cisco Unity 4.2: Update the Active Directory schema. See the "Extending the Active Directory Schema for Cisco Unity 8.x" section.

If you are upgrading from Cisco Unity 5.x or later, you do not need to update the Active Directory schema because there have been no additional schema extensions.

6. If the Cisco Unity servers are running Windows 2000 Server and/or if the Cisco Unity servers are no longer supported for version 8.0: Upgrade to Windows Server 2003 on both Cisco Unity servers and/or replace the servers. For more information, see the "Replacing or Converting a Cisco Unity 8.x Server, or Upgrading to Windows 2003" chapter.

If Exchange 2000 is installed on the Cisco Unity server and if you want Exchange to be installed on the upgraded Cisco Unity server, you must install Exchange Server 2003 or Exchange Server 2003 System Manager while you are reinstalling software. If you do not want Exchange to be installed on the Cisco Unity server at the end of the upgrade, see the "Separating Cisco Unity 8.x and Exchange" chapter.

If Exchange 2000 System Manager is installed on the Cisco Unity server, you must install Exchange Server 2003 System Manager while you are reinstalling software.


Caution For Cisco Unity 8.0 and later, Windows 2000 Server is not supported on the Cisco Unity server, and Exchange 2000 Server is not supported on the Cisco Unity server or on the partner Exchange server.

7. If you upgraded to Windows Server 2003 or replaced the servers in Task 6., and if Cisco Unity is integrated with the phone system using PIMG or TIMG: If you changed the name of the Cisco Unity server when re-installing the operating system, and if the PIMG or TIMG devices are configured to communicate with Cisco Unity by using the Cisco Unity server name instead of the IP address, on each PIMG or TIMG device, update the "Host List" setting under the "VoIP Host Group Settings" to reflect the new Cisco Unity server name.

In addition, confirm that the following values match for each port:

In the PIMG administration application, the value of VoIP Endpoint ID on the Gateway Routing tab.

On the Cisco Unity server, in the Unity Telephone Integration Manager (UTIM), the value of Contact Line Name on the Sip Info tab.

For more information, see the applicable integration guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.

8. If the partner Exchange server is a separate server running Exchange 2000 Server: Upgrade Exchange. Do the procedures in the applicable section in the "Upgrading Exchange on the Cisco Unity 8.x System or Before an Upgrade to 8.x" chapter.


Caution For Cisco Unity 8.0 and later, Exchange 2000 Server is not supported on the partner Exchange server.

9. If you are using Exchange Server 2003: When Exchange 2003 or Exchange 2003 System Manager is running on one of the Cisco Unity servers, or when Exchange 2003 is running on the partner Exchange server or any Exchange server on which Cisco Unity subscriber mailboxes are homed, install Exchange 2003 Service Pack 2 on both Cisco Unity servers. See the "Installing Exchange 2003 Service Pack 2 for Cisco Unity 8.x" section.

10. If SMTP Networking is configured: Migrate to VPIM Networking. Beginning with Cisco Unity 5.0(1), SMTP Networking is no longer supported. See the "Migrating from SMTP Networking to VPIM Networking" chapter in the Networking in Cisco Unity Guide (With Microsoft Exchange), Release 4.0(5) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/405/networking/guide/ex/ex.html.


Caution You must migrate from SMTP Networking to VPIM Networking before you begin the upgrade to Cisco Unity 8.x, or SMTP subscribers will stop functioning.

11. On the primary server, check the consistency of the Cisco Unity database by using the Cisco Unity Directory Walker (DbWalker) utility. See the "Checking the Consistency of the Cisco Unity Database for the Upgrade to 8.x" section.

12. On the secondary server, back up Cisco Unity data by using the Cisco Unity Disaster Recovery Backup tool. See the "Checking the Consistency of the Cisco Unity Database for the Upgrade to 8.x" section.

13. Required if you are upgrading from Cisco Unity 4.2, optional if you are upgrading from Cisco Unity 5.0 or later: Run the Permissions wizard on both Cisco Unity servers.

If you downloaded the latest version of the Permissions wizard from CiscoUnityTools.com, install and run that version. Otherwise, run the version that appears in the Utilities\PermissionsWizard directory on the shipping Cisco Unity 8.x DVD. For more information, refer to the Permissions wizard Help file, PWHelp_<language>.htm.


Note If you are upgrading from Cisco Unity 5.0 or later, you do not need to run the Permissions wizard.


We recommend that you run the Cisco Unity Permissions wizard during off-peak hours unless Cisco Unity is configured as Voice Messaging and subscriber accounts are not stored in the corporate directory.

When the Permissions wizard completes, the Lsass.exe process updates the Active Directory database with the new permissions. While Lsass.exe is processing the updates, it uses 100 percent of available processor time on a domain controller that:

Hosts the domain to which the Cisco Unity server belongs.

Has been specified to respond to requests from the site.

Other domain controllers in the domain and other global catalog servers in the forest are also affected, but the impact is less significant. The updates take a few minutes to several hours, depending on the size of the database. Except when the Cisco Unity server is the domain controller and the Lsass.exe process slows the screen refresh, you may continue with the Cisco Unity upgrade while Lsass.exe is processing changes.


Note When you run the Permissions wizard on the secondary server, Lsass.exe does not affect performance on domain controllers if you use the same service accounts and if you do not choose the Permissions wizard option to reset permissions on those accounts.


14. If Cisco Unity is configured to automatically create Bridge or VPIM subscribers in a different AD location than regular subscribers, and if you are upgrading from Cisco Unity 4.2: On both Cisco Unity servers, rerun the Permissions wizard, and specify the domain and location on the Set Active Directory Containers for New Objects page. See the "Setting Permissions on an Active Directory Location by Using the Permissions Wizard for the Upgrade to 8.x" section.

15. If antivirus software is installed on the Cisco Unity server: On both Cisco Unity servers, disable antivirus services. See the "Disabling Antivirus and Cisco Security Agent Services for the Upgrade to 8.x" section.

16. On both Cisco Unity servers, run the Cisco Unity System Setup Assistant to install the software required by Cisco Unity 8.x and to verify network requirements. Cisco Unity System Setup Assistant updates the required Windows components and browser, and installs the Windows and the SQL Server or MSDE service packs required by the current Cisco Unity Setup. See the "Installing Software Prerequisites and Verifying Network Prerequisites for the Upgrade to 8.x" section.


Caution Do not install the latest service packs that are recommended for use with Cisco Unity yet. Any service packs qualified for use with the current version of Cisco Unity after the current version was released have not been tested with Cisco Unity Setup and may cause Setup to fail. In addition, do not run the latest Cisco Unity Server Updates wizard, which installs updates only for the latest recommended service packs.

17. If you are using Cisco Unity voice recognition: Turn off the voice-recognition server.

Cisco Unity 8.0 and later cannot be integrated with a Cisco Unity 5.x to 7.x voice-recognition server. If you want to use voice recognition with Cisco Unity 8.x, you must install new software on the voice-recognition server. The task list alerts you when to install and configure voice-recognition software.

18. On both Cisco Unity servers, run the Cisco Unity System Setup Assistant to upgrade and configure the Cisco Unity software. See the "Upgrading and Configuring Cisco Unity 8.x Software" section.

19. On both Cisco Unity servers, install the latest Microsoft service packs qualified for use with Cisco Unity, if any. See the "Installing the Latest Microsoft Service Packs for Cisco Unity 8.x" section.

20. On both Cisco Unity servers, run the Cisco Unity Server Updates wizard to install Microsoft security updates and, optionally, Cisco Security Agent for Cisco Unity. See the "Installing Microsoft Updates and Cisco Security Agent for Cisco Unity for 8.x" section.

21. If antivirus software is installed on the Cisco Unity server: On both Cisco Unity servers, re-enable antivirus services. See the "Re-enabling Antivirus and Cisco Security Agent Services for Cisco Unity 8.x" section.

22. On the primary server, run the Configure Cisco Unity Failover wizard. See the "Configuring Failover on the Primary Server" section in the "Configuring Cisco Unity 8.x Failover" chapter of the Failover Configuration and Administration Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/failover/guide/8xcufgx.html.

23. On the secondary server, run the Configure Cisco Unity Failover wizard. See the "Configuring Failover on the Secondary Server" section in the "Configuring Cisco Unity 8.x Failover" chapter of the Failover Configuration and Administration Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/failover/guide/8xcufgx.html.

24. On the primary Cisco Unity server, review the substitute objects on the System > Configuration > Settings page of the Cisco Unity Administrator. The objects are Substitute Recipient, Substitute Owner, Substitute After Message Call Handler, and Substitute Exit Call Handler. Cisco Unity uses the objects to substitute references to any subscriber that is deleted by using the Cisco Unity Administrator without first reassigning such references (for example, ownership of a call handler or distribution list). For new installations, the Example Administrator is configured as the Substitute Recipient and Substitute Owner, and the Goodbye call handler is configured as the Substitute After Message Call Handler and Substitute Exit Call Handler. For upgrades, any changes made to the defaults will not be overwritten. However, we recommend that you review these settings now and update them if you wish to use different substitute objects. Refer to Cisco Unity Administrator Help for a description of each object and where it applies.

25. If you want to use Cisco Unity 8.x voice recognition: Install and configure voice-recognition software. See the "Installing and Configuring a Cisco Unity 8.x Voice-Recognition Server" appendix of the applicable Cisco Unity installation guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

26. On both Cisco Unity servers, update Internet Explorer security settings. See the "Configuring Internet Explorer to Display the Cisco Unity Administrator in 8.x" section.

27. On the primary Cisco Unity server, secure the Example Administrator and Example Subscriber accounts against toll fraud. See the "Securing the Example Administrator and Example Subscriber Accounts Against Toll Fraud in Cisco Unity 8.x" section.

28. Harden the Cisco Unity servers. See the "Hardening the Cisco Unity 8.x Server" section.

29. If the system is using the AMIS or VPIM networking options: Refer to the applicable "Upgrading with <Networking Option>" section in the "Upgrading and Uninstalling Networking Options in Cisco Unity 8.x" chapter of the Networking Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/networking/guide/8xcunetx.html.

Task List for a Rolling Upgrade of a Cisco Unity Failover System to the Shipping 8.x Version

If you want to upgrade a Cisco Unity failover system and retain most Cisco Unity functionality for the duration of the upgrade, use this task list. You can perform a rolling upgrade only when all of the requirements listed in Table 1-1 are met. If you want to perform a rolling upgrade on a system that does not meet the requirements, follow the specified documentation to satisfy the requirements, then return to this section and follow the task list.


Note Documentation in the Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange) applies to Cisco Unity 5.x and 7.x.


Table 1-1 Requirements for Performing a Rolling Upgrade 

Requirements for Performing a Rolling Upgrade
Documentation to Meet Requirements for Performing a Rolling Upgrade

The Cisco Unity servers are running version 4.2 or later.

The applicable chapter of the Cisco Unity Reconfiguration and Upgrade Guide (With Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/42/upgrade/guide/ex/ex.html. (The document title does not include a version, but it applies to Cisco Unity 4.x.)

The Cisco Unity servers are running Windows Server 2003.

The "Replacing Both 5.x Failover Servers, or Upgrading to Windows 2003" section in the "Replacing or Converting a Cisco Unity 5.x Server, or Upgrading to Windows 2003" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/upgrade/guide/ex/5xcurugex.html.


Note If you are upgrading to Windows Server 2003 and replacing the servers, you can do both simultaneously.


If you are replacing the Cisco Unity servers, they have already been replaced.

The "Replacing Both 5.x Failover Servers, or Upgrading to Windows 2003" section in the "Replacing or Converting a Cisco Unity 5.x Server, or Upgrading to Windows 2003" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/upgrade/guide/ex/5xcurugex.html.

Exchange is not installed on either Cisco Unity server.

The "Converting from Two-Server to Three-Server Failover" section in the "Separating Cisco Unity 5.x and Exchange" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/upgrade/guide/ex/5xcurugex.html.

The partner Exchange server is running Exchange Server 2003 or 2007.

The "Upgrading Exchange on the Cisco Unity 5.x System" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/upgrade/guide/ex/5xcurugex.html.

Cisco Unity is not interoperating with another voice-messaging system using SMTP Networking.

The "Migrating from SMTP Networking to VPIM Networking" chapter of the Networking in Cisco Unity Guide (With Microsoft Exchange), Release 4.0(5) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/405/networking/guide/ex/ex.html.


If you want to upgrade a Cisco Unity failover system faster than with a rolling upgrade—roughly half of the duration of a rolling upgrade because you are upgrading both servers simultaneously—and you do not care that Cisco Unity functionality is not available during the upgrade, use the "Task List for a Simultaneous Upgrade of Both Cisco Unity Failover Servers to the Shipping 8.x Version" section.

If you want to prevent users from using the Cisco Unity Administrator and the Cisco Personal Communications Assistant to change settings in the Cisco Unity database during the rolling upgrade, you can disable the World Wide Web Publishing Services service. If you do not stop the service and users make changes, the changes may be lost.

For systems that use the standard, optional, or alternate conversations, your subscribers may lose changes that they make through the telephony user interface (TUI) to their personal options (for example, voice names or greetings) during the rolling upgrade process. We recommend that you advise subscribers to avoid changing their personal options through the TUI during the rolling upgrade process.

For systems that have custom conversations created through the Custom Key Map Tool, you can optionally use the Custom Key Map Tool to disable the menu in the telephony user interface (TUI) for changing subscriber personal settings such as a new voice name or new greeting. If you do not disable the menu, changes to subscriber options that are made in the TUI may be lost.

1. Obtain the license file(s) for the upgrade to Cisco Unity 8.x. See the "Obtaining Cisco Unity License 8.x Files" section.

2. Refer to Release Notes for Cisco Unity Release <Version> for additional information on upgrading to the shipping version of Cisco Unity. In particular, note the items in the sections "Installation and Upgrade Notes" and "Limitations and Restrictions." Release notes are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

3. Download software for the upgrade. See the "Downloading Software for the Upgrade to Cisco Unity 8.x" section.

4. If you are upgrading from Cisco Unity 4.2: Update the Active Directory schema. See the "Extending the Active Directory Schema for Cisco Unity 8.x" section.

If you are upgrading from Cisco Unity 5.x or 7.x: You do not need to update the Active Directory schema because there have been no additional schema extensions. Skip to Task 5.

5. On the primary server, check the consistency of the Cisco Unity database by using the Cisco Unity Directory Walker (DbWalker) utility. See the "Checking the Consistency of the Cisco Unity Database for the Upgrade to 8.x" section.

6. On the secondary server, back up Cisco Unity data by using the Disaster Recovery Backup tool. See the "Backing Up Cisco Unity Data for the Upgrade to 8.x" section.

7. If you want to use Cisco Unity 8.x voice recognition: Install voice-recognition software on the voice-recognition server. See the "Installing and Configuring a Voice-Recognition Server" appendix of the applicable Cisco Unity installation guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

The task list will alert you when to configure the voice-recognition server in Cisco Unity Administrator.

8. If your subscribers use a custom conversation created through the Custom Key Map Tool, and if you want to prevent them from changing Cisco Unity data during the upgrade: On the primary server, disable the telephony user interface (TUI) menu option for changing subscriber settings in the custom conversation. See the "Disabling the TUI Menu Option for Changing Subscriber Settings in Custom Conversations for the Upgrade to 8.x" section.

9. Manually fail over to the secondary server, and disable automatic failover and failback. See the "Manually Failing Over, and Disabling Automatic Failover and Failback for the Upgrade to 8.x" section.

10. If you want to prevent users from using Cisco Unity Administrator or Cisco PCA to change Cisco Unity data during the upgrade: Stop and disable the World Wide Web Publishing Services service on the primary and secondary servers. See the "Stopping and Disabling the World Wide Web Publishing Services on the Primary and Secondary Servers for the Upgrade to 8.x" section.

Unless noted otherwise, do the following tasks on the primary server. The task list will alert you when to begin doing the same tasks on the secondary server.

11. Required if you are upgrading from Cisco Unity 4.2, optional if you are upgrading from Cisco Unity 5.0 or later: Run the Permissions wizard on both Cisco Unity servers.

If you downloaded the latest version of the Permissions wizard from CiscoUnityTools.com, install and run that version. Otherwise, run the version that appears in the Utilities\PermissionsWizard directory on the shipping Cisco Unity 8.x DVD. For more information, refer to the Permissions wizard Help file, PWHelp_<language>.htm.

We recommend that you run the Cisco Unity Permissions wizard during off-peak hours unless Cisco Unity is configured as Voice Messaging and subscriber accounts are not stored in the corporate directory.

When the Permissions wizard completes, the Lsass.exe process updates the Active Directory database with the new permissions. While Lsass.exe is processing the updates, it uses 100 percent of available processor time on a domain controller that:

Hosts the domain to which the Cisco Unity server belongs.

Has been specified to respond to requests from the site.

Other domain controllers in the domain and other global catalog servers in the forest are also affected, but the impact is less significant. The updates take a few minutes to several hours, depending on the size of the database. Except when the Cisco Unity server is the domain controller and the Lsass.exe process slows the screen refresh, you may continue with the Cisco Unity upgrade while Lsass.exe is processing changes.


Note When you run the Permissions wizard on the secondary server, Lsass.exe does not affect performance on domain controllers if you use the same service accounts and if you do not choose the Permissions wizard option to reset permissions on those accounts.


12. If Cisco Unity is configured to automatically create Bridge or VPIM subscribers in a different AD location than regular subscribers, and if you are upgrading from Cisco Unity 4.2: Only on the primary server, rerun the Permissions wizard, and specify the domain and location on the Set Active Directory Containers for New Objects page. See the "Setting Permissions on an Active Directory Location by Using the Permissions Wizard for the Upgrade to 8.x" section.

13. If antivirus software or Cisco Security Agent for Cisco Unity is installed on the Cisco Unity server: Disable antivirus services and the Cisco Security Agent service. See the "Disabling Antivirus and Cisco Security Agent Services for the Upgrade to 8.x" section.

14. Install the required Exchange service pack. See the "Installing Exchange 2003 Service Pack 2 for Cisco Unity 8.x" section.

15. Run the Cisco Unity System Setup Assistant to install the software required by Cisco Unity 8.x and to verify network requirements. Cisco Unity System Setup Assistant updates the required Windows components and browser, and installs the Windows and the SQL Server or MSDE service packs required by the current Cisco Unity Setup. See the "Installing Software Prerequisites and Verifying Network Prerequisites for the Upgrade to 8.x" section.


Caution Do not install the latest service packs that are recommended for use with Cisco Unity yet. Any service packs qualified for use with the current version of Cisco Unity after the current version was released have not been tested with Cisco Unity Setup and may cause Setup to fail. In addition, do not run the latest Cisco Unity Server Updates wizard, which installs updates only for the latest recommended service packs.

16. If you are using Cisco Unity voice recognition: Turn off the voice-recognition server.

Cisco Unity 8.0 and later cannot be integrated with a Cisco Unity 5.x to 7.x voice-recognition server. If you want to use voice recognition with Cisco Unity 8.x, you must install new software on the voice-recognition server. The task list alerts you when to install and configure voice-recognition software.

17. Run the Cisco Unity System Setup Assistant to upgrade and configure the Cisco Unity software. See the "Upgrading and Configuring Cisco Unity 8.x Software" section.

18. Install the latest Microsoft service packs qualified and recommended for use with Cisco Unity, if any. See the "Installing the Latest Microsoft Service Packs for Cisco Unity 8.x" section.

19. Run the Cisco Unity Server Updates wizard to install Microsoft security updates and, optionally, Cisco Security Agent for Cisco Unity. See the "Installing Microsoft Updates and Cisco Security Agent for Cisco Unity for 8.x" section.

20. If antivirus software or Cisco Security Agent for Cisco Unity is installed on the Cisco Unity server: Re-enable antivirus services and the Cisco Security Agent service. See the "Re-enabling Antivirus and Cisco Security Agent Services for Cisco Unity 8.x" section.

21. Update Internet Explorer security settings. See the "Configuring Internet Explorer to Display the Cisco Unity Administrator in 8.x" section.

22. If you installed a Cisco Unity 8.x voice recognition server in Task 7.: Configure the voice-recognition server in the Cisco Unity Administrator. See the "Configuring Voice-Recognition Software" section in the "Installing and Configuring a Cisco Unity 8.x Voice-Recognition Server" appendix of the applicable Cisco Unity installation guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

23. On the primary server, run the Configure Cisco Unity Failover wizard. See the "Configuring Failover on the Primary Server" section in the "Configuring Cisco Unity 8.x Failover" chapter of the Failover Configuration and Administration Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/failover/guide/8xcufgx.html.

24. On the secondary server, fail back to the primary server. See the "Manually Initiating Failover or Failback" section in the "Monitoring and Maintaining Cisco Unity 8.x Failover" chapter of the Failover Configuration and Administration Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/failover/guide/8xcufgx.html.

25. On the secondary server, repeat the following tasks:

Task 11.

Task 13. through Task 15.

Task 17. through Task 22.

When you have completed these tasks on the secondary, both Cisco Unity servers will be fully functional in a failover configuration.

26. On the secondary server, run the Configure Cisco Unity Failover wizard. See the "Configuring Failover on the Secondary Server" section in the "Configuring Cisco Unity 8.x Failover" chapter of the Failover Configuration and Administration Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/failover/guide/8xcufgx.html.

27. If you disabled World Wide Web Publishing Services service in Step 10.: Enable and start the World Wide Web Publishing Services service on the primary and secondary servers. See the "Enabling and Starting the World Wide Web Publishing Services on the Primary and Secondary Servers for Cisco Unity 8.x" section

28. If you disabled the TUI menu option for changing subscriber settings in the custom conversation in Step 8.: Re-enable the telephony user interface (TUI) menu option for changing subscriber settings in the custom conversation. See the "Re-enabling the TUI Menu Option for Changing Subscriber Settings in Custom Conversations for Cisco Unity 8.x" section.

29. On the primary server, review the substitute objects on the System > Configuration > Settings page of the Cisco Unity Administrator. The objects are Substitute Recipient, Substitute Owner, Substitute After Message Call Handler, and Substitute Exit Call Handler. Cisco Unity uses the objects to substitute references to any subscriber that is deleted by using the Cisco Unity Administrator without first reassigning such references (for example, ownership of a call handler or distribution list). For new installations, the Example Administrator is configured as the Substitute Recipient and Substitute Owner, and the Goodbye call handler is configured as the Substitute After Message Call Handler and Substitute Exit Call Handler. For upgrades, any changes made to the defaults will not be overwritten. However, we recommend that you review these settings now and update them if you wish to use different substitute objects. Refer to Cisco Unity Administrator Help for a description of each object and where it applies.

30. On the primary server, secure the Example Administrator and Example Subscriber accounts against toll fraud. See the "Securing the Example Administrator and Example Subscriber Accounts Against Toll Fraud in Cisco Unity 8.x" section.

31. zzzIf the system is using the AMIS or VPIM networking options: Refer to the applicable "Upgrading with <Networking Option>" section in the "Upgrading and Uninstalling Networking Options in Cisco Unity 8.x" chapter of the Networking Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/networking/guide/8xcunetx.html.

Task List for Upgrading Cisco Unity to the Shipping 8.x Version When the Cisco Unity Bridge Is Configured

When the Cisco Unity system is using the Cisco Unity Bridge, the order and timing of upgrade tasks are different than for a Cisco Unity system that is not using the Bridge. Use the task list in this section to upgrade Cisco Unity to version 8.x—and, if necessary, to upgrade Bridge and Cisco Unity servers to versions supported by Cisco Unity 8.x before the 8.x upgrade.

1. If the Bridge server is running version 3.0(6) or later, and all Cisco Unity servers in the network are running version 4.2(1) or later, skip to Task 2.

Otherwise, upgrade as applicable, depending on the Bridge and Cisco Unity versions:

Bridge
Version
Cisco Unity
Version
Upgrade Servers

3.0(6) or later

4.0(3) through 4.1(1)

Upgrade all Cisco Unity servers in the network to version 4.2(1). See the "Upgrading from Cisco Unity 4.0(3) or Later with Bridge 3.x" chapter of the Networking Guide for Cisco Unity Bridge Release 3.1 (For Cisco Unity Release 4.x with Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/bridge/31/networking/guide/31ex/31ebnet.html.

Note When the Networking Guide directs you to the Reconfiguration and Upgrade Guide for Cisco Unity, follow the doc link here to the "Upgrading Cisco Unity 4.x Software to the Shipping Version" chapter rather than the link provided in that guide.

3.0(1) through 3.0(5)

4.2(1) or later

Upgrade the Bridge server to version 3.0(6) or 3.1(1). See the "Upgrading Bridge 3.x Software to the Shipping Version" chapter of the Networking Guide for Cisco Unity Bridge Release 3.1 (For Cisco Unity Release 4.x with Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/bridge/31/networking/guide/31ex/31ebnet.html.

3.0(1) through 3.0(5)

4.0(3) through 4.1(1)

Upgrade the Bridge server to version 3.0(6) or 3.1(1) and all the Cisco Unity servers in the network to version 4.2(1). See the "Upgrading from Cisco Unity 4.0(3) or Later with Bridge 3.x" chapter of the Networking Guide for Cisco Unity Bridge Release 3.1 (For Cisco Unity Release 4.x with Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/bridge/31/networking/guide/31ex/31ebnet.html.

Note When the Networking Guide directs you to the Reconfiguration and Upgrade Guide for Cisco Unity, follow the doc link here to the "Upgrading Cisco Unity 4.x Software to the Shipping Version" chapter rather than the link provided in that guide.


2. Upgrade the Cisco Unity bridgehead server to version 8.x:

If failover is not configured

Do Task 2. through Task 27. in the "Task List for Upgrading Cisco Unity Without Failover to the Shipping 8.x Version" section.

If failover is configured and you want to do a simultaneous upgrade

Do Task 2. through Task 29. in the "Task List for a Simultaneous Upgrade of Both Cisco Unity Failover Servers to the Shipping 8.x Version" section.

If failover is configured and you want to do a rolling upgrade

Do all tasks in the "Task List for a Rolling Upgrade of a Cisco Unity Failover System to the Shipping 8.x Version" section.


3. Run ConfigMgr.exe on the bridgehead server to redesignate it as the bridgehead server. See the "Redesignating the Bridgehead Server for Cisco Unity 8.x" section.

4. If there are nonbridgehead Cisco Unity servers in the network: Upgrade each Cisco Unity nonbridgehead server to version 8.x:

If failover is not configured

Do Task 6. through Task 27. in the "Task List for Upgrading Cisco Unity Without Failover to the Shipping 8.x Version" section.

If failover is configured and you want to do a simultaneous upgrade

Do Task 6. through Task 29. in the "Task List for a Simultaneous Upgrade of Both Cisco Unity Failover Servers to the Shipping 8.x Version" section.

If failover is configured and you want to do a rolling upgrade

Do Task 5. through Task 31. in the "Task List for a Rolling Upgrade of a Cisco Unity Failover System to the Shipping 8.x Version" section.


5. Upgrade the voice connector. See the "Uninstalling the Voice Connector" and "Installing the Voice Connector for Bridge Networking" sections in the latest Release Notes for Cisco Unity Voice Connector for Microsoft Exchange at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Obtaining Cisco Unity License 8.x Files

License files, which enable the features purchased by the customer, are required for installing Cisco Unity software, for some upgrades, and for adding or changing licensed features. You obtain the license files by completing registration information on Cisco.com.

Shortly after registration, Cisco emails the license files. The email from Cisco contains instructions on how to save and store the files. The Cisco Unity Reconfiguration and Upgrade Guide Release 8.x later provides specific instructions on the use of the license files. (For more information on licensing, refer to the white paper Licensing for Cisco Unity (All Versions) at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.)


Note If the system is configured for failover, you install the license files only on the primary server.


The following information is required during registration:

The MAC address (physical address) for the network interface card (NIC) in the Cisco Unity server or, if a dual NIC is configured for fault tolerance, the MAC address that the two NICs share.

The product authorization key (PAK), which appears on the sticker located on the front of the sleeve for Cisco Unity DVD 1.

Do the following two procedures in the order listed.

To Get the MAC Address of the Cisco Unity Servers


Step 1 On the computer on which Cisco Unity will be installed, do one of the following:

If the server contains a dual NIC that has been configured for fault tolerance, run the NIC-configuration utility provided by the manufacturer, and write down the MAC address (excluding hyphens) that is shared by the two NICs. Then skip the rest of this procedure.

If the server does not contain a dual NIC or if the server contains a dual NIC that is not configured for fault tolerance, on the Windows Start menu, click Programs > Accessories > Command Prompt.

Step 2 In the Command Prompt window, enter ipconfig /all, and press Enter.

Step 3 Write down the value of Physical Address, excluding the hyphens, or save it to a file that you can access during online registration. (For example, if the physical address is 00-A1-B2-C3-D4-E5, record 00A1B2C3D4E5.)

If the server contains a dual NIC, two values will appear. Write down the value for the NIC that you will use to connect the Cisco Unity server to the network.

Step 4 Close the Command Prompt window.

Step 5 Repeat Step 1 through Step 4 on all of the Cisco Unity servers that you want to upgrade. When failover is configured, do these steps only on the primary server.


To Register and Obtain the License Files


Step 1 Browse to the registration website at http://www.cisco.com/go/license (URL is case sensitive).

You must be a registered user on Cisco.com to obtain license files.

Step 2 Enter the PAK or software serial number, and click Submit.

Step 3 Follow the on-screen prompts.

Step 4 Repeat Step 2 and Step 3 for every Cisco Unity that you want to upgrade.

Step 5 Shortly after registration, you will receive an email with the Cisco Unity license files.

If license files are lost, it can take up to one business day to get another copy.


If you do not receive the license files within 1 hour or to get another copy of a license file, call the Cisco Technical Assistance Center (TAC) and ask for the Licensing Team:

In the U.S.

800 553-2447

Outside
the U.S.

For your local Cisco TAC phone number, see the Cisco Worldwide Contacts page at http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.


Or open a service request using the TAC Service Request Tool at http://tools.cisco.com/ServiceRequestTool/create/DefineProblem.do.

You will need to provide information to verify Cisco Unity ownership—for example, the purchase order number or the PAK (which appears on the sticker located on the front of the sleeve for Cisco Unity DVD 1).

Downloading Software for the Upgrade to Cisco Unity 8.x


Caution If you are reinstalling all software on the Cisco Unity server (because, for example, you are upgrading from Windows 2000 Server to Windows Server 2003 or replacing the Cisco Unity server), you must get discs from Cisco. The layout of the Cisco Unity Data Store 2000 DVD has changed for Cisco Unity 8.x, and you can no longer use the Cisco Unity Data Store 2000 DVD that shipped with previous versions of Cisco Unity to install the Cisco Unity data store.

This section lists the software needed to upgrade Cisco Unity. If you do not have Cisco Unity DVDs for the currently shipping version, download all of the software listed in this section.

Note the following considerations:

The downloads may total several gigabytes. 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.

Most downloads are self-extracting executable files. When downloads are complete, extract the updates and burn DVDs that contain the extracted files. Then delete the downloaded .exe files to free disk space.

For detailed instructions on downloading software and burning DVDs, refer to the "Installation and Upgrade Information" section of the applicable release notes, available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.


Caution Until you have installed all of the recommended service packs and updates, and, optionally, Cisco Security Agent for Cisco Unity and antivirus software, third-party components installed on the Cisco Unity server have significant security vulnerabilities. Do not connect the Cisco Unity server to the network to install software. Instead, burn DVDs that contain the downloaded software, and install the software from the DVDs.

The Cisco Unity documentation instructs you when to install the software you download.


Note To access the software download page, you must be logged on to Cisco.com as a registered user.


Download the following software for all installations. Even if you have Cisco Unity DVDs for the currently shipping version, we recommend that you download the software, some of which may have been released or updated after the discs were produced.

Cisco Unity Software

Disc images for the currently shipping Cisco Unity version, including:

The Cisco Unity installation disc.

The discs for Cisco Unity languages that you want to install on the server (other that U.S. English, which is automatically installed on all systems).

The Cisco Unity Service Pack DVD for the version of Cisco Unity that you are installing.

Before you install Cisco Unity, you must install the Microsoft service packs that were required for that version of Cisco Unity. After you install Cisco Unity, you can install any later service packs that were qualified for use with Cisco Unity.

Refer to the "Downloading Software for Cisco Unity <Version>" section of the applicable Release Notes for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Latest Microsoft Service Packs and Cisco Unity Server Updates Wizard

Download the following software:

For the Microsoft software that you are installing on the Cisco Unity server, the latest service packs recommended for use with Cisco Unity, if later than the service packs shipped with Cisco Unity. Any service packs that are qualified for use with Cisco Unity after the most recent Cisco Unity release are available on the Microsoft Updates Software Download page at http://www.cisco.com/cgi-bin/tablebuild.pl/unity_msft_updates. Also download or print the installation instructions.

For a list of the service packs that are recommended, refer to the section "Recommended Service Packs—Cisco Unity Server" in the System Requirements for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/requirements/8xcusysreq.html.

The latest Cisco Unity Server Updates Wizard, which automatically installs the latest Microsoft updates for Windows, Exchange, and SQL Server or MSDE that are recommended for use with Cisco Unity. The wizard also optionally installs the latest version of the Cisco Security Agent for Cisco Unity. Available on the Microsoft Updates for Cisco Unity Software Download page at http://www.cisco.com/cgi-bin/tablebuild.pl/unity_msft_updates.

For information on the Microsoft updates and the version of Cisco Security Agent for Cisco Unity that are installed by the Server Updates Wizard, refer to Software Installed by the Cisco Unity Server Updates Wizard at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Cisco Unity Directory Walker Utility and Cisco Unity Disaster Recovery Tools

The latest versions of the Cisco Unity Directory Walker (DbWalker) utility utility and the Cisco Unity Disaster Recovery tools (DiRT). DbWalker is used to check the consistency of and correct errors in the Cisco Unity database before the upgrade. DiRT is used to back up Cisco Unity data before the upgrade and to restore Cisco Unity data, if necessary. (All are included on the Cisco Unity discs, but updates are posted regularly to the Cisco Unity Tools website.)

DbWalker for Cisco Unity 4.x and later is available at http://www.ciscounitytools.com/Applications/Unity/dbWalker/dbWalker.html. DiRT is available at http://www.ciscounitytools.com/Applications/Unity/DIRT/DIRT.html.

Cisco Unity Permissions Wizard

The latest version of the Cisco Unity Permissions wizard. The Permissions wizard for Cisco Unity 5.0(1) and later is available at http://www.ciscounitytools.com/Applications/Unity/PermissionsWizard/Unity50/PW50.html.

Extending the Active Directory Schema for Cisco Unity 8.x

Several changes to the Active Directory schema are required 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, and view the file Avdirmonex2k.ldf.

Changes to the Active Directory schema may take 15 minutes or more to replicate throughout the forest. These changes must finish replicating before you can install Cisco Unity.

To Extend the Active Directory Schema


Step 1 Confirm that all domain controllers are on line. (The Active Directory schema extensions replicate only when all domain controllers are on line.)

Step 2 On the computer that has the schema master role (typically the first DC/GC in the forest), log on to Windows as a user who is a member of the Schema Admins group.

Step 3 On Cisco Unity DVD 1, browse to the directory ADSchemaSetup, and double-click ADSchemaSetup.exe.

Step 4 In the Active Directory Schema Setup dialog box, check the Exchange Directory Monitor check box.

Step 5 If you have ever used, are currently using, or plan to use VPIM Networking or Bridge Networking, check the applicable boxes.


Caution If the schema has ever been updated with Bridge Connector and/or VPIM Connector extensions (for Bridge Networking and VPIM Networking, respectively) from an earlier version of Cisco Unity, you must update those extensions and the Directory Monitor extensions even if you are no longer using the Bridge or VPIM.

Step 6 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 these files to confirm that the extension completed successfully.


Installing Exchange 2003 Service Pack 2 for Cisco Unity 8.x

Do the procedure in this section to install Exchange 2003 Service Pack 2 on the following servers:

The Cisco Unity server. If failover is configured, both the primary and secondary Cisco Unity servers.

Also install Exchange 2003 Service Pack 2 on the Cisco Unity server when the server is running only Exchange 2003 System Manager.

The partner Exchange server.

The Exchange servers on which Cisco Unity subscribers are homed.

To Install Exchange 2003 Service Pack 2


Step 1 On Cisco Unity Service Packs DVD 1, browse to the directory Exchange_2003_SP1\Setup\I386, and double-click Update.exe.

Step 2 Follow the on-screen prompts to complete the installation.

Step 3 Restart the server.

Step 4 If you have not already done so, repeat this procedure on the partner Exchange server and on every Exchange 2003 server on which Cisco Unity subscriber mailboxes are homed.


Checking the Consistency of the Cisco Unity Database for the Upgrade to 8.x

Before you upgrade Cisco Unity, we recommend that you run the DbWalker utility to check the consistency of the Cisco Unity database. Running DbWalker fixes most minor errors automatically and flags any major errors.

On a system with a few hundred subscribers, running DbWalker takes only a few minutes. However, on a large system, running DbWalker may take several hours. The duration depends on the speed of the processor, the amount of RAM in the server, the number of calls that Cisco Unity is taking, and other variables.

To Check the Consistency of the Cisco Unity Database


Step 1 On the Cisco Unity server, install the latest version of DbWalker, if it is not already installed.

If Cisco Unity failover is configured, do this procedure on the primary server.

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.)


Backing Up Cisco Unity Data for the Upgrade to 8.x

We also recommend that you back up Cisco Unity data by using the Disaster Recovery Backup tool. Running the tool takes only a few minutes, and having a DiRT backup allows you to restore Cisco Unity data easily, if necessary.

If you choose to back up messages as well as Cisco Unity data, backing up takes longer, the size of the backup is significantly larger, and the account with which you log on to Windows requires additional permissions. Refer to DiRT Help for detailed information.

To Back Up Cisco Unity Data


Step 1 On the Cisco Unity server, install the latest versions of DiRT, if the tools are not already installed.

If Cisco Unity failover is configured, do this procedure on the secondary server.

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 If failover is configured, do not back up the primary server unless the secondary server is unavailable. If you restore from a backup of the primary server, you must also perform an additional procedure for Cisco Unity failover to function correctly. For more information, see "Working With Systems Configured For Failover" in DiRT Help.

Disabling the TUI Menu Option for Changing Subscriber Settings in Custom Conversations for the Upgrade to 8.x

If your system uses only the following conversations, skip this section:

Standard Conversation

Optional Conversation 1

Alternate Keypad Mapping N

Alternate Keypad Mapping S

Alternate Keypad Mapping X

For systems that use a custom conversation created through the Custom Key Map Tool, this section describes the steps to prevent access to subscriber options through the phone user interface (TUI) so subscribers cannot change their personal settings such as a new recorded name or a new greeting.


Caution You must disable the TUI menu option for changing subscriber settings on all customized subscriber conversations. Otherwise, changes made to subscriber settings through the TUI may be lost.

Note the following:

During the upgrade, subscribers will be able to listen to and send voice messages.

At the end of the upgrade, the changes to the custom subscriber conversation will be reversed.

To Disable TUI Menu Options for Changing Subscriber Settings in Custom Conversations


Step 1 On the primary server, on the desktop, double-click Cisco Unity Tools Depot.

Step 2 In the Tools Depot window, in the left pane, expand Administration Tools.

Step 3 Double-click Custom Key Map.

Step 4 In the Editing - Custom Keypad Mapping window, on the Select Key Map menu, click a custom key map that subscribers are using.

Step 5 Click the Main Menu tab.

Step 6 In the left pane, click Change Setup Options.

Step 7 Under Key Map, select the number and press Delete so the field is blank and press Enter.

Step 8 Click Save.

Step 9 Repeat Step 4 through Step 8 for all remaining custom conversations that subscribers use.

Step 10 Click Exit.

Step 11 Close the Editing - Custom Keypad Mapping window.


Manually Failing Over, and Disabling Automatic Failover and Failback for the Upgrade to 8.x

This section contains procedures for disabling automatic failover and failback, and for manually initiating failover while the automatic functions are disabled.

Note that when automatic failover and failback are disabled:

File replication is also disabled.

You must manually force a server to become active or inactive by using the Failover Monitor.

If you restart the primary and secondary servers while automatic failover and failback are disabled, both servers start as inactive, so Cisco Unity is not able to take calls.


Note When you disable automatic failover and failback, the primary server never fails over to the secondary server even if the primary server stops taking calls. In addition, the secondary server never fails back to the primary server even if you have specified a schedule for automatic failback.


To Manually Initiate Failover to the Secondary Server


Step 1 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.

Step 4 To maintain Cisco Unity functionality for all subscribers, do the tasks in the following sections as applicable:

"Notifying Subscribers of the Active Server and the URLs to Use for Accessing Cisco Unity Web Applications" section in the "Tasks Required When Failover or Failback Occurs in Cisco Unity 8.x" chapter of the Failover Configuration and Administration Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/failover/guide/8xcufgx.html.

"T1 Integrations Through Voice Cards: Enabling the Phone System to Send Calls to the Active Server After Failover or Failback Occurs" section in the "Tasks Required When Failover or Failback Occurs in Cisco Unity 8.x" chapter of the Failover Configuration and Administration Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/failover/guide/8xcufgx.html.


To Disable Automatic Failover and Failback


Step 1 On the primary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.

Step 2 Click Advanced.

Step 3 Check the Disable Automatic Failover and Failback check box.

Step 4 Click OK.


Stopping and Disabling the World Wide Web Publishing Services on the Primary and Secondary Servers for the Upgrade to 8.x

This section describes the steps to prevent access to Cisco Unity Administrator and the Cisco Personal Communications Assistant so changes to the Cisco Unity database cannot be made.


Caution We recommend that you stop and disable the World Wide Web Publishing Services. Otherwise, changes made through the Cisco Unity Administrator and the Cisco Personal Communications Assistant during the rolling upgrade process may be lost.


Note After doing this procedure, subscribers and administrators will not be able to access the Cisco Unity Administrator and the Cisco Personal Communications Assistant.


To Stop and Disable the World Wide Web Publishing Services on the Primary and Secondary Servers


Step 1 On the primary server, on the Windows Start menu, click Programs > Administrative Tools > Component Services.

Step 2 In the Component Services window, in the right pane, double-click World Wide Web Publishing Services.

Step 3 In the World Wide Web Publishing Services Properties dialog box, in the Startup Type list, click Disabled.

Step 4 Click Stop and click OK.

Step 5 On the secondary server, repeat Step 1 through Step 4.


Setting Permissions on an Active Directory Location by Using the Permissions Wizard for the Upgrade to 8.x

You rerun the Permissions Wizard to update the permissions on the Active Directory location where Cisco Unity automatically creates Bridge and/or VPIM subscribers, if it is different from the location where Cisco Unity creates regular subscribers. If Cisco Unity is configured to automatically create both Bridge and VPIM subscribers in different locations, do the following procedure for the Bridge subscriber location, and repeat the procedure for the VPIM subscriber location.

Run the Permissions wizard during off-peak hours. Beginning with Cisco Unity 4.2(1), the Permissions wizard sets permissions at a more granular level than previous versions did, which requires more changes to the Active Directory database.


Caution When the Permissions wizard completes, the Lsass.exe process updates the Active Directory database with the new permissions. While Lsass.exe is processing the updates, it uses 100% of available processor time on the root domain controller in the domain and on one of the global catalog servers in the site where the Permissions wizard was run. (Other domain controllers in the domain and other global catalog servers in the forest are also affected, but the impact is less significant.) The updates take a few minutes to several hours, depending on the size of the database. Do not continue with the Cisco Unity upgrade until Lsass.exe has finished processing the changes, or Cisco Unity Setup may fail.

To Set Permissions on the AD Location by Using the Permissions Wizard


Step 1 If you downloaded the latest version of Permissions wizard from CiscoUnityTools.com, install and run that version. Otherwise, run the version that appears in the Utilities\PermissionsWizard directory on the shipping Cisco Unity DVD.

Step 2 Click Next without changing any options until you arrive at the Choose Active Directory Containers for New Objects page.

Step 3 Choose the domain and the applicable container or organizational unit in which Cisco Unity automatically creates Bridge or VPIM subscribers.

Note The Permissions wizard only has the ability to grant permissions—it does not remove any permissions. Following this procedure will add the necessary permissions on the container or OU that you select, but will not remove permissions that are already granted on other containers for Cisco Unity.

Step 4 Click Next and follow the prompts to complete the Permissions wizard.


Disabling Antivirus and Cisco Security Agent Services for the Upgrade to 8.x


Note If the system is not using antivirus software or Cisco Security Agent for Cisco Unity, skip this section.


You disable antivirus and Cisco Security Agent services on the server so that they do not slow down the installation of software or cause the installations to fail. The Cisco Unity Reconfiguration and Upgrade Guide alerts you when to re-enable the services after all of the installation procedures that can be affected are complete.

To Disable and Stop Antivirus and Cisco Security Agent Services


Step 1 Refer to the antivirus software documentation to determine the names of the antivirus services.

Step 2 On the Windows Start menu, click Programs > Administrative Tools > Services.

Step 3 Disable and stop each antivirus service and the Cisco Security Agent service:

a. In the right pane, double-click the service.

b. On the General tab, in the Startup Type list, click Disabled. This prevents the service from starting when you restart the server.

c. Click Stop to stop the service immediately.

d. Click OK to close the Properties dialog box.

Step 4 When the services have been disabled, close the Services MMC.


Installing Software Prerequisites and Verifying Network Prerequisites for the Upgrade to 8.x

The Cisco Unity System Setup Assistant includes a Software Prerequisites task that helps customize the platform for Cisco Unity by checking for and installing Windows components, Microsoft service packs and updates, and other software required by Cisco Unity. (For a detailed list, refer to Components and Software Installed by the Cisco Unity Platform Configuration Discs and the Cisco Unity System Setup Assistant at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/pcd/cupcd.html.)

The Cisco Unity System Setup Assistant also includes a Network Prerequisites task that verifies network prerequisites, for example, the presence of an Active Directory domain controller and global catalog server.


Caution For limitations on running the Cisco Unity System Setup Assistant by using Windows Terminal Services, see the "Windows Terminal Services" section of the "Limitations and Restrictions" section of the applicable Cisco Unity release notes at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

If a Microsoft AutoMenu window appears while the Cisco Unity System Setup Assistant is installing an application, close the window and allow the assistant to continue.

To Install Software Prerequisites and Verify Network Prerequisites


Step 1 Log on to Windows by using an Active Directory domain account that is a member of the local Administrators group.


Caution If you have not already done so, disable antivirus services on the server, if applicable. Otherwise, the upgrade may fail.

Step 2 If Cisco Unity DVD 1, the Cisco Unity Prerequisites DVD, or the Cisco Unity Data Store DVD is located on a network share, authenticate on the other server before you continue. For example, start Windows Explorer, browse to the network share, and, when prompted, enter the username and password for an Active Directory account that has access to that location.

Step 3 If Internet Explorer Enhanced Security is enabled on the Cisco Unity server, add the network share as a local intranet site in Internet Explorer.

Step 4 On Cisco Unity DVD 1, browse to the root directory, and double-click Setup.exe.

Step 5 If prompted, double-click the language of your choice to continue the installation.

Step 6 Verify that Software Prerequisites is selected, and click Run Task.

Step 7 On the Choose Your Configuration page, set the following fields:

<x> Ports to Be Installed

Enter the number of voice ports that you are connecting with the Cisco Unity server.

This Server Is a Primary or Secondary Server in a Failover Pair

Check the This Is a Primary or Secondary Failover Server check box if the system is using failover.

Choose the Exchange Version and the Location of the Partner Exchange Server

Choose the Exchange version and the location of the partner Exchange server.


Step 8 Click Next. The assistant lists the applicable prerequisites and indicates whether or not they are met.

Step 9 Follow the on-screen prompts to finish installing prerequisites.

If a Microsoft AutoMenu window appears when the assistant is installing an application, close the window and allow the assistant to continue.

Step 10 When the Software Prerequisites task has completed, click Finish.

Step 11 In Cisco Unity System Setup Assistant, click Network Prerequisites, and click Run Task.

Step 12 Follow the on-screen prompts to complete the verification.


Upgrading and Configuring Cisco Unity 8.x Software

To upgrade and configure Cisco Unity software, you use the Cisco Unity System Setup Assistant. Do the following procedure.


Caution For limitations on running the Cisco Unity System Setup Assistant by using Windows Terminal Services, see the "Windows Terminal Services" section of the "Limitations and Restrictions" section of the applicable Cisco Unity release notes at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

To Upgrade and Configure the Cisco Unity Software


Step 1 Log on to Windows by using the Cisco Unity installation account.


Caution If you have not already done so, disable virus-scanning and Cisco Security Agent services on the server, if applicable. Otherwise, the installation may fail.

Step 2 On Cisco Unity DVD 1, browse to the root directory and double-click Setup.exe.

Step 3 Click Install or Upgrade Cisco Unity Software, and click Run Task.

Step 4 On the Cisco Unity System Setup Assistant Welcome page, click Next.

Step 5 To acknowledge the cryptographic export warning, click Next.

Step 6 On the Install or Update License Files page, do the following steps:

a. Click Next.

b. On the Welcome page, click Next.

c. Click Add.

d. On the Add or Remove License Files page, add or remove the applicable license files:

If you are installing the upgrade license file on a non-failover Cisco Unity server, browse to the location of the upgrade license file, and double-click the license file name.

If you are installing the upgrade license file on the primary Cisco Unity server in a failover configuration, browse to the location of the upgrade license file, and double-click the license file name.

If you are installing a license file on the Cisco Unity secondary server in a failover configuration, remove the default license file for the current version of Cisco Unity: CiscoUnity40.lic, CiscoUnity50.lic, or CiscoUnity70.lic. Then browse to the CommServer\Licenses directory on the Cisco Unity installation disc, and add CiscoUnity80.lic.


Note When the Cisco Unity upgrade was registered on Cisco.com, Cisco replied with an email containing attached file(s) with license(s) for the Cisco Unity upgrade and for additional features, if applicable. The instructions in the email directed that the attached files be saved. For more information, see the "Obtaining Cisco Unity License 8.x Files" section.


e. Follow the on-screen prompts to finish the wizard.

Step 7 If you already checked the consistency of the Cisco Unity database by using DbWalker, as recommended in the "Checking the Consistency of the Cisco Unity Database for the Upgrade to 8.x" section, or if you are upgrading the secondary server in a failover configuration, click Skip DbWalker, click Next, and skip to Step 8.

If you have not checked the consistency of the Cisco Unity database recently, we recommend that you do so now. On a system with a few hundred subscribers, running DbWalker takes only a few minutes. However, on a large system, running DbWalker may take several hours. The duration depends on the speed of the processor, the amount of RAM in the server, the number of calls that Cisco Unity is taking, and other variables. Click Run DbWalker, click Next, and follow the on-screen prompts.

Step 8 If you are upgrading the primary server in a failover configuration, the option to use DiRT to back up Cisco Unity data is not available.

If you have already backed up Cisco Unity data by using the Disaster Recovery Backup tool, as recommended in the "Backing Up Cisco Unity Data for the Upgrade to 8.x" section, click Skip DiRT Backup, click Next, and skip to Step 9.

If you have not backed up Cisco Unity data recently, we recommend that you do so now. Running the Disaster Recovery Backup tool takes only a few minutes, and having a DiRT backup allows you to restore Cisco Unity data easily, if necessary. Click Run DiRT Backup, click Next, and follow the on-screen prompts.

Step 9 On the Cisco Unity Setup page, click Next.

Step 10 In Cisco Unity Setup:

a. Click Next or Continue without changing values until the Select Features dialog box appears.

b. In the Select Features dialog box:

Check the Upgrade Cisco Unity check box.

If the Cisco Unity license includes text to speech, check the Enable TTS check box.

If not, uncheck the Enable TTS check box.

c. Click Next without changing values until you are prompted to restart the Cisco Unity server.


Caution Do not cancel Cisco Unity Setup, or you may have to uninstall and reinstall Cisco Unity. In some cases, nothing may appear to be happening for long periods. To confirm that Cisco Unity Setup is still working, right-click the Windows taskbar and click Task Manager, then the Processes tab and Image Name (to sort by process name), and find Setup.exe. It should be using more than 0% of the CPU.

d. Follow the on-screen prompts, and restart the Cisco Unity server when prompted.

Check the Restart the Server Now check box, and click Next.

Step 11 After the restart, the Configure Cisco Unity Services page in the Cisco Unity System Setup Assistant automatically appears. Click Next.

Step 12 In the Services Configuration wizard, follow the on-screen prompts to configure Cisco Unity services.

Step 13 Confirm that the message store server is running. If the message store server is not running, configuring the message store will fail.

Step 14 In the Cisco Unity System Setup Assistant, on the Configure the Cisco Unity System for the Message Store page, click Next.

Step 15 In the Message Store Configuration Wizard, follow the on-screen prompts to configure Cisco Unity for the message store.

Step 16 Click Finish to exit the Install or Upgrade Cisco Unity Software task.

Step 17 Click Close to close the Cisco Unity System Setup Assistant.


Installing the Latest Microsoft Service Packs for Cisco Unity 8.x

You install the latest Microsoft service packs that has been qualified for use with Cisco Unity, if any, as well as the corresponding updates, to enhance the security of the Cisco Unity server. Do the following procedures.

To Install the Latest Microsoft Service Packs, If Any


Follow the instructions that you printed or downloaded when you downloaded the service pack.


Installing Microsoft Updates and Cisco Security Agent for Cisco Unity for 8.x

You run the Cisco Unity Server Updates wizard on the Cisco Unity Post-Install DVD to install the Microsoft updates that apply to Cisco Unity and, optionally, to install Cisco Security Agent for Cisco Unity. (If you do not have Cisco Unity discs, you downloaded the Cisco Unity Server Updates wizard in the "Downloading Software for the Upgrade to Cisco Unity 8.x" section.)

If Cisco Security Agent for Cisco Unity is already installed on the server, you must disable and uninstall it before you can install the latest version. For more information, see the Release Notes for Cisco Security Agent for Cisco Unity for the version of Cisco Security Agent for Cisco Unity currently installed. Release notes are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

To Install Microsoft Updates and, Optionally, Cisco Security Agent for Cisco Unity


Step 1 Insert in the Cisco Unity Post-Install disc in the drive.

Step 2 Run ServerUpdatesWizard.exe.

Step 3 Follow the on-screen prompts to complete the installation of Microsoft updates and, optionally, Cisco Security Agent for Cisco Unity.


Note If you are accessing the server by using Remote Desktop or a VNC client, and you are installing Cisco Security Agent for Cisco Unity, the Remote Desktop or VNC session will be disconnected when Cisco Security Agent for Cisco Unity restarts the network interface. If the session does not reconnect automatically, reconnect manually to finish the Server Updates wizard.


Step 4 Restart the Cisco Unity server.


Re-enabling Antivirus and Cisco Security Agent Services for Cisco Unity 8.x

You re-enable virus-scanning and Cisco Security Agent services now that all of the software installations that could have been affected if the services were running are complete.

If you installed Cisco Security Agent for Cisco Unity when you ran the Server Updates wizard, you do not need to re-enable or start it.

To Re-enable and Start Antivirus and Cisco Security Agent Services


Step 1 Refer to the virus-scanning software documentation to determine the names of the virus-scanning services.

Step 2 On the Windows Start menu, click Programs > Administrative Tools > Services.

Step 3 Re-enable and start each virus-scanning service and the Cisco Security Agent service:

a. In the right pane, double-click the service.

b. On the General tab, in the Startup Type list, click Automatic to re-enable the service.

c. Click Start to start the service.

d. Click OK to close the Properties dialog box.

Step 4 When the services have been re-enabled, close the Services MMC.


Configuring Internet Explorer to Display the Cisco Unity Administrator in 8.x

If you created a Cisco Unity administration account as recommended by the Installation Guide for Cisco Unity, and if you log on to Windows by using that account, the changes that Windows Server 2003 Service Pack 1 makes to default Internet Explorer security settings cause the Cisco Unity Administrator to display a blank page. Do the following procedure to configure Internet Explorer to display the Cisco Unity Administrator when you log on to Windows using the administration account.

To Configure Internet Explorer to Display the Cisco Unity Administrator


Step 1 Log on to the Cisco Unity server using the Cisco Unity administration account.

Step 2 Right click the Cisco Unity icon in the system tray, and click Launch System Admin.

Step 3 If you are prompted to provide a user name and password, click Cancel.

Step 4 On the Internet Explorer Tools menu, click Internet Options.

Step 5 Click the Security tab.

Step 6 Under Select a Web Content Zone to Specify Its Security Settings, click the Trusted Sites icon.

Step 7 Click Sites.

Step 8 In the Trusted Sites dialog box, in the Add This Website to the Zone field, enter the applicable value depending on whether the Cisco Unity Administrator is set up to use SSL:

If the Cisco Unity Administrator is set up to use SSL

Enter https:\\<CiscoUnityServerName>

If the Cisco Unity Administrator is not set up to use SSL

Enter http:\\<CiscoUnityServerName>


Step 9 If the Cisco Unity Administrator is set up to use SSL, check the Require Server Verification (https:) for All Sites in This Zone check box. If not, uncheck the check box.

Step 10 Click Add.

Step 11 Click Close to close the Trusted Sites dialog box.

Step 12 On the Security tab, click Custom Level.

Step 13 In the Security Settings dialog box, change the value of the Reset To list to Low.

Step 14 Click Reset, and click Yes to confirm that you want to change the security settings for this zone.

Step 15 Click OK to close the Security Settings dialog box.

Step 16 If the Security Settings dialog box does not close:

a. Close the dialog box by clicking the X in the upper-right corner.

b. In the "not responding" message box, click End Now. (The "not responding" message box may take a few seconds to appear.)

Step 17 Restart the Cisco Unity Administrator.


Enabling and Starting the World Wide Web Publishing Services on the Primary and Secondary Servers for Cisco Unity 8.x

This section describes the steps to re-enable access to Cisco Unity Administrator and the Cisco Personal Communications Assistant so changes to the Cisco Unity database can be made again.

To Enable and Start the World Wide Web Publishing Services on the Primary and Secondary Servers


Step 1 On the primary server, on the Windows Start menu, click Programs > Administrative Tools > Component Services.

Step 2 In the Component Services window, in the left pane, double-click World Wide Web Publishing Services.

Step 3 In the World Wide Web Publishing Services Properties dialog box, in the Startup Type drop-down box, click Automatic, then click Apply.

Step 4 Click Start and click OK.

Step 5 Repeat Step 1 through Step 4 on the secondary server.


Re-enabling the TUI Menu Option for Changing Subscriber Settings in Custom Conversations for Cisco Unity 8.x

For systems that use a custom conversation created through the Custom Key Map Tool, this section describes the steps to re-enable access to subscriber options through the telephony user interface (TUI) so subscribers can change their personal settings again such as a new voice name or a new greeting.

To Re-enable TUI Menu Options for Changing Subscriber Settings


Step 1 On the primary server, on the desktop, double-click Cisco Unity Tools Depot.

Step 2 In the Tools Depot window, in the left pane, expand Administration Tools.

Step 3 Double-click Custom Key Map.

Step 4 In the Editing - Custom Keypad Mapping window, on the Select Key Map menu, click a custom key map that subscribers are using.

Step 5 Click the Setup tab.

Step 6 In the left pane, click Change Setup Options.

Step 7 Under Key Map, enter the key that was originally assigned to this menu.

Step 8 Click Save.

Step 9 Repeat Step 4 through Step 8 for all remaining custom conversations that subscribers use.

Step 10 Click Exit.

Step 11 Close the Editing - Custom Keypad Mapping window.


Securing the Example Administrator and Example Subscriber Accounts Against Toll Fraud in Cisco Unity 8.x

It is possible for a malicious user to dial into Cisco Unity, log on as the Example Administrator or Example Subscriber by using the default extension and password, and configure Cisco Unity to forward calls to phone numbers for which there are charges or to reconfigure greetings so an operator believes the messaging system is personally accepting collect-call charges. To help secure Cisco Unity against toll fraud, we strongly recommend that you change the phone password for both accounts after Cisco Unity is installed.

Although the Example Subscriber account is no longer created during Cisco Unity installation in versions 4.0(3) and later, you may still have an Example Subscriber account from an earlier version, as the account is not removed during the upgrade process.

(For information on the accounts, refer to the "About Default Accounts" section in the "Messaging and Default Accounts Overview in Cisco Unity 8.x" chapter of the System Administration Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/administration/guide/8xcusagx.html.

To Change the Password on the Example Administrator and Example Subscriber Accounts


Step 1 In the Cisco Unity Administrator, go to any Subscribers > Subscribers page.

Step 2 Click the Find icon.

Step 3 On the Find and Select Subscriber page, click Find.

Step 4 Click Example Administrator.

Step 5 In the left pane, click Phone Password.

Step 6 In the right pane, check the User Cannot Change Password check box.

Step 7 Check the Password Never Expires check box.

Step 8 Under Reset Phone Password, enter and confirm a new password by using digits 0 through 9.

We recommend that you enter a long and nontrivial password; 20 digits or more is desirable. (The minimum length of the password is set on the Subscribers > Account Policy > Phone Password Restrictions page.) In a nontrivial password:

The digits are not all the same (for example, 9999).

The digits are not consecutive (for example, 1234).

The password is not the same as the extension assigned to the example account.

The password does not spell the name of the example account, the name of the company, the name of the IT manager, or any other obvious words.

Step 9 Click the Save icon.

 

Step 10 Click the Find icon.

Step 11 On the Find and Select Subscriber page, click Find.

Step 12 Click Example Subscriber.

Step 13 Repeat Step 5 through Step 9 for Example Subscriber.

Step 14 Close the Cisco Unity Administrator.


Hardening the Cisco Unity 8.x Server

We strongly recommend that you secure Cisco Unity and the Cisco Unity server. Refer to the Security Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/security/guide/8xcusecx.html.

Redesignating the Bridgehead Server for Cisco Unity 8.x

Run the ConfigMgr.exe utility with the Create Bridge Account option to redesignate the server as the bridgehead. (The CsBridgeConnector service will not start, and the Cisco Unity Administrator will not display Bridge-related pages until ConfigMgr.exe has been run.)

To Redesignate the Bridgehead Server


Step 1 On the Cisco Unity server, browse to the directory in which Cisco Unity is installed (the default location is C:\CommServer).

Step 2 Double-click ConfigMgr.exe. The ConfigMgr dialog box appears.

Step 3 Click Create Bridge Account.

Step 4 Click OK in the dialog box that displays after the configuration has completed.

Step 5 Close the ConfigMgr dialog box.