SQL 2000 Server 2000 xxx serial key or number

Table Of Contents

Release Notes for Cisco Unity Release 4.0(2)

Contents

System Requirements, and Supported Hardware and Software

Compatibility Matrixes

Hewlett-Packard Service Pack for ProLiant DL380 G2 Server

Determining the Software Version

Cisco Unity

Cisco Unity-CM TSP

Cisco Unity Voice Connector for Microsoft Exchange

G.729a Audio Codec

RealSpeak Engine

Important Information to Note from Earlier Cisco Unity 4.0(x) Release Notes

Exchange Is No Longer Supported on the Cisco Unity Server for Unified Messaging

Downloading Software for Cisco Unity 4.0(2)

Downloading CD Images of Cisco Unity 4.0(2)

Downloading CD Images of Service Packs for Cisco Unity 4.(02)

Upgrading to Cisco Unity 4.0(2) from Version 4.0(1)

Task List for Upgrading to Cisco Unity 4.0(2) from Version 4.0(1)

Upgrading and Configuring the Cisco Unity Software

Upgrading to Cisco Unity 4.0(2) from Version 3.x or 2.x

New and Changed Support—Release 4.0(2)

Cisco Unity Tools Depot

IBM Lotus Notes 5.0.11 Supported on a Cisco Unity with Domino Server

Phone System Integrations Qualified for Use with Cisco Unity

Software Qualified for Use on Cisco Unity Subscriber Workstations

SQL Server 2000/MSDE 2000 Service Pack 3 Is Required, and Service Pack 3a Is Not Supported Yet

Third-Party Fax Integrations Supported with Cisco Unity with IBM Lotus Domino

Windows 2000 Advanced Server Is Required on New Platform Overlay 4 and 5 Servers

Windows Automatic Update Supported

New and Changed Functionality—Release 4.0(2)

Cisco Personal Communications Assistant Help

Cisco Unity Bulk Import Wizard

Cisco Unity Greetings Administrator

Cisco Unity Installation and Configuration Assistant

Cisco Unity with Exchange: Active Directory Contacts Deleted When Associated External Subscribers Are Deleted

Cisco Unity with Exchange: Disabling the Automatic Directory Synchronization of Bridge Subscribers

Customizing the Subscriber Conversation: Changing How Subscribers Confirm Message Addressing

Support for Copies of Configuration Files for Circuit-Switched Phone Systems

Installation and Upgrade Notes

Cisco Unity Malfunctions After Exchange 2000 EDSLock Script Is Run

Cisco Unity Phone Conversation System Prompts

Cisco Unity with Exchange: ViewMail for Microsoft Outlook No Longer Controlled by Class of Service

Upgrade Effect on Diagnostic Traces and the Intel Dialogic Quiet Parameter

Upgrades from Cisco Unity Versions Earlier than 2.3(4.104) Are Not Supported

Using Japanese and Mainland Mandarin Text to Speech

Limitations and Restrictions

Cisco Unity Bulk Import Wizard

Digital Networking

Call Transfer Settings Unavailable

Message Sender Is Unknown and Message Recipient Cannot Reply

Dual NICs

Replacing Disks in a RAID

Cisco Unity with Exchange: Subscriber Lookups Fail to Find Subscriber Names in Japanese

Text to Speech Does Not Play Name in From Field

Windows Terminal Services

Caveats

Open Caveats—Release 4.0(2)

Resolved Caveats—Release 4.0(2)

Documentation Updates

Errors

Obtaining License Files for Additional Features: Cisco Unity Installation Guide

Changes

Creating an Integration for a Circuit-Switched Phone System: Cisco Unity Integration Guides

Omissions

Determining the Cause of Failover or Failback: Cisco Unity Failover Configuration and Administration Guide

Viewing License Pooling Information: Cisco Unity System Administration Guide

Troubleshooting

Installing a Cisco Unity Demonstration System

Limits on a Cisco Unity Demonstration System

Default License File

Time-Limited License File

Enabling a Cisco Unity Demonstration System with the Default License File

Enabling a Cisco Unity Demonstration System with the Time-Limited License File

Converting a Cisco Unity Demonstration System to a Standard System

Cisco Unity Documentation

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Website

Cisco TAC Escalation Center

Obtaining Additional Publications and Information

Release Notes for Cisco Unity Release 4.0(2)

Revised June 26, 2003

These release notes describe upgrade instructions, new and changed support, new and changed functionality, limitations and restrictions, open and resolved caveats, and documentation updates for Cisco Unity^™ Release 4.0(2).

