Table Of Contents
Upgrading the Cisco Unity System from Version 2.x to 3.0
Upgrade Methods
Upgrade by Using Cisco Unity Version 3.0(2) or Later
Upgrades from Cisco Unity Versions Earlier than 2.3(4.104) Are Not Supported
System Key
Duration of Upgrade
Data from Duration Tests
Task List for Reinstalling All Software on an Existing Server
Task List for Setting Up a New Server
Task List for Upgrading an Existing Server
Reviewing the Consistency of the Cisco Unity 2.x Database
Exporting Data from Cisco Unity
Data That Is Exported
Data That Is Not Exported, and Data That Is Exported but Not Imported
Installing and Running the Cisco Unity Database Export Utility
Removing Voice Card Software
Dialogic Software
Voice Technologies Group Software
Natural MicroSystems Software
Removing ActiveFax
Uninstalling Cisco Unity Version 2.x
The Cisco Unity Uninstaller Utility
Option to Skip Removal of Exchange Objects
Installing and Running the Cisco Unity Uninstaller Utility
LDAP Port Error with the Cisco Unity Uninstaller Utility
Importing Windows NT/Active Directory Accounts into Exchange 5.5 (Selected Configurations Only)
Importing Data Back into Cisco Unity
The Import Process
Installing and Running the Cisco Unity Database Import Utility
Re-entering Custom Data
Deleting Unneeded Cisco Unity Subscribers
Resetting Custom Settings
Importing Public Distribution Lists
Resetting the Dialogic Quiet Parameter
Upgrading the Cisco Unity System from Version 2.x to 3.0
Your upgrade tasks depend on the method you choose to upgrade the Cisco Unity system from version 2.x to version 3.0. Use the task list for your upgrade method to upgrade the Cisco Unity system correctly.
This chapter contains the following sections:
•
Upgrade Methods
•Upgrade by Using Cisco Unity Version 3.0(2) or Later
•Upgrades from Cisco Unity Versions Earlier than 2.3(4.104) Are Not Supported
•System Key
•Duration of Upgrade
•Task List for Reinstalling All Software on an Existing Server
•Task List for Setting Up a New Server
•Task List for Upgrading an Existing Server
•Reviewing the Consistency of the Cisco Unity 2.x Database
•Exporting Data from Cisco Unity
•Removing Voice Card Software
•Removing ActiveFax
•Uninstalling Cisco Unity Version 2.x
•Importing Windows NT/Active Directory Accounts into Exchange 5.5 (Selected Configurations Only)
•Importing Data Back into Cisco Unity
•Re-entering Custom Data
Upgrade Methods
There are three methods for upgrading a Cisco Unity system from version 2.x to version 3.0. Use the task list for your upgrade method to upgrade the Cisco Unity system correctly.
The following list describes the conditions for each method and references the applicable task list:
Reinstall all software
on an existing server
|
Use this method when the Cisco Unity server is currently running Windows NT 4.0—which you must upgrade to Windows 2000—or when you want to upgrade Exchange 5.5 to Exchange 2000. Use the Task List for Reinstalling All Software on an Existing Server.
|
Set up a new server
|
Use this method when you are replacing the existing server. You transfer data from the existing server to the new server. A benefit of this method is that the existing server can answer calls while you do much of the setup on the new server. Use the Task List for Setting Up a New Server.
|
Upgrade an existing
server
|
We strongly recommend that you use this method only when the server is currently running Windows 2000 and you are not upgrading from Exchange 5.5 to Exchange 2000. (Otherwise, we recommend reinstalling all software.) Use the Task List for Upgrading an Existing Server.
|
Caution Upgrading Windows NT 4.0 to Windows 2000 and Exchange 5.5 to Exchange 2000 are complex processes (for upgrade information, refer to the Microsoft website). Field experience has shown that there are significant challenges associated with upgrading an existing Exchange 5.5 site to Exchange 2000. Rather than upgrade Windows and Exchange with Cisco Unity on the server, we recommend reinstalling all software—which will be faster and more successful. Cisco TAC does not provide support for upgrading Exchange 5.5 to Exchange 2000.
Upgrade by Using Cisco Unity Version 3.0(2) or Later
The Cisco Unity 3.0(2) patch release includes significant performance enhancements to the upgrade tools. If you do not have compact discs for Cisco Unity version 3.0(2) or later, download the patch release from the Cisco Software Center website at http://www.cisco.com/cgi-bin/tablebuild.pl/unity.
Upgrades from Cisco Unity Versions Earlier than 2.3(4.104) Are Not Supported
The Cisco Unity Database Export and Database Import utilities, which let you export subscriber and other information from a 2.x system and import it into a 3.0 system, do not work on Cisco Unity systems earlier than version 2.3(4.104). To upgrade one of these systems, you need to import subscribers from Exchange or from a CSV file. Refer to the "Creating Subscriber Accounts" chapter of the Cisco Unity System Administration Guide.
System Key
Customers with Cisco Unity version 2.3 or earlier must get a new system key to run Cisco Unity version 3.0.
Customers with Cisco Unity version 2.3(4.104) or later need an activation code to upgrade the system key during Cisco Unity Setup.
Duration of Upgrade
The amount of time required to upgrade from Cisco Unity version 2.x to 3.0 depends on a number of variables. The following list is a very broad estimate of the duration of an upgrade:
Installing the operating system and other
third-party software
|
About 6 hours, depending on complexity of installation.
|
Exporting data from Cisco Unity 2.x, uninstalling
Cisco Unity 2.x, and importing data into
Cisco Unity 3.0
|
See duration data in Table 3-1.
|
Reintegrating the upgraded Cisco Unity server
with the phone system
|
About 2 hours.
|
Testing
|
About 2 hours.
|
Data from Duration Tests
To test the duration of exporting data, uninstalling Cisco Unity 2.x, and importing data into Cisco Unity 3.0, we upgraded from Cisco Unity 2.4(6) on a server with an Intel Pentium II 450 MHz processor, 512 MB of RAM, and no other system activity.
The duration of these tasks will vary depending on the speed of the processor and the amount of RAM in the Cisco Unity server. In addition, for Unified Messaging configurations in which Cisco Unity subscribers are homed on other Exchange servers, the duration will vary depending on the speed of the network.
We used three databases for our tests:
Database 1
|
1,150 objects: 500 mail users, 500 subscriber call handlers, 100 other call handlers, other default and random objects.
|
Database 2
|
3,300 objects: 1,500 mail users, 1,500 subscriber call handlers, 250 other call handlers, other default and random objects.
|
Database 3
|
5,300 objects: 2,500 mail users, 2,500 subscriber call handlers, 250 other call handlers, other default and random objects.
|
All mail users had three greetings and a recorded name, and all call handlers had three greetings. Table 3-1 lists the resulting duration data.
The number of objects on your system appears in the Cisco Unity Database Export utility before you run the export.
Table 3-1 Duration Data
Database
|
Duration of Export and
Size of Exported Database
|
Duration of Uninstallation
|
Duration of Import
|
1
|
12 min.
121 MB
|
20 min.
|
Exchange 2000: 1 hr. 27 min.
Exchange 5.5: 49 min.
|
2
|
28 min.
352 MB
|
1 hr. 3 min.
|
Exchange 2000: 4 hr. 50 min.
Exchange 5.5: 2 hr. 44 min.
|
3
|
60 min.
558 MB
|
1 hr. 29 min.
|
Exchange 2000: 9 hr. 32 min.
Exchange 5.5: 7 hr. 0 min.
|
Task List for Reinstalling All Software on an Existing Server
Some tasks apply only to particular configuration types, and are noted as such. If a task does not apply to your situation, skip it.
Caution If you plan to change the phone system integration (for example, by changing from a traditional phone system to Cisco CallManager), do not make any changes until you set up the integration in Step
29. If you change the integration too soon, subscriber and call handler settings will not match integration settings, and transfers will fail.
1. Verify system requirements for the Cisco Unity 3.0 system. Refer to Cisco Unity 3.0 System Requirements, and Supported Hardware and Software at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/30_sysrq.htm.
2. Confirm that a Cisco Unity activation code is available (the code is provided when the software is registered). If the Information Services manager has not already registered Cisco Unity, do so now. See the "Cisco Unity Activation Code" section.
3. Generate and print reports on data for the existing Cisco Unity system, if applicable. Refer to the "Reports" chapter of the Cisco Unity System Administration Guide.
Caution The Cisco Unity Database Export utility does not export data that Cisco Unity uses to generate reports. In addition, when you reinstall all software on an existing server, you delete all the existing Cisco Unity software and data, including data that Cisco Unity uses to generate reports. If you want any reports from the existing Cisco Unity system, generate them now.
4. Review the consistency of the Cisco Unity 2.x database, and fix any errors. See the "Reviewing the Consistency of the Cisco Unity 2.x Database" section.
5. Back up the Cisco Unity server completely by using BackupExec or another Exchange-aware backup utility. In addition, if you are upgrading a Cisco Unity system that was installed in the Unified Messaging in an Existing Exchange Site configuration, back up the Exchange servers that are home servers for Cisco Unity subscribers.
For information on using BackupExec to back up the Cisco Unity server, refer to the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide. For information on using another backup utility, refer to the manufacturer documentation.
Caution The Cisco Unity Database Export utility does not back up messages or other Exchange-specific data. You must back up by using an Exchange-aware backup utility.
6. Write down the existing Cisco Unity data that will not be exported or cannot be imported, then do the export. See the "Exporting Data from Cisco Unity" section.
7. Unified Messaging in an Existing Exchange Site only: Uninstall Cisco Unity 2.x. See the "Uninstalling Cisco Unity Version 2.x" section.
Caution You must uninstall Cisco Unity to remove Cisco Unity properties from Exchange users throughout the Exchange site. Otherwise, you will have to manually remove Cisco Unity properties from each Exchange user in raw mode before you can create subscriber accounts on the upgraded Cisco Unity server by importing mail users into Exchange.
8. Add or replace voice cards, if applicable (traditional phone systems only). If the Cisco Unity server contains cards that are not supported with Cisco Unity 3.0, the cards must be replaced before you upgrade because Cisco Unity 3.0 will not run with unsupported cards.
In addition, remove any fax cards. Installing fax software on the Cisco Unity server is no longer supported.
See the "Installing Voice Cards" section.
9. Install Windows 2000 Server. See the "Installing Windows 2000 Server (Component System Only)" section (for upgrades, the section applies to both component and baseline systems).
10. Install Windows 2000 Multilanguage User Interface, if applicable. See the "Installing Additional Windows 2000 Languages" section.
11. All configurations except Voice Messaging Only: Assign a static IP address, if applicable and if you did not do so while installing Windows 2000 Server. See the "Assigning a Static IP Address" section.
12. All configurations except Voice Messaging Only: Confirm that the server is getting an IP address. See the "Verifying the IP Address" section.
13. Install Active Directory, or add the Cisco Unity server to an existing domain. See the "Installing Active Directory or Adding the Cisco Unity Server to an Existing Domain" section.
14. Install SQL Server 2000 or MSDE 2000. See the "Installing SQL Server 2000 or MSDE 2000" section.
15. Install Internet Explorer 5.5. See the "Installing Internet Explorer" section.
16. Install Message Queuing 2.0. See the "Installing Message Queuing 2.0" section.
17. Install NNTP Service, if the system is using Exchange 2000. See the "Installing NNTP Service (Exchange 2000 Only)" section.
18. Install Exchange 2000 Server or Exchange Server 5.5, or install the corresponding administration software. See the applicable section:
•"Installing Exchange, Including Administration Software (Selected Configurations Only)" section.
•"Installing Exchange Administration Software Only" section.
19. Update the Active Directory schema, if the system is using Exchange 2000. See the "Updating the Active Directory Schema (Exchange 2000 only)" section.
20. Install other software. Do not install Outlook 2000 (it is incompatible with Exchange 5.5 and Exchange 2000). See the "Installing Other Software" section.
21. If applicable, create Active Directory organizational units for users and distribution lists, and a mailbox store, if the system is using Exchange 2000. See the "Creating Organizational Units and a Mailbox Store (Exchange 2000 Only)" section.
22. Install Cisco Unity. See the "Installing Cisco Unity Software" section.
Caution After you install Cisco Unity software, do not add any objects (such as subscribers and distribution lists) or remove any default objects until after you import data from the existing Cisco Unity system. The Cisco Unity Database Import utility requires that data be imported into a clean Cisco Unity system.
23. Unified Messaging configurations only, if messages for Cisco Unity subscribers will be stored on both Exchange 5.5 and Exchange 2000 servers, and if the Active Directory Connector uses a one-way connection agreement from Exchange 5.5 to Windows 2000: Configure the system for Exchange 5.5 and Exchange 2000. See the "Configuring a System That Includes Exchange 5.5 and Exchange 2000 Servers (Selected Systems Only)" section.
24. Reinstall Windows 2000 Service Pack 2. See the "Reinstalling Windows 2000 Service Pack 2" section.
25. Import Windows NT/Active Directory accounts into Exchange 5.5, if applicable. See the "Importing Windows NT/Active Directory Accounts into Exchange 5.5 (Selected Configurations Only)" section.
26. Import data exported from the existing Cisco Unity 2.x system. See the "Importing Data Back into Cisco Unity" section.
27. If you want to restore messages and other Exchange data, use the backup you created in Step 5.
This step is not necessary if the Cisco Unity 2.x system was installed in the Unified Messaging in an Existing Exchange Site configuration and no Exchange accounts were homed on the Cisco Unity server.
28. Manually re-enter custom data. See the "Re-entering Custom Data" section.
29. Integrate Cisco Unity and the phone system. Refer to the Cisco Unity integration guide for your phone system. Cisco Unity integration guides are available on the Cisco Unity Documentation compact disc and on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.
30. Create an emergency repair disk. Refer to Windows 2000 Help.
31. Back up the Cisco Unity server. Refer to the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide.
Task List for Setting Up a New Server
Some tasks apply only to particular configuration types, and are noted as such. If a task does not apply to your situation, skip it.
Caution If you plan to change the phone system integration (for example, by changing from a traditional phone system to Cisco CallManager), do not make any changes until you set up the integration in Step
31. If you change the integration too soon, subscriber and call handler settings will not match integration settings, and transfers will fail.
1. Verify system requirements for the Cisco Unity 3.0 system. Refer to Cisco Unity 3.0 System Requirements, and Supported Hardware and Software at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/30_sysrq.htm.
2. Confirm that a Cisco Unity activation code is available (the code is provided when the software is registered). If the Information Services manager has not already registered Cisco Unity, do so now. See the "Cisco Unity Activation Code" section.
3. Generate and print reports on data for the existing Cisco Unity system, if applicable. Refer to the "Reports" chapter of the Cisco Unity System Administration Guide.
Caution The Cisco Unity Database Export utility does not export data that Cisco Unity uses to generate reports. If you want any reports from the existing Cisco Unity system, generate them now.
4. Review the consistency of the Cisco Unity 2.x database, and fix any errors. See the "Reviewing the Consistency of the Cisco Unity 2.x Database" section.
5. Back up the Cisco Unity server completely by using BackupExec or another Exchange-aware backup utility. In addition, if you are upgrading a Cisco Unity system that was installed in the Unified Messaging in an Existing Exchange Site configuration, back up the Exchange servers that are home servers for Cisco Unity subscribers.
For information on using BackupExec to back up the Cisco Unity server, refer to the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide. For information on using another backup utility, refer to the manufacturer documentation.
Caution The Cisco Unity Database Export utility does not back up messages or other Exchange-specific data. You must back up by using an Exchange-aware backup utility.
6. Write down the existing Cisco Unity data that will not be exported or cannot be imported, then do the export. See the "Exporting Data from Cisco Unity" section.
7. Unified Messaging in an Existing Exchange Site only: Uninstall Cisco Unity 2.x. See the "Uninstalling Cisco Unity Version 2.x" section.
Caution You must uninstall Cisco Unity to remove Cisco Unity properties from Exchange users throughout the Exchange site. Otherwise, you will have to manually remove Cisco Unity properties from each Exchange user in raw mode before you can create subscriber accounts on the upgraded Cisco Unity server by importing mail users into Exchange.
8. Add or replace voice cards, if applicable (traditional phone systems only). If the Cisco Unity server contains cards that are not supported with Cisco Unity 3.0, the cards must be replaced before you upgrade because Cisco Unity 3.0 will not run with unsupported cards.
In addition, remove any fax cards. Installing fax software on the Cisco Unity server is no longer supported.
See the "Installing Voice Cards" section.
9. Set up the Cisco Unity 3.0 server. Do not detach the system key from the Cisco Unity 2.x system to attach it to the Cisco Unity 3.0 system yet, or the 2.x system will stop taking calls at midnight. See the "Setting Up the Cisco Unity Server" section.
10. Component system only: Install Windows 2000 Server. See the "Installing Windows 2000 Server (Component System Only)" section.
11. Install Windows 2000 Multilanguage User Interface, if applicable. See the "Installing Additional Windows 2000 Languages" section.
12. All configurations except Voice Messaging Only: Assign a static IP address, if applicable and if you did not do so while installing Windows 2000 Server. See the "Assigning a Static IP Address" section.
13. All configurations except Voice Messaging Only: Confirm that the server is getting an IP address. See the "Verifying the IP Address" section.
14. Install Active Directory, or add the Cisco Unity server to an existing domain. See the "Installing Active Directory or Adding the Cisco Unity Server to an Existing Domain" section.
15. Install SQL Server 2000 or MSDE 2000. See the "Installing SQL Server 2000 or MSDE 2000" section.
16. Component system only: Install Internet Explorer 5.5. See the "Installing Internet Explorer" section.
17. Component system only: Install Message Queuing 2.0. See the "Installing Message Queuing 2.0" section.
18. Component system only: Install NNTP Service, if the system is using Exchange 2000. See the "Installing NNTP Service (Exchange 2000 Only)" section.
19. Install Exchange 2000 Server or Exchange Server 5.5, or install the corresponding administration software. See the applicable section:
•"Installing Exchange, Including Administration Software (Selected Configurations Only)" section.
•"Installing Exchange Administration Software Only" section.
20. Update the Active Directory schema, if the system is using Exchange 2000. See the "Updating the Active Directory Schema (Exchange 2000 only)" section.
21. Install other software. (Do not install Outlook 2000; it is incompatible with Exchange 5.5 and Exchange 2000.) See the "Installing Other Software" section.
22. If applicable, create Active Directory organizational units for users and distribution lists, and a mailbox store, if the system is using Exchange 2000. See the "Creating Organizational Units and a Mailbox Store (Exchange 2000 Only)" section.
23. Attach the system key. If the system key for the Cisco Unity 3.0 system:
24. Install Cisco Unity. See the "Installing Cisco Unity Software" section.
Caution After you install Cisco Unity software, do not add any objects (such as subscribers and distribution lists) or remove any default objects until after you import data from the existing Cisco Unity system. The Cisco Unity Database Import utility requires that data be imported into a clean Cisco Unity system.
25. Unified Messaging configurations only, if messages for Cisco Unity subscribers will be stored on both Exchange 5.5 and Exchange 2000 servers, and if the Active Directory Connector uses a one-way connection agreement from Exchange 5.5 to Windows 2000: Configure the system for Exchange 5.5 and Exchange 2000. See the "Configuring a System That Includes Exchange 5.5 and Exchange 2000 Servers (Selected Systems Only)" section.
26. Reinstall Windows 2000 Service Pack 2. See the "Reinstalling Windows 2000 Service Pack 2" section.
27. Import Windows NT/Active Directory accounts into Exchange 5.5, if applicable. See the "Importing Windows NT/Active Directory Accounts into Exchange 5.5 (Selected Configurations Only)" section.
28. Import data exported from the existing Cisco Unity 2.x system. See the "Importing Data Back into Cisco Unity" section.
29. If you want to restore messages and other Exchange data, use the backup you created in Step 5.
This step is not necessary if the Cisco Unity 2.x system was installed in the Unified Messaging in an Existing Exchange Site configuration and no Exchange accounts were homed on the Cisco Unity server.
30. Manually re-enter custom data. See the "Re-entering Custom Data" section.
31. Integrate Cisco Unity and the phone system. Refer to the Cisco Unity integration guide for your phone system. Cisco Unity integration guides are available on the Cisco Unity Documentation compact disc and on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.
32. Create an emergency repair disk. Refer to Windows 2000 Help.
33. Back up the Cisco Unity server. Refer to the "Maintaining Cisco Unity" chapter in the Cisco Unity System Administration Guide.
Task List for Upgrading an Existing Server
Some tasks apply only to particular configuration types, and are noted as such. If a task does not apply to your situation, skip it.
Caution If you plan to change the phone system integration (for example, by changing from a traditional phone system to Cisco CallManager), do not make any changes until you set up the integration in Step
32. If you change the integration too soon, subscriber and call handler settings will not match integration settings, and transfers will fail.
1. Verify system requirements for the Cisco Unity 3.0 system. Refer to Cisco Unity 3.0 System Requirements, and Supported Hardware and Software at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/30_sysrq.htm.
2. Confirm that a Cisco Unity activation code is available (the code is provided when the software is registered). If the Information Services manager has not already registered Cisco Unity, do so now. See the "Cisco Unity Activation Code" section.
3. Generate and print reports on data for the existing Cisco Unity system, if applicable. Refer to the "Reports" chapter of the Cisco Unity System Administration Guide.
Caution The Cisco Unity Database Export utility does not export data that Cisco Unity uses to generate reports. In addition, during the upgrade, you delete all the existing Cisco Unity software and data, including data that Cisco Unity uses to generate reports. If you want any reports from the existing Cisco Unity system, generate them now.
4. Review the consistency of the Cisco Unity 2.x database, and fix any errors. See the "Reviewing the Consistency of the Cisco Unity 2.x Database" section.
5. Back up the Cisco Unity server completely by using BackupExec or another Exchange-aware backup utility. In addition, if you are upgrading a Cisco Unity system that was installed in the Unified Messaging in an Existing Exchange Site configuration, back up the Exchange servers that are home servers for Cisco Unity subscribers.
For information on using BackupExec to back up the Cisco Unity server, refer to the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide. For information on using another backup utility, refer to the manufacturer documentation.
Caution The Cisco Unity Database Export utility does not back up messages or other Exchange-specific data. You must back up by using an Exchange-aware backup utility.
6. Write down the existing Cisco Unity data that will not be exported or cannot be imported, then do the export. See the "Exporting Data from Cisco Unity" section.
7. Add or replace voice cards, if applicable (traditional phone systems only). If the Cisco Unity server contains cards that are not supported with Cisco Unity 3.0, the cards must be replaced before you upgrade because Cisco Unity 3.0 will not run with unsupported cards.
In addition, remove any fax cards. Installing fax software on the Cisco Unity server is no longer supported.
See the "Installing Voice Cards" section.
8. Uninstall voice card software, if applicable. See the "Removing Voice Card Software" section.
9. Uninstall ActiveFax, if applicable. See the "Removing ActiveFax" section.
10. Uninstall any version of pcAnywhere earlier than version 10. (Earlier versions are not compatible with Windows 2000.) Refer to the manufacturer instructions to uninstall pcAnywhere.
11. Uninstall Cisco Unity 2.x. See the "Uninstalling Cisco Unity Version 2.x" section.
12. If you are upgrading Windows NT 4.0 to Windows 2000, upgrade now. (Cisco Unity 3.0 does not support Windows NT 4.0.) For information, refer to the Microsoft website.
13. Install Windows 2000 Service Pack 2. See the "Reinstalling Windows 2000 Service Pack 2" section (the procedure is the same for installing and reinstalling).
14. Install Windows 2000 Multilanguage User Interface, if applicable. See the "Installing Additional Windows 2000 Languages" section.
15. All configurations except Voice Messaging Only: Confirm that the server is still getting an IP address. See the "Verifying the IP Address" section.
16. If you upgraded Windows NT 4.0 to Windows 2000 in Step 12., install Active Directory or add the Cisco Unity server to an existing domain. See the "Installing Active Directory or Adding the Cisco Unity Server to an Existing Domain" section.
17. Install SQL Server 2000 or MSDE 2000. See the "Installing SQL Server 2000 or MSDE 2000" section.
18. If the current version of Internet Explorer is earlier than 5.01, install Internet Explorer 5.01 or 5.5. See the "Installing Internet Explorer" section.
19. Install Message Queueing 2.0. See the "Installing Message Queuing 2.0" section.
20. Install NNTP Service and SMTP Service, if the system is using Exchange 2000. See the "Installing NNTP Service (Exchange 2000 Only)" section.
21. If you are upgrading Exchange 5.5 to Exchange 2000, upgrade now. For information, refer to the Microsoft website.
Caution Cisco TAC does not provide support for upgrading Exchange 5.5 to Exchange 2000.
22. Update the Active Directory schema, if the system is using Exchange 2000. See the "Updating the Active Directory Schema (Exchange 2000 only)" section.
23. Install pcAnywhere version 10. Refer to the manufacturer instructions to install pcAnywhere.
24. If applicable, create Active Directory organizational units for users and distribution lists, and a mailbox store, if the system is using Exchange 2000. See the "Creating Organizational Units and a Mailbox Store (Exchange 2000 Only)" section.
25. Install Cisco Unity. See the "Installing Cisco Unity Software" section.
Caution After you install Cisco Unity software, do not add any objects (such as subscribers and distribution lists) or remove any default objects until after you import data from the existing Cisco Unity system. The Cisco Unity Database Import utility requires that data be imported into a clean Cisco Unity system.
26. Unified Messaging configurations only, if messages for Cisco Unity subscribers will be stored on both Exchange 5.5 and Exchange 2000 servers, and if the Active Directory Connector uses a one-way connection agreement from Exchange 5.5 to Windows 2000: Configure the system for Exchange 5.5 and Exchange 2000. See the "Configuring a System That Includes Exchange 5.5 and Exchange 2000 Servers (Selected Systems Only)" section.
27. Reinstall Windows 2000 Service Pack 2. See the "Reinstalling Windows 2000 Service Pack 2" section.
28. Import Windows NT/Active Directory accounts into Exchange 5.5, if applicable. See the "Importing Windows NT/Active Directory Accounts into Exchange 5.5 (Selected Configurations Only)" section.
29. Import the data exported from the existing Cisco Unity 2.x system. See the "Importing Data Back into Cisco Unity" section.
30. If you want to restore messages and other Exchange data, use the backup you created in Step 5.
This step is not necessary if the Cisco Unity 2.x system was installed in the Unified Messaging in an Existing Exchange Site configuration and no Exchange accounts were homed on the Cisco Unity server.
31. Manually re-enter custom data. See the "Re-entering Custom Data" section.
32. Integrate Cisco Unity and the phone system. Refer to the Cisco Unity integration guide for your phone system. Cisco Unity integration guides are available on the Cisco Unity Documentation compact disc and on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.
33. Create an emergency repair disk. Refer to Windows 2000 Help.
34. Back up the Cisco Unity server. Refer to the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide.
Reviewing the Consistency of the Cisco Unity 2.x Database
Cisco Unity version 3.0 includes the Cisco Unity Directory Walker utility to find invalid links, and incorrect and stranded objects in the Exchange directory. You fix any errors before exporting data.
The Directory Walker utility creates a log file that contains a list of invalid references. In addition, the utility includes options to automatically remove call handlers that are not associated with a subscriber (orphaned call handlers) and to remove Cisco Unity properties from Exchange mail users who do not have a primary call handler.
The Directory Walker utility reviews each subscriber account and confirms that:
•Display Name is not blank.
•The primary call handler exists and is valid.
•The primary call handler is not shared by another mail user.
•The class of service reference exists and is valid.
•The location exists and is valid.
•The language selected for the mail user is installed on the Cisco Unity server (the utility confirms this only on Cisco Unity versions 2.45 and later).
•The phone system ID is valid and references a phone system integration on the Cisco Unity server (the utility confirms this only on Cisco Unity versions 2.45 and later).
Directory Walker also reviews each call handler and confirms that:
•The owner and the recipient exist and are valid. (The call handler is not orphaned.)
•The location exists and is valid.
•For non-primary call handlers, the Text Name is not blank.
•For primary call handlers, the DTMF_ID is not blank.
•The DTMF_ID does not conflict with another object.
•The after-message action links to a valid object.
•All one-key rules (caller-input keys) link to valid objects.
•The after-greeting action links to a valid object for each greeting rule.
•The schedule reference is valid.
•The Standard greeting is active. If not, Directory Walker makes it active.
•The Standard transfer rule is active. If not, Directory Walker makes it active.
To run the Cisco Unity Directory Walker utility
Step 1 Log on to Windows by using the account that was used to install Cisco Unity.
Step 2 Confirm that Cisco Unity is running.
Step 3 Insert Cisco Unity 3.0 Disc 1 in the CD-ROM drive.
Step 4 Browse to the directory TechTools, and double-click DbWalker.exe.
Step 5 Uncheck the Remove Orphaned Call Handlers Automatically check box and the Remove Subscriber Properties on Mail Users That Have No Primary Call Handlers check box. This produces a report so you can correct errors before you delete orphaned call handlers and subscriber properties.
Step 6 Specify a name and location for the Directory Walker log file.
Step 7 Click Walk Database.
Step 8 When Directory Walker has finished, review the log file that you specified in Step 6. To find problems, search for the string (error). Each error listed in the log includes detailed information so you can correct it.
Step 9 When you have corrected the errors that Directory Walker reported, repeat Steps 4 through 8 until the only errors in the log file are orphaned call handlers and mail users that have no primary call handlers. (If you have no such errors, you are finished with this procedure.)
Step 10 Run the Directory Walker utility one more time. Browse to the directory TechTools, and double-click DbWalker.exe.
Step 11 This time, check the Remove Orphaned Call Handlers Automatically check box and the Remove Subscriber Properties on Mail Users That Have No Primary Call Handlers check box.
Step 12 Specify a name and location for the Directory Walker log file.
Step 13 Click Walk Database.
Step 14 When Directory Walker has finished, search the log file for the string (error) to find which orphaned call handlers were removed and which mail users had their Cisco Unity subscriber properties removed.
Step 15 Copy the log file to a network drive or to a high-capacity removable storage device. If you encounter problems with the upgrade process, Cisco TAC requires this file for troubleshooting.
Exporting Data from Cisco Unity
Cisco Unity version 3.0 includes the Cisco Unity Database Export utility for exporting subscriber and system information from earlier versions of the product.
Caution Upgrading to Cisco Unity 3.0 requires that you completely remove the previous version of Cisco Unity and then install the new version. If you do not export Cisco Unity data, you will have to recreate subscriber accounts, call handlers, and other objects and properties.
Data is exported to a Microsoft Access database. The size of the database depends on the number and size of objects and properties in the Cisco Unity 2.x database. (For example, exporting all objects and properties on a system with 1,500 subscribers, 2,000 call handlers, and short greetings for 700 of the call handlers generated a 300 MB database.)
Most of the Cisco Unity data stored on the Cisco Unity server and in Exchange is exported by the Cisco Unity Database Export utility and can be imported into Cisco Unity 3.0 with the Cisco Unity Database Import utility. The following sections detail how data is handled and how to run the export utility.
Data That Is Exported
Table 3-2 Data Exported by the Cisco Unity Database Export Utility
Data
|
Qualifications
|
Subscriber information
|
Exported, except for the following values on each subscriber account:
•Phone password.
•Last password change date/time.
•Account lockout status.
•Last contact time stamp.
•SMTP address, unless the user is an Internet subscriber. This value is generated automatically when you import subscribers into Cisco Unity 3.0.
•Home server. This value is assigned automatically when you import subscribers into Cisco Unity 3.0.
New users are homed on the Cisco Unity server, or—if Exchange is not installed on the Cisco Unity server—the user is created on the Exchange server to which Cisco Unity is connected.
|
Subscriber templates
|
For Cisco Unity versions earlier than 2.4, templates are not exported.
For Cisco Unity versions 2.4 and later, templates are exported except for the public distribution lists that were associated with the templates. Public distribution lists will need to be manually readded to subscriber templates on the Cisco Unity 3.0 system.
|
Call handlers
|
Exported.
|
Interview handlers
|
Exported.
|
Class of service information
|
Exported.
|
Restriction tables
|
Exported.
|
Locations
|
Locations that were created on the local Cisco Unity server (locations that have a matching System ID to the local Cisco Unity server) are exported.
All subscribers added to the Cisco Unity 3.0 system will be associated with the primary location object created by Cisco Unity 3.0 Setup. No subscribers will be associated with any other location object. The other location objects imported will be used for blind addressing only.
|
Name lookup handler
|
Exported.
|
Password policy
settings
|
Exported.
|
Schedules
|
If the site added schedules and deleted system default schedules, the updated system will have both the added schedules and the system defaults. The Cisco Unity Database Import utility has no provision for removing existing data.
|
Holidays
|
For Cisco Unity versions earlier than 2.4, templates are not exported. Holidays will need to be manually re-entered on the Cisco Unity 3.0 system.
|
Port configuration
information
|
All the port capability settings information (such as answer, dial, TRAP, and out of service), the phone system with which the port is associated (for dual phone system configurations), the extension number associated with the port, and the MWI capability flag in the registry are exported.
|
Data That Is Not Exported, and Data That Is Exported but Not Imported
Phone system settings
To restore the current phone system settings, you need to follow the procedures in the Cisco Unity integration guide for your phone system, later in the upgrade process.
System prompts
Customized system prompts are not supported. All system prompts are automatically deleted and replaced whenever you upgrade Cisco Unity.
Settings on the Configuration pages in the Cisco Unity Administrator
You may want to write down settings on the Configuration pages in the Cisco Unity Administrator, including site name, file aging settings, RSA SecurID security settings, contact information, recording options, and languages loaded.
Caution If you do not install and load the same phone languages on the Cisco Unity 3.0 system as were installed and loaded on the 2.x system, subscribers who are configured to use the missing languages will not be able to hear the system conversation in their languages.
Public distribution lists
Public distribution lists (PDLs) are not exported, but because members of PDLs are stored in Exchange, PDLs are preserved in the following cases:
•When Cisco Unity is installed in the Unified Messaging in an Existing Exchange Site configuration.
•When you are not reinstalling Exchange on the Cisco Unity server.
When PDLs will not be preserved, you can export them from Exchange 5.5 to a CSV file. After you upgrade to Cisco Unity 3.0, you import them into Exchange 5.5 or Active Directory groups (Exchange 2000), then use the Cisco Unity Administrator to import them back into Cisco Unity. For information on exporting PDLs from Exchange 5.5, refer to Exchange 5.5 Help.
Call routing rules
Call routing rules are exported, but they cannot be imported, and you cannot easily read the routing-rules file that is saved in the CommServer\BackupData directory. The information is exported for the benefit of technicians.
If you added any call routing rules to Cisco Unity 2.x, write down the settings for those rules so you can reproduce them in Cisco Unity 3.0. (The default routing rules can be changed only with the help of Cisco TAC, so you generally should not have to write down the settings for those rules.)
To write down the settings for customized call routing rules
Step 1 In the Cisco Unity Administrator, go to Call Management > Call Routing > Direct Calls.
Step 2 In the Routing Table, click each customized routing rule and write down the settings for that rule.
Step 3 Go to Call Management > Call Routing > Forwarded Calls.
Step 4 In the Routing Table, click each customized routing rule and write down the settings for that rule.
Phone system files and Windows registry keys
Many Cisco Unity-related Windows registry keys and attributes in the Cisco Unity phone system files can be customized. Some of these customizable attributes are no longer relevant for Cisco Unity 3.0—and some may even cause problems—so changes to the registry and phone system files are exported but cannot be imported.
After you run the Cisco Unity Database Import utility, you can find the settings from the Cisco Unity 2.x server on the Cisco Unity 3.0 server in the directory CommServer\BackupData. The directory will contain:
•The phone system file currently active on the Cisco Unity 2.x system.
•All phone system files in the Intlib directory that have an .avd extension: Avsmdi.avd, Avanalog.avd, Averic.avd, Avfuji.avd, Avdcs.avd, Avhcx.avd, Avmci.avd, and Avtosh.avd.
•The entire ActiveVoice tree in the Windows registry. The tree is saved in a file named RegistryTree.old.
Installing and Running the Cisco Unity Database Export Utility
If Cisco Unity version 2.x is installed on a server running Windows NT 4.0 and if the existing version of Cisco Unity is earlier than 2.4, install Microsoft Data Access Components (MDAC).
Caution Do not install MDAC on a Cisco Unity server running Windows 2000.
To install MDAC
Step 1 Insert Cisco Unity 3.0 Disc 1 in the CD-ROM drive.
Step 2 Browse to the directory Mdac\Enu, and double-click Mdac_typ.exe.
To install the Cisco Unity Database Export utility
Step 1 Insert Cisco Unity 3.0 Disc 1 in the CD-ROM drive.
Step 2 Browse to the directory MigrationTools\ExportUnityData, and double-click Setup.exe.
Step 3 Follow the on-screen prompts.
Step 4 If you are prompted to restart the server, do so.
To run the Cisco Unity Database Export utility
Step 1 Log on to Windows by using the account that was used to install Cisco Unity.
Step 2 Confirm that the location to which you are exporting has enough space for the export database. See the "Exporting Data from Cisco Unity" section. Without enough space, the export will fail and you will have to run the export again.
Step 3 Exit the Cisco Unity software. (If you do not exit the software before you export the database, the utility will exit Cisco Unity automatically before it begins exporting data.)
Step 4 On the Windows Start menu, click Programs > Database Export > Database Export.
Step 5 Specify which information to include in the database. For each property that you exclude, the export and import processes will be faster and the database will be smaller.
Caution We strongly recommend that if you choose to exclude properties from the export, that subscriber greetings and recorded names be the only properties that you choose not to export.
If you exclude subscriber greetings and recorded names, you can set the Cisco Unity 3.0 system to play the first-time enrollment conversation for all subscribers when you import the database. The conversation prompts subscribers to record a greeting and name if none exist.
Step 6 Specify the names and locations for the database file (which contains all the data listed in the "Data That Is Exported" section) and the log file (which logs the progress of the export and which Cisco TAC requires for any troubleshooting).
Step 7 Click Export Data. If necessary, you can click Exit to interrupt the export before it finishes.
Step 8 When the export finishes, a dialog box displays the number of errors that the export encountered. If there are any errors, display the log file and search for the string (error) to find and review each error.
Step 9 Copy the database and log files that you specified in Step 6 from the Cisco Unity server to a network drive or to a high-capacity removable storage device.
Removing Voice Card Software
This section contains procedures for removing different brands of voice card software. Do the procedures that apply to your voice card brand(s).
If the Cisco Unity 3.0 system will contain voice cards, the voice card software will be reinstalled when you install Cisco Unity version 3.0.
Dialogic Software
When the Dialogic quiet parameter has been set to a value other than the default, the setting will be lost when you remove the Dialogic software. Write down the current value of the quiet parameter so you can restore that value after you reinstall the software.
To determine the current setting for the Dialogic quiet parameter
Step 1 Exit the Cisco Unity software, if it is running. For more information, see "Exiting and Starting the Cisco Unity Software and Server."
Step 2 Click Programs > Administrative Tools > Services.
Step 3 In the right pane of the Services dialog box, right-click Telephony, and click Stop.
Step 4 If you are prompted to stop other services, click Yes.
Step 5 On the Windows Start menu, click Programs > Dialogic System Software > Dialogic Configuration Manager-DCM.
The tree-structured list contains an entry for each Dialogic card installed in the server.
Step 6 On the Service menu, click Stop Service.
Step 7 Double-click a voice card in the tree list.
Step 8 In the Properties dialog box for the card, click the Misc tab.
Step 9 Under Parameter, note and write down the value of ParameterFile.
Step 10 Click OK.
The following procedure may differ slightly for earlier versions of Cisco Unity, which used an earlier version of Dialogic Configuration Manager.
To remove Dialogic software (Windows 2000)
Step 1 Exit the Cisco Unity software, if it is running. For more information, see "Exiting and Starting the Cisco Unity Software and Server."
Step 2 Click Programs > Administrative Tools > Services.
Step 3 In the right pane of the Services dialog box, right-click Telephony, and click Stop.
Step 4 If you are prompted to stop other services, click Yes.
Step 5 On the Windows Start menu, click Programs > Dialogic Systems Software > Dialogic Configuration Manager-DCM.
Dialogic Configuration Manager may display an error message about not detecting devices. This error is harmless. Click OK.
Step 6 On the Service menu, click Stop Service.
Step 7 Click Close.
Step 8 Close the DCM.
Step 9 On the Windows Start menu, click Settings > Control Panel > Phone and Modem Options.
Step 10 Click the Advanced tab.
Step 11 Click Dialogic Generation 2 Service Provider for NT.
If you are using D/160SC voice cards and VoiceBridge 2000 feature-set cards, this option will be DSE Service Provider.
Step 12 Click Remove.
Step 13 Click Yes.
Step 14 Click Close to close the Phone and Modem Options dialog box.
Step 15 In Control Panel, double-click Sounds and Multimedia.
Step 16 In the Sounds and Multimedia Options dialog box, click the Hardware tab.
Step 17 Click Legacy Audio Drivers.
Step 18 Click Properties.
Step 19 In the Legacy Audio Drivers Properties dialog box, click the Properties tab.
Step 20 Expand Audio Devices.
Step 21 Click Audio for Dialogic WAVE.
Step 22 Click Remove. The Legacy Audio Drivers Properties dialog box closes.
Step 23 Click Yes to confirm.
Step 24 When prompted to restart the server, click Don't Restart Now.
Caution If you restart now, the WAVE driver is not removed.
Step 25 Click OK to close the Legacy Audio Drivers Properties dialog box.
Step 26 Click OK to close the Sounds and Multimedia Properties dialog box.
Step 27 Close Control Panel.
Step 28 On the Windows Start menu, click Programs > Dialogic System Software > Uninstall.
Step 29 Follow the on-screen prompts.
If you are prompted to delete shared files, click No to All.
Step 30 Click OK.
Step 31 If you are using D/160SC voice cards and VoiceBridge 2000 feature-set cards, at the end of the uninstall, do not restart the server. Instead, skip to the "Voice Technologies Group Software" section.
Otherwise, at the end of the uninstall, click Yes to restart the server. (The Dialogic-triggered restart may not restart the session; in this case, manually restart.)
Step 32 After the system restarts, log on.
Step 33 In Windows Explorer, browse to the directory where Cisco Unity is installed (the default directory is C:\CommServer) and delete the Dialogic directory.
To remove Dialogic software (Windows NT)
Step 1 Exit the Cisco Unity software, if it is running. For more information, see "Exiting and Starting the Cisco Unity Software and Server."
Step 2 On the Windows Start menu, click Programs > Dialogic System Software > Dialogic Configuration Manager-DCM.
Step 3 On the Service menu, click Stop Service.
Step 4 Close the DCM.
Step 5 On the Windows Start menu, click Settings > Control Panel > Telephony.
Step 6 In the Dialing Properties dialog box, click the Telephony Drivers tab.
Step 7 Click Dialogic Generation 2 Service Provider for NT.
If you are using D/160SC voice cards and VoiceBridge 2000 feature-set cards, this option will be DSE Service Provider.
Step 8 Click Remove.
Step 9 Click Close to close the Dialing Properties dialog box.
Step 10 In Control Panel, double-click Multimedia.
Step 11 In the Multimedia Properties dialog box, click the Devices tab.
Step 12 Expand Audio Devices.
Step 13 Click Audio for Dialogic WAVE Driver 1.x or Audio for Dlgwave.dll.
Step 14 Click Remove.
Step 15 When prompted to restart, click Don't Restart Now.
Step 16 Click OK to close the Multimedia Properties dialog box.
Step 17 Close Control Panel.
Step 18 On the Windows Start menu, click Programs > Dialogic System Software > Uninstall.
Step 19 Follow the on-screen prompts
If you are prompted to delete shared files, click No to All.
Step 20 If you are using D/160SC voice cards and VoiceBridge 2000 feature-set cards, at the end of the uninstall, do not restart the server. Instead, skip to the "Voice Technologies Group Software" section.
Otherwise, at the end of the uninstall, click Reboot. (The Dialogic-triggered restart may not restart the system; in this case, manually restart.)
Step 21 After the system restarts, log on.
Step 22 In Windows Explorer, browse to the directory where Cisco Unity is installed (the default directory is C:\CommServer) and delete the TSPSetup directory.
Voice Technologies Group Software
Do the following procedure when the Cisco Unity server contains Dialogic D/160SC voice cards and Voice Technologies Group VoiceBridge 2000 feature-set cards.
To remove VTG software
Step 1 On the Windows Start menu, click Settings > VoiceBridge 2000 > Uninstall.
Step 2 If you are prompted to delete shared files, click No to All.
Step 3 Restart the server.
Natural MicroSystems Software
To remove NMS software
Step 1 Exit the Cisco Unity software, if it is running. For more information, see "Exiting and Starting the Cisco Unity Software and Server."
Step 2 On the Windows Start menu, click Settings > Control Panel >Telephony.
Step 3 In the Dialing Properties dialog box, click the Telephony Drivers tab.
Step 4 Click Natural MicroSystems Service Provider.
Step 5 Click Remove.
Step 6 Click OK to close the Dialing Properties dialog box.
Step 7 In Control Panel, double-click Multimedia.
Step 8 In the Multimedia Properties dialog box, click the Devices tab.
Step 9 Expand Audio Devices.
Step 10 Click Audio for Natural MicroSystems Telephony Hardware.
Step 11 Click Remove.
Step 12 Click OK to close the Multimedia Properties dialog box.
Step 13 If you are prompted to restart the server, click Don't Restart Now.
Step 14 In Control Panel, double-click Add/Remove Programs.
Step 15 Click Natural MicroSystems Natural Access.
Step 16 Click OK repeatedly to confirm that you want to remove each program.
Step 17 Click Add/Remove.
Step 18 When all NMS components have been removed, close all programs and restart the server.
Step 19 After restarting, log on.
Step 20 In Windows Explorer, browse to the root directory and delete the NMS directory.
Removing ActiveFax
ActiveFax is no longer supported, and fax software installed on the Cisco Unity server is not supported.
To remove ActiveFax from the Cisco Unity server
Step 1 Log on to Windows by using the account that was used to install Cisco Unity.
Step 2 Stop all Cisco Unity services (which begin with "Av") and ActiveFax services (which begin with "LF").
Step 3 On the Windows Start menu, click Settings > Control Panel >Add/Remove Programs.
Step 4 Remove the following programs in the order listed. If you are prompted to delete shared files, click No to All.
•LightningFAX 6.5 - LFExGateway
•LightningFAX 6.5 - FAXTOMAIL (if it is installed)
•LightningFAX 6.5 - CLIENT
•LightningFAX 6.5 - RASTERIZATION SERVER
•LightningFAX 6.5 - DRIVER
•LightningFAX 6.5 - SERVER
•LightningFAX 6.5 - USYNC
•LightningFAX 6.5 - ACTIVEX CONTROLS
Step 5 Close the Add/Remove Programs dialog box.
Step 6 Restart the Cisco Unity server.
Step 7 Confirm that the ActiveFax directory has been deleted. By default, ActiveFax was installed in one of the following locations. (Both directories may exist, if you installed an early version of Cisco Unity and upgraded to a later version.)
•C:\Program files\ActiveFax
•C:\CommServer\Fax
Step 8 On the Windows Start menu, click Programs > Microsoft Exchange > Microsoft Exchange Administrator.
Step 9 In the left pane of Exchange Administrator, click <Site name> > Configuration > Connection.
Step 10 In the right pane, confirm that Lightning Fax Gateway for Microsoft Exchange does not appear. (You may need to wait for replication to occur.)
If Lightning Fax Gateway for Microsoft Exchange still appears, stop the LFExGateway service.
Step 11 Start Regedt32.
Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. Note that a typical backup of the Cisco Unity server does not back up the registry. Refer to the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe for additional information. If you have any questions about changing registry key settings, contact Cisco TAC.
Step 12 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.
Step 13 For each of the following registry keys, do Steps a through f:
•HKEY_LOCAL_MACHINE\Software\Interstar Technologies
•HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\
LEGACY_7J8I-9K0L-1R5T-8K9P-1A2B-1V5H-5H7J
•HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\
LEGACY_ LFUSync
a. Select the key.
b. On the Regedt32 menu, click Security > Permissions.
c. In the Permissions dialog box, click Everyone.
d. In the Permissions table, check the Full Control check box in the Allow column.
e. Click OK to close the Permissions dialog box.
f. Delete the key.
Step 14 In the Winnt\System32 directory, delete files with the extension .lfl, if any.
Step 15 On the Windows Start menu, click Run, and run the command C:\Winnt\System32\regsvr32.exe scrrun.dll. (For early versions of ActiveFax, uninstalling ActiveX removes Windows Scripting Host from the registry. This command restores the registry entry.)
Step 16 Restart the Cisco Unity server.
Uninstalling Cisco Unity Version 2.x
Cisco Unity version 3.0 includes the Cisco Unity Uninstaller utility for uninstalling Cisco Unity version 2.x.
Uninstall Cisco Unity only if one or both of the following is true:
•The Cisco Unity system is installed in the Unified Messaging in an Existing Exchange Site configuration.
•You are upgrading an existing server without reinstalling all software.
Caution If the Cisco Unity system is installed in the Unified Messaging in an Existing Exchange Site configuration, you must uninstall Cisco Unity to remove Cisco Unity properties from Exchange users throughout the Exchange site. Otherwise, you will have to manually remove Cisco Unity properties from each Exchange user in raw mode before you can create subscriber accounts on the upgraded Cisco Unity server by importing mail users into Exchange.
The Cisco Unity Uninstaller Utility
When you run the utility:
•All Cisco Unity (Av) services are stopped, unregistered, and deleted.
•All Cisco Unity custom data is deleted from all mail users in the Exchange directory who are associated with the local Cisco Unity server. This data is not removed for users who are associated with other Cisco Unity servers that may be installed in the Exchange site. Properties that are not specific to Cisco Unity are not affected.
•All Cisco Unity objects on the current Cisco Unity server (such as call handlers and class of service objects) are deleted from the existing Exchange directory.
•The Unaddressed Messages and Unaddressed Faxes PDLs added by Cisco Unity are deleted from the recipients/distribution lists container of the local server. If this is the last Cisco Unity server in the site, the All Subscribers and System Event Messages PDLs are deleted from the site.
•The Example Administrator, Example Subscriber, and Cisco Unity_<MachineName> accounts are deleted from the recipients container of the local Cisco Unity server.
If the Cisco Unity system you are upgrading is version 2.3.x, you also need to manually remove the Windows NT accounts for Example Administrator and Example Subscriber.
•All Cisco Unity greetings are deleted from the Exchange RES folder.
•Cisco Unity-related registry entries are deleted from the registry.
•The Cisco Unity status-bar application is deleted from the Windows Startup menu.
•The Cisco Unity program group is deleted from the Windows Start menu.
•The Cisco Unity Administrator and ActiveAssistant icons are deleted from the desktop.
•The CommServer directory and its subdirectories are deleted from the hard disk.
•The Cisco Unity-specific directories are deleted from the Wwwroot directory.
•Some Cisco Unity-specific DLLs are deleted from the System32 directory.
Option to Skip Removal of Exchange Objects
If you have manually removed the "Unity" folder from Exchange, reinstalled Exchange, or want the Cisco Unity Uninstaller utility to skip the removal of all Exchange objects, run the Uninstaller utility with the "/SkipDOH" command line option. The following items are retained:
•All Cisco Unity custom data for all mail users in the Exchange directory who are associated with the local Cisco Unity server.
•All Cisco Unity objects on the current Cisco Unity server in the existing Exchange directory.
•The Example Administrator, Example Subscriber, and Cisco Unity_<MachineName> accounts in the recipients container of the local Cisco Unity server.
The "/SkipDOH" command line option can be useful if you reinstalled Exchange but forgot to remove Cisco Unity first, and you want to clean up all the Cisco Unity-specific files on your hard disk and in the registry before installing a new version of Cisco Unity.
Installing and Running the Cisco Unity Uninstaller Utility
To install the Cisco Unity Uninstaller utility (Windows 2000)
Step 1 Insert Cisco Unity 3.0 Disc 1 in the CD-ROM drive.
Step 2 Browse to the directory MigrationTools\UninstallUnity, and double-click Setup.exe.
Step 3 Follow the on-screen prompts.
You do not need to restart the server before you run the utility.
To install the Cisco Unity Uninstaller utility and ADSI (Windows NT)
Step 1 Insert Cisco Unity 3.0 Disc 1 in the CD-ROM drive.
Step 2 Browse to the directory MigrationTools\UninstallUnity, and double-click Setup.exe.
Step 3 Follow the on-screen prompts.
Step 4 When the installation finishes, browse to the directory in which you installed the Uninstaller utility, and double-click Ads.exe.
Step 5 Follow the on-screen prompts to install Active Directory Service Interface (ADSI).
Step 6 Restart the server.
To run the Cisco Unity Uninstaller utility
Step 1 If the Windows Program menu item for Cisco Unity was renamed from "Unity," change the name back to "Unity" now, or menu items will not be removed during the uninstall.
Step 2 If you have not already removed Dialogic, NMS, VTG, and ActiveFax software, do so now or the uninstall program may not properly remove everything from the system.
Step 3 Log on to Windows by using the account that was used to install Cisco Unity.
Step 4 On the Windows Start menu, click Programs > Unity Uninstaller > Unity Uninstaller.
Step 5 Follow the on-screen prompts to complete the Cisco Unity uninstall.
If you are prompted to stop IIS and NNTP services, click OK to continue.
In some cases, a dialog box may appear explaining that you will need to manually remove the Unity folder from Exchange. Note this so that you can remove the folder later.
Caution Do not interrupt the Cisco Unity Uninstaller utility. Depending on the number of subscribers and the speed of the Cisco Unity server, the utility may take an hour or more to complete. If you interrupt the uninstall program, you cannot restart it. You will need to call Cisco TAC for information on completing the uninstall manually. For more information on the duration of the uninstall, see the
"Duration of Upgrade" section.
Step 6 When the Cisco Unity Uninstaller utility has finished running, delete the directory for the L&H TTS3000 text-to-speech engine. The default directory is Winnt\LHSP.
Step 7 If necessary, remove the Unity folder from Exchange. Start the Exchange Administrator in raw mode:
<drive>:\Exchsrvr\bin\Admin.exe -r
Caution Delete the Unity folder from Exchange only if there are no other Cisco Unity servers on the site.
Step 8 Select the Unity folder.
Step 9 On the Exchange Administrator menu, click Edit > Delete Raw Object.
Step 10 Confirm that you want to delete the folder.
Step 11 Close the Exchange Administrator.
Step 12 If the system you are upgrading is version 2.3.x, manually remove the Windows NT accounts for Example Administrator and Example Subscriber.
LDAP Port Error with the Cisco Unity Uninstaller Utility
If the uninstall does not start and you get an error message that indicates the LDAP port is incorrect, one of the following problems has occurred:
•The wrong LDAP port was specified in the Uninstaller utility.
To determine which LDAP port the Cisco Unity server is using, in the Exchange Administrator, open the site container, open the Configuration container, click Protocols, and double-click LDAP. If necessary, you can change this value at the server level instead of the site level.
•Active Directory Service Interface was not installed (Windows NT only). See the "To install the Cisco Unity Uninstaller utility and ADSI (Windows NT)" section to install ADSI.
Importing Windows NT/Active Directory Accounts into Exchange 5.5 (Selected Configurations Only)
If the Cisco Unity 3.0 system is using Exchange 5.5, you may have to import Windows NT/Active Directory accounts into Exchange before you import Cisco Unity data into Exchange.
When you exported data from the Cisco Unity 2.x system by using the Database Export utility, the utility exported the Exchange alias for every subscriber. When you import data back into Cisco Unity 3.0, the Database Import utility will look in Exchange for subscribers by alias. If an alias does not exist in Exchange but does exist in Windows NT/Active Directory, the import process will not import that subscriber. Therefore, if the aliases that you exported from Cisco Unity 2.x still exist in Windows NT/Active Directory but do not exist in Exchange, you need to import the Windows NT/Active Directory accounts into Exchange 5.5 before you can use the Database Import utility to import data back into Cisco Unity.
To import Windows NT/Active Directory accounts into Exchange 5.5
Step 1 On the Windows Start menu, click Programs > Exchange > Microsoft Exchange Administrator.
Step 2 In the Exchange Administrator, click Tools > Extract Windows NT Account List.
Step 3 Click the domain and domain controller where Windows NT/Active Directory accounts are stored.
Step 4 Click Browse, and specify the name and location of the output file. The file will be stored in CSV format.
Step 5 Click OK twice to finish extracting accounts from Windows NT or Active Directory.
Step 6 Click Tools > Directory Import.
Step 7 Click Import File, and browse to the file you named in Step 4.
Step 8 If the organization does not use the default recipients container, change the container. Consult the Information Systems administrator for the correct container.
Step 9 Do not change any other settings.
Step 10 Click Import.
Importing Data Back into Cisco Unity
After software on the Cisco Unity 3.0 server is fully installed and Cisco Unity is integrated with the phone system, use the Cisco Unity Database Import utility to import the data you exported earlier. For information on how long importing data will take, see the "Duration of Upgrade" section.
The Cisco Unity Database Import utility requires that data be imported into a clean Cisco Unity system.
The Import Process
The Database Import utility imports subscribers into Exchange based on Exchange aliases. (If the site upgraded from Exchange 5.5 to Exchange 2000, which causes the Exchange distinguished name to change even if the container structure remains the same, the alias is the only piece of data about each Cisco Unity subscriber that will be the same.) In rare cases, this may cause problems because Exchange does not require the alias to be unique, although it is highly recommended. If more than one match for an alias is found, the Cisco Unity subscriber will not be imported.
If you create a new Exchange directory and manually create users, be certain that aliases in the new directory match those in the old directory. If aliases do not match, the Database Import utility will look up a subscriber, not find that person, and then create a new Exchange account by using the old alias. Each subscriber for which this occurs will have two Exchange accounts.
Installing and Running the Cisco Unity Database Import Utility
To install the Cisco Unity Database Import utility
Step 1 Insert Cisco Unity 3.0 Disc 1 in the CD-ROM drive.
Step 2 Browse to the directory MigrationTools\ImportUnityData, and double-click Setup.exe.
Step 3 Follow the on-screen prompts.
You do not need to restart the server before you run the Database Import utility.
To run the Cisco Unity Database Import utility
Step 1 Log on to Windows by using the account that was used to install Cisco Unity.
Step 2 Note and write down the current maximum size of the paging file (virtual memory) on the Cisco Unity server.
Step 3 Increase the maximum size of the paging file on the Cisco Unity server to 2 GB (2000 MB).
Step 4 Insert Cisco Unity 3.0 Disc 1 in the CD-ROM drive.
Step 5 Browse to the directory MigrationTools\ImportUnityData, and double-click Setup.exe.
Step 6 Follow the on-screen prompts. Note the following:
•The Windows 2000 password is not changed for existing Exchange accounts. The password that you specify is used only when new users are created.
•The phone password cannot be exported, so the Cisco Unity Database Import utility lets you set a default password during import. We recommend that you also click Set All Users for First Time Enrollment. This requires subscribers to go through the first-time enrollment conversation and requires them to change their phone password the first time they log on to Cisco Unity.
•The Cisco Unity Database Import utility allows imports only onto newly installed systems. If you try to import into a system to which you have added Cisco Unity subscribers or call handlers, the import will terminate with an error message.
•After subscriber information is imported, subscribers are homed on the same Exchange server that they were homed on before you exported them by using the Cisco Unity Database Export utility. If a subscriber in the database is not found in Exchange, the Database Import utility will create a new Exchange account on the Cisco Unity server. If Exchange is not installed on the Cisco Unity server, the account will be created on the Exchange server to which Cisco Unity connects.
For information on moving subscribers between Exchange servers, see the "Moving Subscriber Mailboxes" section in the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide.
Step 7 Reset the maximum size of the paging file on the Cisco Unity server to the value you noted and wrote down in Step 2.
To review the error log for errors
Step 1 Open the error log file (the default is C:\DBImport.log).
Step 2 Search for the string (error).
Step 3 If you find any instances of the string (error), determine the cause. Error descriptions are detailed. Note the following:
•On the same line as the string (error) is an explanation of what caused the error (for example, Menu entry destination link not found in target directory). The lines immediately before the string (error), up to the previous appearance of the string **Starting record**, identify the object and, if applicable, the part of the object (for example, the name of the call handler and the specific menu option that caused the error).
•If you cannot tell from the name of the object what type of object it is, search backward again for the previous appearance of the string Importing. This line indicates the type of object (for example, Importing Call Handlers, first pass).
•The Database Import utility passes through the database twice, once to create objects and a second time to create the links between them. As a result, errors for one object may appear in two different places in the error log.
Step 4 Fix the error as appropriate. If necessary, contact Cisco TAC for assistance.
To run Exchange Optimizer (Exchange 5.5 only)
Step 1 On the Windows Start menu, click Programs > Microsoft Exchange > Microsoft Exchange Optimizer.
Step 2 Follow the on-screen prompts.
Re-entering Custom Data
Deleting Unneeded Cisco Unity Subscribers
In some cases, after you upgrade to Cisco Unity 3.0, two Cisco Unity subscribers become associated with the same Active Directory account. As a result, each time someone logs on to Windows by using that Active Directory account and then tries to access the Cisco Unity Administrator, a page appears asking which Cisco Unity subscriber to log on as. If you encounter this problem, do the following procedure to delete unneeded Cisco Unity subscribers.
To delete unneeded Cisco Unity subscribers
Step 1 Access the Cisco Unity Administrator.
A page appears that reads: "Your Windows Domain Account [<Domain name>\
<Active Directory account name>] is associated with multiple Cisco Unity subscribers." The list on this page includes all of the Cisco Unity subscribers that are associated with the Active Directory account that you used to log on to Windows.
Step 2 Write down the names of the Cisco Unity subscribers you want to delete.
Caution Do not delete the Unity Installer - <
Servername> account.
Step 3 Click Unity Installer - <Servername>, and click Log In.
Step 4 Go to the Subscriber pages and delete the subscribers whose names you wrote down in Step 2.
Step 5 Run the Directory Walker utility to determine whether deleting the subscribers introduced any inconsistencies into the database. See the procedure "To run the Cisco Unity Directory Walker utility" in the "Reviewing the Consistency of the Cisco Unity 2.x Database" section.
Step 6 Correct inconsistencies found by Directory Walker, if any.
Resetting Custom Settings
As noted in the "Phone system settings" section, the "Call routing rules" section, and the "Phone system files and Windows registry keys" section, some settings from the Cisco Unity 2.x system were not automatically imported into the Cisco Unity 3.0 system. You may want to:
•Selectively reapply changes to the Windows 2000 registry or to phone system files. (If you do not have a current backup of the registry, start Regedit, click Registry > Export Registry File, and save the registry settings to a file.)
Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. Note that a typical backup of the Cisco Unity server does not back up the registry. Refer to the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe for additional information. If you have any questions about changing registry key settings, contact Cisco TAC.
•Copy custom prompts to the new system, and test the conversation to ensure that the custom prompts still fit with the modified Cisco Unity 3.0 conversation.
•Re-enter settings on the Cisco Unity Administrator Configuration pages.
•Recreate routing rules.
•Re-enter holidays manually, if you upgraded a Cisco Unity system earlier than version 2.4.
Importing Public Distribution Lists
If you exported Exchange 5.5 PDLs to a CSV file, you can now import them into Exchange 5.5 or into Active Directory.
On a Cisco Unity 3.0 system with Exchange 5.5, import the CSV file back into Exchange 5.5. On a Cisco Unity 3.0 system with Exchange 2000, use the Microsoft Csvde utility to import the CSV file into Active Directory groups.
After you import the CSV file into Exchange 5.5 or Active Directory, create a public distribution list in the Cisco Unity Administrator by using the Import option.
For information on:
Resetting the Dialogic Quiet Parameter
If you removed Dialogic voice card software earlier, do the following procedure to reset the quiet parameter to the value you identified in the "Removing Voice Card Software" section.
To reset the Dialogic quiet parameter
Step 1 Exit the Cisco Unity software, if it is running. For more information, see "Exiting and Starting the Cisco Unity Software and Server."
Step 2 Click Programs > Administrative Tools > Services.
Step 3 In the right pane of the Services dialog box, right-click Telephony, and click Stop.
Step 4 If you are prompted to stop other services, click Yes.
Step 5 On the Windows Start menu, click Programs > Dialogic System Software > Dialogic Configuration Manager-DCM.
The tree-structured list contains an entry for each Dialogic card installed in the server.
Step 6 On the Service menu, click Stop Service.
Step 7 Double-click a card in the tree list.
Step 8 In the Properties dialog box for the card, click the Misc tab.
Step 9 Under Parameter, click ParameterFile.
Step 10 In the Value box, enter quiet<XX>.prm (where XX = the -dBm level of the desired quiet parameter file).
Step 11 Click OK.
Step 12 Repeat Steps 7 through 11 for each additional card.
Step 13 Restart the server.
Feedback