The latest software upgrades for Cisco Unity 4.0 are available on the Cisco Unity 4.0 Software Download page at http://www.cisco.com/pcgi-bin/tablebuild.pl/unity-40.

Note Confirm that you have the latest software version available and that you are using the corresponding version of the Cisco Unity Installation Guide. The guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Contents

These release notes contain the following sections:

•System Requirements, and Supported Hardware and Software

•Determining the Software Version

•Important Information to Note from Earlier Cisco Unity 4.0(x) Release Notes

•Downloading Software for Cisco Unity 4.0(2)

•Upgrading to Cisco Unity 4.0(2) from Version 4.0(1)

•Upgrading to Cisco Unity 4.0(2) from Version 3.x or 2.x

•New and Changed Support—Release 4.0(2)

•New and Changed Functionality—Release 4.0(2)

•Installation and Upgrade Notes

•Limitations and Restrictions

•Caveats

•Documentation Updates

•Troubleshooting

•Installing a Cisco Unity Demonstration System

•Cisco Unity Documentation

•Obtaining Documentation

•Obtaining Technical Assistance

•Obtaining Additional Publications and Information

System Requirements, and Supported Hardware and Software

The following documents list the most current Cisco Unity requirements, and are available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html.

•Cisco Unity 4.0 System Requirements, and Supported Hardware and Software

•Cisco Unity Bridge System Requirements, and Supported Hardware and Software

•Cisco Unity Networking Options Requirements (With Microsoft Exchange)

Compatibility Matrixes

The following matrixes list the most current version combinations qualified for use with Cisco Unity. The matrixes are available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html.

•Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations

•Compatibility Matrix: Cisco Unity, the Cisco Unity-CM TSP, and Cisco CallManager

•Compatibility Matrix: Required and Recommended Third-Party Service Packs.

Hewlett-Packard Service Pack for ProLiant DL380 G2 Server

A customer-provided Hewlett-Packard ProLiant DL380 G2 server with a Magma expansion chassis and a system BIOS version P23 or earlier requires installation of service pack SP20496, available from the Hewlett-Packard/Compaq website at ftp://ftp.compaq.com/pub/softpaq/sp20001-20500/sp20496.exe.

Determining the Software Version

This section contains procedures for determining the version in use for the following software:

•Cisco Unity

•Cisco Unity-CM TSP

•Cisco Unity Voice Connector for Microsoft Exchange

•G.729a Audio Codec

•RealSpeak Engine

Cisco Unity

To determine the Cisco Unity version in use by using the Cisco Unity Administrator

In the Cisco Unity Administrator, go to the System > Configuration > Software Versions page. The Cisco Unity version is displayed in the Cisco Unity Build Number field.

To determine the Cisco Unity version in use by using the AvCsMgr.exe file (Cisco Unity 3.0(4) and later)

Step 1 Browse to the CommServer directory.

Step 2 Right-click AvCsMgr.exe, and click Properties.

Step 3 In the Properties window, click the Version tab.

Step 4 In the Item Name list, click Product Version. The Cisco Unity version is displayed in the Value window.

Cisco Unity-CM TSP

To determine the Cisco Unity-CM TSP version in use by using the Cisco Unity Telephony Integration Manager

Step 1 Double-click the Cisco Unity Tools Depot icon on the desktop.

Step 2 Under Switch Integration Tools, double-click Telephony Integration Manager.

Step 3 In the Cisco Unity Telephony Integration Manager, go to the Cisco CallManager > Properties page. The Cisco Unity-CM TSP version is displayed in the TSP Version field.

To determine the Cisco Unity-CM TSP version in use by using the AvSkinny.tsp file

Step 1 Browse to the WinNT\System32 directory.

Step 2 Right-click AvSkinny.tsp, and click Properties.

Step 3 In the Properties window, click the Version tab.

Step 4 In the Item Name list, click Product Version. The Cisco Unity-CM TSP version is displayed in the Value window.

Cisco Unity Voice Connector for Microsoft Exchange

This section contains two procedures. Do the procedure for your version of Cisco Unity.

To determine the Voice Connector version in use: Cisco Unity 4.0 and later, Voice Connector 10.0 and later

Step 1 Log on to the Exchange server on which the Voice Connector is installed.

Step 2 In Windows Explorer or My Computer, browse to the appropriate folder:

•Exchange 2000:<ExchangeServerPath>\VoiceGateway\bin

•Exchange 5.5:<ExchangeServerPath>\connect\voice\bin

Step 3 Right-click GwIvc.exe, and select Properties.

Step 4 Click the Version tab in the Properties window.

Step 5 Click Product Version in the Item Name box to view the product version in the Value box.

To determine the Voice Connector version in use: Cisco Unity 3.0 through 3.1

Step 1 Log on to the Exchange server on which the Voice Connector is installed.

Step 2 In Windows Explorer or My Computer, browse to the appropriate folder:

•Exchange 2000:
<ExchangeServerPath>\VoiceGateway\bin\LocalizedFiles\ENU.

•Exchange 5.5:<ExchangeServerPath>\voice\bin\LocalizedFiles\ENU.

Step 3 Right-click SetupRes.dll, and select Properties.

Step 4 Click the Version tab in the Properties window to view the File Version.

G.729a Audio Codec

When the G.729a audio codec has been installed on the Cisco Unity server or on a subscriber workstation, use the following procedure to determine the codec version.

To determine the G.729a audio codec version in use

Step 1 Browse to the Winnt\System32 directory.

Step 2 Right-click Sl_g729a.acm, and click Properties.

Step 3 Click the Version tab.

Step 4 In the Items list, click Product Version. The G.729a audio codec version is displayed in the Value window.

RealSpeak Engine

To determine the RealSpeak ENU language engine version in use

Step 1 Browse to the CommServer\RealSpeak\Engine directory.

Step 2 Right-click Enu_g2p.dll, and click Properties.

Step 3 Click the Version tab.

Step 4 In the Items list, click Product Version. The File version corresponds to the following RealSpeak versions:

•3.6.0.0 = RealSpeak ENU language engine version 3.0(1)

•2.11.0.0 = RealSpeak ENU language engine version 2.1(1)

•2.1.0.0 = RealSpeak ENU language engine version 2.0(1)

To determine the RealSpeak base engine version in use

Step 1 Browse to the CommServer\RealSpeak\Api\Lib directory.

Step 2 Right-click Lhstts.dll, and click Properties.

Step 3 Click the Version tab.

Step 4 In the Items list, click Product Version. The File version corresponds to the following RealSpeak versions:

•2.13.0.0 = RealSpeak base engine version 3.0(1)

•2.12.0.0 = RealSpeak base engine version 3.0(0)

•2.11.0.0 = RealSpeak base engine version 2.1(1)

•2.1.0.0 = RealSpeak base engine version 2.0(1)

Important Information to Note from Earlier Cisco Unity 4.0(x) Release Notes

This section contains information worth noting from the Cisco Unity 4.0(1) release notes. Release notes for all versions of Cisco Unity are available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Exchange Is No Longer Supported on the Cisco Unity Server for Unified Messaging

When Cisco Unity with Exchange is configured as Unified Messaging, Exchange cannot be installed on the Cisco Unity server for Cisco Unity 4.0(x). You must either move Exchange users to other Exchange servers or, if there are no other Exchange servers, you must install Exchange on another server and move Exchange users to the new server.

(When Cisco Unity is configured as Voice Messaging, Exchange 5.5 is supported on a Cisco Unity 4.0 server only if you are upgrading from a previous version of Cisco Unity. Exchange 2000 is supported on the Cisco Unity server both for upgrades and for new installations in the Voice Messaging configuration.)

Downloading Software for Cisco Unity 4.0(2)

This section contains procedures for downloading full CD images of Cisco Unity version 4.0(2) software and of third-party service packs from the Cisco Software Center website:

•Downloading CD Images of Cisco Unity 4.0(2), below

•Downloading CD Images of Service Packs for Cisco Unity 4.(02)

Downloading CD Images of Cisco Unity 4.0(2)

Table 1 lists the contents of the Cisco Unity 4.0(2) CD images. The images contain only Cisco Unity software. They do not contain any third-party software.

To download full images of Cisco Unity CDs

Step 1 Use Table 1 to determine which Cisco Unity 4.0(2) CD images to download. You always need CD 1.

Step 2 Confirm that the computer you are using has up to 680 MB of hard disk space for each of the applicable full Cisco Unity 4.0(2) images, in addition to the space required to download the image. (The download file sizes appear on the Cisco Software Center website.)

Step 3 On a computer with a high-speed Internet connection, go to the Software Center website at http://www.cisco.com/public/sw-center/sw-voice.shtml.

Step 4 Click Unity 4.0 under "Cisco Unity Software."

Step 5 On the Cisco Unity 4.0 Software Download page, click the name of the file to download.

Step 6 Follow the on-screen prompts to complete the download. Note that each file may take more than 10 minutes to download.

Step 7 Repeat Step 5 and Step 6 for each file that you need.

Step 8 When all downloads are complete, extract the files for each CD to a separate directory:

a. In Windows Explorer, double-click the file.

b. In WinZip, specify a directory to which the files will be extracted.

Step 9 If you plan to install Cisco Unity 4.0(2) from new compact discs, create a new 4.0(2) Cisco Unity Disc <N> for each image.

Step 10 When you are done extracting the files, delete the downloaded .exe files to free disk space.

Downloading CD Images of Service Packs for Cisco Unity 4.(02)

Table 2 lists the contents of the service pack CD images for Cisco Unity 4.0(2). Each CD image is available in multiple languages, noted by the three-letter language acronym in the file name (for example, the ENU in the name CiscoUnity4.0-ServicePacks-ENU-CD1.exe refers to U.S. English).

To download full images of service pack CDs

Step 1 Use Table 2 to determine which service pack CD images to download. You always need CD 1.

Whether you download CD 2 and CD 3 depends on the message store being used. (Note that for an upgrade to Cisco Unity 4.0(2) from version 4.0(1), you do not need to download the CD 2 and CD 3 images.)

Step 2 Confirm that the computer you are using has up to 680 MB of hard disk space for each of the applicable Cisco Unity 4.0(2) service pack images, in addition to the space required to download the image. (The download file sizes appear on the Cisco Software Center website.)

Step 3 On a computer with a high-speed Internet connection, go to the Software Center website at http://www.cisco.com/public/sw-center/sw-voice.shtml.

Step 4 Click Unity 4.0 under "Cisco Unity Software."

Step 5 On the Cisco Unity 4.0 Software Download page, click the name of the service pack file to download, in the applicable language. (The three letters that appear before the CD number in the file name refer to the language.)

Note For all languages, service pack CD 2 and CD 3 did not change between Cisco Unity versions 4.0(1) and 4.0(2). The CD 2 and CD 3 files on the Download page are still listed as being for version 4.0(1) and have an earlier date than the CD 1 files.

Step 6 Follow the on-screen prompts to complete the download.

Step 7 Repeat Step 5 and Step 6 for each service pack file that you need.

Step 8 When all downloads are complete, extract the files for each service pack CD to a separate directory:

a. In Windows Explorer, double-click the file.

b. In WinZip, specify a directory to which the files will be extracted. The following table lists the default locations of the unzipped service pack files (<XXX> is the language):

Step 9 When you are done extracting the files, delete the downloaded .exe files, to free disk space.

Upgrading to Cisco Unity 4.0(2) from Version 4.0(1)

For an upgrade from version 4.0(1), you download the applicable Cisco Unity 4.0(2) CD images from the Cisco Software Center website, and install from those images.

Use the following task list to upgrade Cisco Unity correctly. Some tasks in the list reference detailed instructions in the Cisco Unity Installation Guide, which is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

If you are upgrading a system configured for failover, start the upgrade on the primary Cisco Unity server. The task list alerts you when to begin upgrading the secondary server. Some failover tasks reference detailed instructions in the Cisco Unity Failover Configuration and Administration Guide, which is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.

Note The failover feature cannot be used for continuing Cisco Unity service on one server while upgrading the Cisco Unity software on the other server. Both the primary and secondary servers must be out of service while the Cisco Unity software is upgraded. The secondary server cannot handle voice messaging while the primary server is being upgraded.

Task List for Upgrading to Cisco Unity 4.0(2) from Version 4.0(1)

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

1. Back up the Cisco Unity system.

2. Download the applicable Cisco Unity 4.0(2) software CD images and the Cisco Unity Service Packs CD 1 image from the Software Center website. See the"Downloading Software for Cisco Unity 4.0(2)" section. (Note that you do not need to download the Cisco Unity Service Packs CD 2 and CD 3 images for the upgrade.)

3. If virus-scanning software or the Cisco IDS Host Sensor Agent is installed on the Cisco Unity server: Disable virus-scanning services and set the IDS Host Sensor Agent to run in On-Warning mode. Refer to the "Setting Security-Monitoring Software Before Running the Installation Programs" section of the "Customizing the Cisco Unity Platform" chapter of the Cisco Unity Installation Guide.

4. Run the Cisco Unity System Preparation Assistant to install SQL Server 2000 Service Pack 3 or MSDE 2000 Service Pack 3. Refer to the"Running the Cisco Unity System Preparation Assistant" section of the "Customizing the Cisco Unity Platform" chapter of the Cisco Unity Installation Guide.

5. Run the Cisco Unity Installation and Configuration Assistant to upgrade and configure the Cisco Unity software. See the "Upgrading and Configuring the Cisco Unity Software" section.

6. If virus-scanning software or the Cisco IDS Host Sensor Agent is installed on the Cisco Unity server: Re-enable virus-scanning services and reset the IDS Host Sensor Agent to run in On-Protecting mode. Refer to the "Resetting Security-Monitoring Software After the Installation Programs Have Been Run" section of the "Installing and Configuring Cisco Unity Software" chapter of the Cisco Unity Installation Guide.

7. If the system is configured for failover: Upgrade the secondary server and configure both servers for failover:

a. Run the Configure Cisco Unity Failover wizard on the primary Cisco Unity server. Refer to the "Configuring Failover on the Primary and Secondary Servers" section in the "Configuring Cisco Unity Failover" chapter of the Cisco Unity Failover Configuration and Administration Guide

b. Repeat Task 3. through Task 6. on the secondary Cisco Unity server.

c. Run the Configure Cisco Unity Failover wizard on the secondary Cisco Unity server. Refer to the "Configuring Failover on the Primary and Secondary Servers" section in the "Configuring Cisco Unity Failover" chapter of the Cisco Unity Failover Configuration and Administration Guide.

8. If you are modifying hardware or software, or adding features: Refer to the "Modifying the Cisco Unity 4.0 System" chapter of the Cisco Unity Installation Guide.

9. If the system is using the AMIS, Bridge, SMTP, or VPIM networking options: Upgrade the Cisco Unity Voice Connector for Microsoft Exchange, if applicable. Refer to the applicable version of release notes for the Voice Connector, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Upgrading and Configuring the Cisco Unity Software

Caution When you run the Cisco Unity Installation and Configuration Assistant, Cisco Unity is uninstalled and then reinstalled. Fields will contain values from the current installation. Do not change any values unless you are instructed to do so in the following procedure, or the system may not be updated correctly.

To upgrade and configure the Cisco Unity software

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

Step 2 From the location to which you saved the downloaded Cisco Unity CD 1 image files, browse to the root directory and double-click Setup.exe.

Step 3 If prompted, double-click the language of your choice to continue the upgrade.

Step 4 On the Cisco Unity Installation and Configuration Assistant Welcome screen, click Continue.

Step 5 In the main window of the assistant, click Run the Cisco Unity Setup Program.

Step 6 If prompted, double-click the language of your choice to continue the upgrade.

Step 7 If a message to stop services appears, click OK.

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

Step 9 In the Select Features dialog box:

a. Check the Upgrade Cisco Unity check box.

b. Uncheck the Install Voice Card Software check box.

Do not change any other values.

Step 10 Click Next or Continue without changing values until you are prompted to restart the Cisco Unity server.

Step 11 Check the Yes, I Want to Restart My Computer Now check box, and click Finish.

The Cisco Unity Installation and Configuration Assistant displays check marks next to "Install Cisco Unity" and "Install the Cisco Unity License Files," and the Configure the Cisco Unity Services screen appears in the main window.

Step 12 In the main window of the assistant, click Run the Cisco Unity Services Configuration Wizard. (Note that you should be logged on to Windows with the Cisco Unity installation account.)

Step 13 On the Welcome screen, click Next.

Step 14 Select the message store type, and click Next.

Step 15 Follow the on-screen prompts to complete the configuration.

The Cisco Unity Installation and Configuration Assistant displays a check mark next to "Configure the Cisco Unity Services," and the Configure the Cisco Unity Message Store screen appears in the main window.

Step 16 In the main window of the assistant, click Run the Cisco Unity Message Store Configuration Wizard. (Note that you should be logged on to Windows with the Cisco Unity installation account.)

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

Step 18 On the Welcome screen, click Next.

Step 19 Follow the on-screen prompts.

Step 20 When the message store configuration is complete, click Finish.

The Cisco Unity Installation and Configuration Assistant displays a check mark next to "Configure the Cisco Unity Message Store."

Step 21 When the Summary screen appears, click Close.

Upgrading to Cisco Unity 4.0(2) from Version 3.x or 2.x

For upgrades from Cisco Unity version 3.x or 2.x, refer to the applicable chapter of the Cisco Unity Installation Guide:

•Chapter 13, "Upgrading Cisco Unity Version 3.x to Version 4.0"

•Chapter 14, "Upgrading a Cisco Unity 2.x System to Version 4.0"

The Cisco Unity Installation Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

New and Changed Support—Release 4.0(2)

This section contains information about new and changed support in the Cisco Unity Release 4.0(2) time frame only. Refer to the release notes of the applicable version for information about new and changed support with earlier versions of Cisco Unity. Release notes for all versions of Cisco Unity are available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Cisco Unity Tools Depot

The following tools have been updated or are new in the Tools Depot. The Cisco Unity Tools Depot icon is available on the Cisco Unity server desktop.

The left pane of the Tools Depot lists all available tools by category. To display online Help for a tool, click the name in the left pane. To run the tool, double-click the name.

Some tools work only with selected versions of Cisco Unity. If a tool does not appear in the Tools Depot, it does not work with the version of Cisco Unity currently running.

IBM Lotus Notes 5.0.11 Supported on a Cisco Unity with Domino Server

Cisco Unity versions 4.0(2) and later support IBM Lotus Notes 5.0.11 as a messaging client on a Cisco Unity with IBM Lotus Domino server.

Phone System Integrations Qualified for Use with Cisco Unity

The following phone system integrations have been qualified for use with Cisco Unity:

•ECI Coral III

•Fujitsu 9600

For the most current list of all supported phone system integrations—including integrations qualified since the release of Cisco Unity version 4.0(2)—refer to the "Supported Phone System Integrations" section in Cisco Unity 4.0 System Requirements, and Supported Hardware and Software on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html.

Software Qualified for Use on Cisco Unity Subscriber Workstations

Cisco Unity version 4.0(2) with IBM Lotus Domino supports IBM Lotus Notes version 5.0.10 for use as a messaging client on Cisco Unity subscriber workstations.

For the most current version combinations of software qualified for use on subscriber workstations—including software qualified since the release of Cisco Unity version 4.0(2)—refer to Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html.

SQL Server 2000/MSDE 2000 Service Pack 3 Is Required, and Service Pack 3a Is Not Supported Yet

Because of the recent W32.Slammer worm, Cisco is requiring Service Pack 3 for SQL Server 2000 and MSDE 2000 with Cisco Unity versions 3.0(1) and later. Procedures in these release notes and in the Cisco Unity Installation Guide, Release 4.0(2), for upgrading to and installing Cisco Unity 4.0(2) have been updated to reflect the change.

Caution Do not install SQL Server 2000/MSDE 2000 Service Pack 3a on the Cisco Unity server. Service Pack 3a is currently being qualified for use with Cisco Unity. The testing done so far suggests that you may need to make some configuration changes to use Service Pack 3a on the Cisco Unity server. Do not install Service Pack 3a until it has been qualified, or Cisco Unity may stop working.

Third-Party Fax Integrations Supported with Cisco Unity with IBM Lotus Domino

Cisco Unity with Domino supports third-party fax integrations.

For a complete list of qualified third-party fax products, refer to the "Supported Fax Server Software" section of the Cisco Unity 4.0 System Requirements, and Supported Hardware and Software on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html.

Windows 2000 Advanced Server Is Required on New Platform Overlay 4 and 5 Servers

Windows 2000 Advanced Server (in English, German, French, or Japanese) is required for a new installation of Cisco Unity on a Platform Overlay 4 or 5 server. It is also required for an existing Cisco Unity site that purchases an additional Cisco Unity Platform Overlay 4 or 5 server or is replacing a Cisco Unity server with a new Platform Overlay 4 or 5 server. (Platform overlays are defined in the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.)

Note that Windows 2000 Advanced Server is included with Cisco Unity Platform Overlay 4 and 5 servers purchased from Cisco. If the server is not purchased from Cisco, the customer also must purchase Windows 2000 Advanced Server.

You are not required to upgrade existing Cisco Unity servers to Windows 2000 Advanced Server. However, if you are using Cisco Unity with Microsoft Exchange, you may want to upgrade for performance reasons as described in Cisco Unity Virtual Memory Usage Troubleshooting and Workaround, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_tech_notes_list.html. If you choose to upgrade from Windows 2000 Server to Windows 2000 Advanced Server, do the following procedure.

Caution The following procedure does not work when Domino is the message store, because the Disaster Recovery Tool does not support Domino.

To upgrade from Windows 2000 Server to Windows 2000 Advanced Server (optional, Exchange only)

Step 1 Download the latest version of the Cisco Unity Disaster Recovery Tool (DiRT) from http://ciscounitytools.com/.

Step 2 Back up Cisco Unity data by using DiRT. For more information, refer to the DiRT online Help and the streaming video training available on http://ciscounitytools.com/.

Caution The restore will fail if you do not follow the instructions in the DiRT online Help. For example, you cannot restore data to a version of Cisco Unity different from the one you backed up.

Step 3 If Exchange is installed on the Cisco Unity server: Back up messages by using Veritas Backup Exec or another Exchange-aware backup utility.

Step 4 Reinstall all software on the Cisco Unity server. Refer to "Part 1: Installing and Configuring the Cisco Unity Server" in the "Mandatory Tasks for Installing Cisco Unity" chapter of the Cisco Unity Installation Guide, Release 4.0(2), available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Step 5 If Exchange is installed on the Cisco Unity server: Restore messages by using the backup that you made in Step 3.

Step 6 Restore Cisco Unity data by using DiRT. Refer to the DiRT online Help.

Step 7 Restore settings that are not saved by DiRT (for example, any mappings made with the GrantUnityAccess tool). Refer to the DiRT online Help.

Windows Automatic Update Supported

Windows Automatic Update (WAU) is supported on a Cisco Unity 4.0(x) and later server, and on a Cisco Unity Bridge 2.1(x) and later server when the option Notify Me Before Downloading Any Updates and Notify Me Again Before Installing Them on My Computer is selected. (Note that if Cisco Unity Platform Configuration Disc revision 12 or later is used to configure the platform for the Cisco Unity or Cisco Unity Bridge server, then WAU is disabled.)

Caution Configure WAU only to check for updates, not to install updates. Most Microsoft updates can be installed on the Cisco Unity or Cisco Unity Bridge server as soon as they become available. However, Microsoft service packs must be qualified for use with Cisco Unity and the Cisco Unity Bridge, and WAU does not let you distinguish between service packs and other updates.

For Microsoft service pack and update support policy information, refer to Compatibility Matrix: Required and Recommended Third-Party Service Packs, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html.

New and Changed Functionality—Release 4.0(2)

This section contains information about new and changed functionality for Cisco Unity Release 4.0(2) only. Refer to the release notes of the applicable version for information about new and changed functionality in earlier versions of Cisco Unity. Release notes for all versions of Cisco Unity are available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Cisco Personal Communications Assistant Help

Online Help for the Cisco Personal Communications Assistant (PCA) is available on the Cisco Unity software discs. You do not need to download it separately from the Cisco Software Center website, nor do you need to install it. It is installed automatically when Cisco Unity is installed.

Cisco Unity Bulk Import Wizard

The Cisco Unity Bulk Import wizard allows you to modify existing subscriber accounts on Cisco Unity with Domino and Cisco Unity with Exchange systems.

In addition, on a Cisco Unity with Exchange system, DELIVERY_LOCATION_ID is now a valid, optional column header in CSV files used to create AMIS, Bridge, or VPIM subscriber accounts with multiple delivery locations.

For additional Cisco Unity Bulk Import wizard information, see the "Limitations and Restrictions" section.

Cisco Unity Greetings Administrator

When a public distribution list owns a call handler, the Cisco Unity Greetings Administrator allows each member of the public distribution list to manage call handler greetings by using the Cisco Unity phone conversation.

For example, the public distribution list members can call Cisco Unity from any site to:

•Rerecord a call handler greeting.

•Enable or disable the alternate greeting for a call handler.

•Determine which greeting is currently active for a call handler.

In previous versions of Cisco Unity, the Cisco Unity Greetings Administrator was not available for use when a public distribution list owned a call handler. Only individual subscribers who owned call handlers could use the Cisco Unity Greetings Administrator. (Note that the call handler owner is not necessarily the message recipient.)

Cisco Unity Installation and Configuration Assistant

The Cisco Unity Installation and Configuration Assistant is now used for installing or upgrading a system with failover, and for adding licensed features to a system with or without failover. In Cisco Unity 4.0(1), the assistant was used only to install a new Cisco Unity system without failover.

Cisco Unity with Exchange: Active Directory Contacts Deleted When Associated External Subscribers Are Deleted

When AMIS, Bridge, or VPIM subscribers (referred to collectively as external subscribers) are deleted in the Cisco Unity Administrator—either by deleting the subscriber accounts individually or by deleting the associated delivery location—the underlying Active Directory contacts (or in the case of AMIS subscribers, the underlying Exchange 5.5 custom recipients) are automatically deleted. When you delete an Internet subscriber in the Cisco Unity Administrator, a dialog box is displayed that allows you to optionally delete the associated contact (or custom recipient).

Note that for regular Cisco Unity subscribers, the option to delete the associated accounts in Active Directory or Windows and Exchange is not provided. Because of the security risk of accidentally deleting messages for a user and denying a user access to the Windows domain, the associated accounts and Exchange mailboxes have to be deleted by using standard Microsoft tools after deleting the subscribers in the Cisco Unity Administrator.

Cisco Unity with Exchange: Disabling the Automatic Directory Synchronization of Bridge Subscribers

On a Cisco Unity server configured for networking with the Cisco Unity Bridge, the CsBridgeConnector service can be customized to disable the automatic creation, modification, and deletion of Bridge subscribers. For more information, see the "Disabling the Automatic Creation, Modification, and Deletion of Bridge Subscribers (Cisco Unity 4.0(2) and Later)" section in the "Bridge Networking" chapter of the Cisco Unity Bridge Networking Guide, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.

Customizing the Subscriber Conversation: Changing How Subscribers Confirm Message Addressing

The Cisco Unity subscriber conversation can be customized to alter how Cisco Unity prompts a subscriber to confirm message addressing. By default, when a subscriber addresses a message, Cisco Unity plays the recorded name and extension of the intended recipient (when there is no recorded name, Cisco Unity plays the extension instead) and asks the subscriber to confirm that the recipient is correct.

A new registry setting allows you to alter the subscriber conversation during message addressing. Table 4 lists the confirmation prompts that subscribers hear with the available values for the registry setting.

You use the Advanced Settings Tool to change the registry setting. For details, refer to the "Cisco Unity Conversation" chapter in the Cisco Unity System Administration Guide, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guides_list.html.

Support for Copies of Configuration Files for Circuit-Switched Phone Systems

When you are creating an integration with a circuit-switched phone system and have made a copy of the .ini configuration file for your phone system in the CommServer\IntLib directory, the Telephony Integration Setup wizard and the Cisco Unity Telephony Integration Manager (UTIM) offer you the choice of the applicable configuration files.

This feature is useful when you modify the contents of the configuration file but want to keep a copy of the original file available for reference.

Please see the below approaches,

Approach 1: Using INFORMATION_SCHEMA.TABLES view

We can write a query like below to check if a Customers Table exists in the current database.

Approach 2: Using OBJECT_ID() function

We can use OBJECT_ID() function like below to check if a Customers Table exists in the current database.

Approach 3: Using sys.Objects Catalog View

We can use the Sys.Objects catalog view to check the existence of the Table as shown below:

Approach 4: Using sys.Tables Catalog View

We can use the Sys.Tables catalog view to check the existence of the Table as shown below:

Approach 5: Avoid Using sys.sysobjects System table

We should avoid using sys.sysobjects System Table directly, direct access to it will be deprecated in some future versions of the Sql Server. As per Microsoft BOL link, Microsoft is suggesting to use the catalog views sys.objects/sys.tables instead of sys.sysobjects system table directly.

referred from: http://sqlhints.com/2014/04/13/how-to-check-if-a-table-exists-in-sql-server/

Important: If you haven't already done so, take the time to read the How To Make A Request guide and our comprehensive Posting Guidelines. Posting or requesting serials which do not meet our criteria for abandonware/beta software will result in a ban.

The serials provided in the posts below are supplied and compiled by our helpful visitors. We cannot guarantee any particular serial will work for you, however if you try enough you'll find one. We are slowly building a list of verified serials, shown below in this specific post.

If you have used a serial successfully, please post and let us know which serial and with what software you used it on!

Tested & Verified Working Serials

Windows 95A Upgrade
049-6301576

Windows 98 Second Edition
RW9MG-QR4G3-2WRR9-TG7BH-33GXB
RC7JH-VTKHG-RVKWJ-HBC3T-FWGBG

Windows Millennium
B88DH-VQ89B-G4WWK-DCBP2-7B7PW
HBTD9-6P338-XT2MV-QBTTF-WPGGB

Windows 2000 Professional SP4
DDTPV-TXMX7-BBGJ9-WGY8K-B9GHM