•A list of settings for the previous voice messaging system configuration, including extensions, transfer settings, and caller input settings. (Subscriber information can be imported from Microsoft Exchange, and from phone systems and voice messaging systems that can generate comma-delimited files.)

If the site had no previous voice messaging system, then you need a list of extensions.

Cisco Unity Activation Code

You must have an activation code for the system key to complete the Cisco Unity installation or upgrade. (To set up failover, you must have two activation codes, one for each Cisco Unity server.)

Cisco sends an e-mail with the code—which activates license settings—once the Cisco Unity software has been registered on Cisco.com.

A registration notice shipped with Cisco Unity contains instructions for registering the software. The resulting e-mail from Cisco instructs the recipient to save the code to a blank disk labeled "Cisco Unity Activation Code" and to store the disk with the Cisco Unity software and documentation.

If the Cisco Unity software has not been registered, do so immediately because it can take up to one business day to receive the activation code for the system key. See the following section, "Registering Cisco Unity," for instructions on registering the software and on getting another copy of the activation code, if it has been misplaced.

The Cisco Unity installation instructions later in this chapter explain when to use the activation code.

Registering Cisco Unity

The Cisco Unity system key is shipped with a minimal number of settings. To activate the system key so that it includes the settings purchased by the customer, the Cisco Unity software must be registered on Cisco.com.

Within one business day of registration, you will receive an e-mail with a Cisco Unity activation code.

Registrations are processed only during regular business hours.

Caution You cannot complete the installation without a Cisco Unity activation code.

The following information is required during registration:

•The serial number (printed on the system key).

•Product authorization key, or PAK (printed on the sticker on the back of the Cisco Unity CD 1 sleeve).

To Register Cisco Unity on Cisco.com

Step 1 Browse to the applicable software registration site (URLs are case sensitive):

Within one business day of registration, you will receive an e-mail with the Cisco Unity activation code. (If the Cisco Unity activation code is misplaced or lost, it can take up to one business day to get another copy.)

If you do not receive the activation code within one business day or to get another copy of the activation code, call the Cisco Technical Assistance Center (TAC) and ask for the Licensing Team:

The way in which logical drives on the Cisco Unity server are set up and which application, log, and database files are located on the drives depend on the size of the Cisco Unity system, the RAID volume configuration used, whether the system will be installed as Voice Messaging (VM) or as Unified Messaging (UM), and whether Exchange is used on a separate server or on the Cisco Unity server.

Note If the system is using failover, the file locations must be the same on the primary and secondary servers.

Using one of the following sections, make note of the applicable drive locations for files on the Cisco Unity system that you are installing:

Warning This unit is intended for installation in restricted access areas. A restricted access area can be accessed only through the use of a special tool, lock and key, or other means of security.

Warning Read the installation instructions before connecting the system to the power source.

Warning Before working on a system that has an on/off switch, turn OFF the power and unplug the power cord.

Warning This equipment must be grounded. Never defeat the ground conductor or operate the equipment in the absence of a suitably installed ground conductor. Contact the appropriate electrical inspection authority or an electrician if you are uncertain that suitable grounding is available.

Warning There is the danger of explosion if the battery is replaced incorrectly. Replace the battery only with the same or equivalent type recommended by the manufacturer. Dispose of used batteries according to the manufacturer's instructions.

Warning To prevent bodily injury when mounting or servicing this unit in a rack, you must take special precautions to ensure that the system remains stable. The following guidelines are provided to ensure your safety: · This unit should be mounted at the bottom of the rack if it is the only unit in the rack. · When mounting this unit in a partially filled rack, load the rack from the bottom to the top with the heaviest component at the bottom of the rack. · If the rack is provided with stabilizing devices, install the stabilizers before mounting or servicing the unit in the rack.

Warning Before opening the chassis, disconnect the telephone-network cables to avoid contact with telephone-network voltages.

Warning Do not work on the system or connect or disconnect cables during periods of lightning activity.

Warning To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line cord.

Warning Only trained and qualified personnel should be allowed to install, replace, or service this equipment.

Warning This equipment is to be installed and maintained by service personnel only as defined by AS/NZS 3260 Clause 1.2.14.3 Service Personnel.

Warning The safety cover is an integral part of the product. Do not operate the unit without the safety cover installed. Operating the unit without the cover in place will invalidate the safety approvals and pose a risk of fire and electrical hazards.

Warning Blank faceplates and cover panels serve three important functions: they prevent exposure to hazardous voltages and currents inside the chassis; they contain electromagnetic interference (EMI) that might disrupt other equipment; and they direct the flow of cooling air through the chassis. Do not operate the system unless all cards, faceplates, front covers, and rear covers are in place.

Warning During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself.

Step 3 Set the switches and jumpers on each card. See Appendix A, "Voice Cards," for information on hardware settings for your cards.

Some cards include hardware settings that indicate which card is first, which is second, and so on. If you are installing more than one card of the same model, keep the cards in order so you can install them in the correct order in Step 4.

If you are installing Intel Dialogic D/120JCT-EURO or D/240PCI-T1 cards, do not do the procedure under "Software Settings" in Appendix A, "Voice Cards," at this time. The Cisco Unity Installation Guide alerts you when to do the procedure later in the installation.

Step 4 Insert each card firmly into its slot, and fasten each card to the computer backplate with a screw.

If you are installing more than one card of the same model, and if the cards include a hardware setting that indicates which card is first, second, and so on, install the cards in the order specified by the hardware settings.

If you are installing cards of different models in the same server, install cards of the same model adjacent to one another.

PCI cards can be put into either 32-bit or 64-bit, 33-MHz PCI slots.

All cards with H.100 bus (also known as CT bus) connectors must be installed in the same server. If all the cards do not fit in the Cisco Unity server, then you must install all of them in an expansion chassis.

Step 5 If you are installing multiple voice cards that have H.100 bus connectors, cable the cards together. On each card, connect the cable so the red stripe on the cable corresponds with pin 1 on the card connector. Confirm that the connectors are firmly seated.

Caution If you do not cable cards together as required, the voice card software will not start, and Cisco Unity will not answer calls.

If the cable has more connectors than the server has voice cards, use the first and last connectors, and leave unused connectors in the middle of the cable. If the end of a cable is allowed to dangle loose, it can act as a radio antenna and pick up noise from the bus.

If you are cabling three or more cards together, connect the first connector on the cable to the first card, the second connector to the second card, and so on.

Setting Up the Cisco Unity Server

Cisco recommends that you connect the Cisco Unity server to a dedicated uninterruptible power supply.

Servers qualified for use as Cisco Unity servers are configured for a specific hardware setup. Do not add or change any hardware on the server, except to add voice cards, memory, a tape drive, an external modem, or a rail kit.

To Set Up the Server

Step 1 Place the server in a dry, cool area that is free of dust. If you are connecting the server to the network, place it near a network connection. If you are integrating Cisco Unity with a circuit-switched phone system, place the server near the phone system.

Step 2 Attach peripheral devices to the server.

Caution Do not attach the network cable to the server until you have installed Windows 2000 Server Service Pack 3. The Cisco Unity Installation Guide alerts you when to do the procedure later in the installation.

If you are setting up a Cisco MCS-7825 server (Compaq DL-320) and connecting it to the network, use only the bottom RJ-45 Ethernet receptacle.

Step 3 Attach the system key, if applicable:

Parallel key

Attach to the server. (To connect a printer to the server, plug the printer into the parallel port on the key.)

USB key, server purchased from Cisco

Attach to the server in any USB port.

USB key, server not purchased from Cisco

Wait to attach the key until after you have installed the USB key driver. The Cisco Unity Installation Guide alerts you when to do the procedure later in the installation.

If you are setting up failover and do not know which system key goes with which server, attach a key to each server, if applicable. After Cisco Unity is installed, you can determine the correct key-and-server combination when you are ready to configure the servers for failover. The Cisco Unity Failover Configuration and Administration Guide alerts you when to do the procedure later in the installation.

Step 4 If you are integrating Cisco Unity with a circuit-switched phone system, connect the phone system to the server as described in the Cisco Unity integration guide for your phone system.

Step 5 If you are installing the Cisco Unity system outside the United States and the server contains voice cards that came with a ferrite clamp, attach the clamp around the analog phone lines as close to the server as possible.

Configuring the RAID Arrays

Do this section only if the system is using hardware-based RAID. (Software-based RAID is not supported.)

To configure the arrays, you group the physical disks into logical disks and assign a RAID type to each logical disk.

The procedure you use to configure the arrays depends on whether the Cisco Unity server was purchased from Cisco:

Cisco-Provided Array-Configuration Utility

A Cisco Unity server purchased from Cisco ships with Platform Configuration discs that contain a utility for automatically configuring the arrays. Do one of the following two procedures, depending on the platform (Hewlett-Packard or IBM).

Hewlett-Packard: To Configure the RAID Arrays by Using the Cisco-Provided Utility

Step 1 Start the Cisco Unity server, and insert the applicable disc in the CD-ROM drive, depending on the Windows 2000 edition:

Windows 2000 Server

Cisco Unity Platform and RAID Configuration Disc (HP) CD 1

Windows 2000 Advanced Server

Cisco Unity Platform and RAID Configuration Disc—AS (HP) CD 1

Step 2 When the main menu appears, press <F1>.

Step 3 Follow the on-screen prompts. When the utility has completed, the main menu reappears.

Caution Do not press any keys while the BIOS screen is displayed. If you interrupt the utility, you will have to start over.

Step 2 Select the server type. The options may combine the following information:

•Server model.

•Number of physical disks installed in the server.

•Size, in gigabytes, of the largest physical disks.

Step 3 Press Enter.

Step 4 Follow the on-screen prompts.

Manufacturer-Provided Array-Configuration Utility

The server manufacturer provides a disc that contains utilities for several setup tasks, including configuring RAID arrays. Use the disc to configure the arrays when the Cisco Unity server was not purchased from Cisco.

The following discs are provided by server manufacturers:

Dell

Dell Server Assistant

Hewlett-Packard

Hewlett-Packard SmartStart

IBM

IBM ServerGuide

Use the manufacturer-provided array-configuration utility to set up the logical disks now.

The following procedure contains only general steps. For detailed instructions on using a specific array-configuration utility, refer to the manufacturer documentation.

To Configure the RAID Arrays by Using the Manufacturer-Provided Utility

Step 1 Start the Cisco Unity server, and insert the manufacturer disc in the CD-ROM drive.

Step 2 On the main menu, select the array-configuration utility.

Step 3 For each logical disk needed, group physical disks of the same make and model, and assign a RAID type. (Group three physical disks for a RAID 5 volume, and two physical disks for a RAID 1 volume.)

Step 4 Follow the manufacturer instructions to complete the configuration.

Installing Windows 2000 Server or Windows 2000 Advanced Server

Caution Do not install Windows Server 2003 on the Cisco Unity server.

The compact discs you use to install Windows 2000 Server or Windows 2000 Advanced Server depend on whether the Cisco Unity server was purchased from Cisco:

Note All references to Windows 2000 Server in the remainder of the Cisco Unity Installation Guide apply both to Windows 2000 Server and to Windows 2000 Advanced Server.

Installing Windows 2000 Server by using the utility on the Cisco Unity Platform Configuration discs reduces the Cisco Unity system installation time and ensures that the required operating system and components, drivers, and service packs are installed and configured correctly. In addition, the logical drives are automatically set up.

Caution Do not attach the network cable to the server until Windows 2000 Server Service Pack 3 is installed. The Cisco Unity Installation Guide alerts you when to install the service pack and when to connect to the network later in the installation process.

Do one of the following two procedures, depending on the platform (Hewlett-Packard or IBM).

Step 5 Follow the on-screen prompts until you are prompted to select a licensing mode.

Step 6 Click Per Seat, and click Next.

Step 7 Enter a name for the Cisco Unity server (netBIOS name). Use only alphabetical characters from A to Z and a to z, numerical characters from 0 to 9, and hyphen (-).

Caution Using other characters in the server name is not supported by DNS.

If the system is using failover, the server name must be 15 characters or fewer in length. Cisco recommends that you assign a name with 15 or fewer characters regardless of whether the system is using failover.

Step 11 In the Workgroup or Computer Domain dialog box, click No, This Computer Is Not on a Network, or Is on a Network Without a Domain.

If the Workgroup or Computer Domain dialog box is empty, enter a workgroup name. The name you enter now is not important. You will join a domain or make the Cisco Unity server a domain controller in a later procedure, so the Cisco Unity server will no longer be in a workgroup.

Step 1 Start the Cisco Unity server, and insert the applicable disc in the CD-ROM drive, depending on the Windows 2000 edition:

Windows 2000 Server

Cisco Unity Platform Configuration Disc (IBM) CD 1

Windows 2000 Advanced Server

Cisco Unity Platform Configuration Disc —AS (IBM) CD 1

Step 2 When the main menu appears, press Enter to start the installation program.

Step 3 Follow the on-screen prompts until you are prompted to select a licensing mode.

Step 4 Click Per Seat, and click Next.

Step 5 Enter a name for the Cisco Unity server (netBIOS name). Use only alphabetical characters from A to Z and a to z, numerical characters from 0 to 9, and hyphen (-).

Caution Using other characters in the server name is not supported by DNS.

If the system is using failover, the server name must be 15 characters or fewer in length. Cisco recommends that you assign a name with 15 or fewer characters regardless of whether the system is using failover.

Step 9 In the Workgroup or Computer Domain dialog box, click No, This Computer Is Not on a Network, or Is on a Network Without a Domain.

If the Workgroup or Computer Domain box is empty, enter a workgroup name. The name you enter now is not important. You will join a domain or make the Cisco Unity server a domain controller in a later procedure, so the Cisco Unity server will no longer be in a workgroup.

The server manufacturer provides a disc that contains utilities for several setup tasks, including guiding the installation of Windows 2000 Server or Windows 2000 Advanced Server from a retail disc. Use the manufacturer disc when the Cisco Unity server was not purchased from Cisco.

The following discs are provided by server manufacturers:

Dell

Dell Server Assistant

Hewlett-Packard

Hewlett-Packard SmartStart

IBM

IBM ServerGuide

Installing Windows 2000 Server or Windows 2000 Advanced Server by using the manufacturer's guided system-setup utility ensures that the operating system and the drivers are installed and configured correctly.

Note All references to Windows 2000 Server in the remainder of the Cisco Unity Installation Guide apply both to Windows 2000 Server and to Windows 2000 Advanced Server.

Caution Do not attach the network cable to the server until Windows 2000 Server Service Pack 3 is installed. The Cisco Unity Installation Guide alerts you when to install the service pack and when to connect to the network later in the installation process.

To Install Windows 2000 Server By Using the Manufacturer's Guided System-Setup Utility and a Retail Windows 2000 Server Disc

Step 1 Start the Cisco Unity server, and insert the manufacturer disc in the CD-ROM drive.

•If the arrays have already been configured, do not change the configuration.

•If the arrays have not been configured, follow the prompts to configure them. Refer to the manufacturer documentation.

Step 3 When applicable, make the following choices:

•Specify a partition size of 8 GB for the operating system.

•If you are installing Windows 2000 Server on the same partition where an operating system is already installed, select and delete that partition.

•Format the operating system partition by using the NTFS file system.

•For regional settings, select a locale in the Your Locale (Location) list. The locale you select must match one of the languages that you will install for Cisco Unity, which are listed below. Note that the Cisco Unity installation always installs English (United States).

–Chinese (People's Republic of China) (Check the Simplified Chinese check box in the Language Settings for the System list.)

–Chinese (Taiwan) (Check the Traditional Chinese check box in the Language Settings for the System list.)

–Danish

–Dutch (Netherlands)

–English (Australia)

–English (New Zealand)

–English (United Kingdom)

–English (United States)

–French (France)

–German (Germany)

–Italian (Italy)

–Japanese (Check the Japanese check box in the Language Settings for the System list.)

–Korean

–Norwegian (Bokmal)

–Portuguese (Brazil)

–Spanish (Colombia)

–Spanish (Spain)

–Swedish

Caution If the locale you specify when you install Windows 2000 Server does not match any of the installed Cisco Unity languages, Cisco Unity will log errors in the event log and may stop taking calls. The locale you select here must match the Cisco Unity language exactly. For example, if you choose English (United Kingdom) for locale, you must also choose English (United Kingdom) as one of the Cisco Unity languages. English (Australia) will not work.

•Specify Per Seat for the licensing mode.

•When you enter a name for the Cisco Unity server (netBIOS name), use only alphabetical characters from A to Z and a to z, numerical characters from 0 to 9, and hyphen (-).

Caution Using other characters in the server name is not supported by DNS.

If the system is using failover, the server name must be 15 characters or fewer in length. Cisco recommends that you assign a name with 15 or fewer characters regardless of whether the system is using failover.

•Do not join a domain. Instead, specify a workgroup. The Cisco Unity Installation Guide alerts you when to connect to the network and when to join a domain later in the installation.

•If you are prompted to specify Windows 2000 Server components to install, select the following required components:

–Internet Information Server

–Message Queuing Services

–Terminal Services

•If you are prompted to specify a Windows 2000 Server service pack to install, specify Windows 2000 Server Service Pack 3.

Step 5 Uncheck the Show This Screen at Startup check box, and close the window.

Setting Up the Logical Drives (If the Cisco Unity Server Was Not Purchased from Cisco)

Note If the Cisco Unity server was purchased from Cisco, skip this section. When you installed Windows 2000 with the Cisco Unity Platform Configuration discs shipped with the server, the logical drives were automatically set up.

Step 4 Right-click the first available unallocated region of the first available logical disk, and click Create Partition.

Typically, you will need to create one more logical drive than the number of logical disks available. After you install the operating system, the first 8 GB of the first logical disk is used for the system partition and is given the drive letter C. You create the first extended partition by using the remaining space on the first logical disk. When you create subsequent partitions, you use the entire logical disk. If you need the same number of logical drives as the number of logical disks available, use an entire logical disk for each partition you create.

Step 9 In the Disk Management utility, right-click the new partition, and click Create Logical Drive.

Step 10 On the Create Partition wizard Welcome screen, click Next.

Step 11 Click Logical Drive,and click Next.

Step 12 Specify to use the maximum disk space, and click Next.

Step 13 Assign a drive letter, and click Next.

Step 14 Specify to use the NTFS file system format, and click Next.

Step 15 Verify the settings, and click Finish.

Step 16 Repeat Steps 4 through 15 for each for each logical drive you have to create.

Installing Windows 2000 Server Service Pack 3 (Selected Systems)

If the Cisco Unity server was purchased from Cisco and if you installed Windows 2000 Server by using the Platform Configuration discs, revision 11 or later, Windows 2000 Server Service Pack 3 is already installed. Skip this procedure.

Disabling the Found New Hardware Wizard for the Voice Cards (If Applicable)

If the Cisco Unity server contains voice cards, in the following cases, the Found New Hardware wizard may appear each time you restart the Cisco Unity server and report that the voice cards are new hardware, even though the cards are properly installed and configured:

•The operating system was installed by using the Platform Configuration discs.

•The operating system was installed by using the manufacturer's guided system-setup utility before the voice cards were installed.

Do the following procedure to prevent the Found New Hardware wizard from reporting the voice cards as new hardware. The procedure will not prevent the Found New Hardware wizard from finding and reporting other new hardware.

Connecting the Cisco Unity Server to the Network

To Connect the Cisco Unity Server to the Network

Attach the network cable(s) to the Cisco Unity server.

Configuring Dual NICs in the Cisco Unity Server

If the Cisco Unity server contains dual NICs, Cisco recommends that they be configured in adapter fault tolerant mode (AFT) or network fault tolerant (NFT) mode. One NIC is designated as the primary and the other NIC as the secondary for active-passive fault tolerance. In this configuration, the primary (active) NIC handles 100 percent of the traffic. Only in the event that the primary NIC becomes unavailable does the secondary NIC then become active and handle 100 percent of the traffic.

Alternatively, if you do not want to configure AFT or NFT, or do not have a second LAN port available, the following configurations are supported, though not recommended:

•Disable TCP/IP for the second NIC, which allows you to re-enable the second NIC remotely if the first NIC fails. (Use the Network and Dial-up Connections Control Panel to disable TCP/IP for the second NIC.)

•Disable the second NIC in the BIOS.

Caution Note that not plugging a network cable into the second NIC is not sufficient. The NIC must be disabled in the BIOS, or Cisco Unity may not work properly.

To Configure Dual NICs in the Cisco Unity Server

Step 1 Configure the NICs—or verify their configuration—so that:

•Both are connected to the same network segment.

•Both share the same IP address.

•Both are set up for AFT when using a Dell or IBM server, or for NFT when using a Hewlett-Packard server. (Refer to the documentation provided by the NIC manufacturer or server vendor.)

Step 2 Restart the Cisco Unity server for any changes to take effect.

Assigning a Static IP Address or Reserving an IP Address in DHCP

The Cisco Unity server must have an IP address. If you installed the operating system by using the Platform Configuration discs that are shipped with a Cisco Unity server purchased from Cisco and you connected the server to a network that has a Dynamic Host Configuration Protocol (DHCP) server, the Cisco Unity server is configured to automatically obtain an IP address from the DHCP server. Cisco strongly recommends that you change this configuration in one of the following ways:

If the device sends a reply, the Cisco Unity server has a valid IP address.

If the device does not reply, there may be a variety of causes. Some of the most common problems include:

•The assigned static IP address or the address reserved in DHCP conflicts with the IP address of another computer on the network.

•For a static IP address, the subnet mask is incorrect.

•The Cisco Unity server has a problem contacting the DHCP server.

Verify the network settings. If needed, troubleshoot any problem as you would a network connectivity problem.

Installing the USB Key Driver and Attaching the USB System Key (Selected Systems)

Do this section if the system key is a USB key and the Cisco Unity server was not purchased from Cisco. (The driver is installed automatically when you install Windows and other software by using the Platform Configuration discs that are shipped with Cisco Unity servers purchased from Cisco.)

Step 5 When the installation program finishes, attach the USB system key to any USB port on the Cisco Unity server.

If you are setting up failover, attach the USB keys to the primary and secondary servers. If you do not know which system key goes with which server, attach a key to each server. After Cisco Unity is installed, you can determine the correct key-and-server combination when you are ready to configure the servers for failover. The Cisco Unity Failover Configuration and Administration Guide alerts you when to do the procedure later in the installation.

Do the following procedure only if you installed Windows 2000 Server with the USB key already attached.

To Remove the Default USB Driver If You Installed Windows 2000 Server with the USB key Already Attached

Installing Active Directory or Adding the Cisco Unity Server to an Existing Domain

The Cisco Unity server must be either a member server in an existing domain or a domain controller. Cisco Unity's interactions with Exchange do not allow the server to be in a workgroup.

This section contains procedures for installing Active Directory and adding the Cisco Unity server as a member server in an existing domain. Do the procedure that is applicable to your installation. Exchange does not support workgroups, so you must do one procedure or the other.

If you are setting up failover, add both the primary and the secondary Cisco Unity servers to the same existing domain. Do not install Active Directory on either server.

Caution If the Cisco Unity server will be the only server in the domain, you must install Active Directory. However, because Active Directory is a very processor- and memory-intensive application, if you are adding the Cisco Unity server to an existing domain, Cisco strongly recommends that you do not also install Active Directory on the Cisco Unity server. Instead, do the procedure in the "Existing Domain" section.

Active Directory

Do the following procedure to install Active Directory on the Cisco Unity server.

Step 4 In the Identification Changes dialog box, click Domain, and enter the name of the domain that you want to join.

If you are setting up failover, add both servers to the same domain.

Step 5 Click OK.

Step 6 In the Domain Username and Password dialog box, enter the name and password of an account that has permission to add computers to the domain.

Step 7 Click OK three times.

Step 8 Click Yes to restart the server.

Installing SQL Server 2000 or MSDE 2000

This section contains procedures for installing SQL Server 2000 and MSDE 2000 on the Cisco Unity server. Do the procedures in the order listed for the version that is applicable to your installation.

If you are not setting up failover, the number of voice ports that you are connecting with the Cisco Unity server determines whether you install SQL Server 2000 or MSDE 2000:

SQL Server 2000

For systems with more than 32 ports.

MSDE 2000

For systems with 32 ports or fewer.

If you are not setting up failover, do not install SQL Server 2000 on a system with 32 ports or fewer; such a system is licensed only for MSDE 2000.

If you are setting up failover, always install SQL Server 2000 on both servers, regardless of the number of voice ports that you are connecting with the Cisco Unity server.

If you are upgrading a Cisco Unity 3.0 system to version 3.1, and the system has 17 to 32 ports, you do not need to downgrade from SQL Server 2000 to MSDE 2000 because the system was originally licensed for SQL Server 2000.

Whether you are installing SQL Server 2000 or MSDE 2000, the software must be installed on the Cisco Unity server. Installing it on another server is not supported.

If you click Mixed Mode (which is supported, but is less secure), under Add Password for the SA Login, enter and confirm a password for the SQL Server system administrator logon.

Step 20 Click Next.

Step 21 In the Start Copying Files dialog box, click Next.

Step 22 In the Choose Licensing Mode dialog box, click Processor License For, and specify the number of processors in the Cisco Unity server.

Step 23 Click Continue.

Step 24 If you are prompted about shutdown tasks before continuing with the installation, click Next.

Step 25 Click Finish.

Step 26 Restart the server.

After Cisco Unity 3.1(5) was released, SQL Server 2000 Service Pack 3 was made a requirement for all 3.1(x) releases because of the Slammer worm, but the requirement was not enforced by the Cisco Unity Setup program. Beginning with Cisco Unity 3.1(6), the requirement is enforced.

To Install SQL Server 2000 Service Pack 3

Step 1 Insert Cisco Unity Service Packs CD 2 in the CD-ROM drive.

Step 2 Browse to the directory SQL2000_SP3\x86\Setup, and double-click Setupsql.exe.

Step 3 Follow the on-screen prompts to install the service pack. Do not check the Enable Cross-Database Ownership Chaining For All Databases (Not Recommended) check box.

Step 4 When the installation is finished, shut down and restart the Cisco Unity server.

MSDE 2000

Do the following three procedures in the order listed.

Caution MSDE 2000 is not the same as SQL Server 2000 Personal Edition. Do not install Personal Edition.

Caution If you are setting up failover, do not install MSDE 2000 on either Cisco Unity server. Instead, install SQL Server 2000. See the "SQL Server 2000" section.

After Cisco Unity 3.1(5) was released, MSDE 2000 Service Pack 3 was made a requirement for all 3.1(x) releases because of the Slammer worm, but the requirement was not enforced by the Cisco Unity Setup program. Beginning with Cisco Unity 3.1(6), the requirement is enforced.

This section contains procedures for installing Exchange 2000 Server and Exchange Server 5.5, both of which include administration software, on the Cisco Unity server. Do the procedures for your version of Exchange:

Exchange 2000

Do the following five procedures, if applicable, in the order listed. The procedures apply to the compact discs that are shipped with Cisco Unity. If you are using different discs, the procedures may differ.

Caution If you are setting up failover, do not install Exchange 2000 on either Cisco Unity server.

To Run Forestprep (Required Only If the Cisco Unity Server Is the First Exchange 2000 Server in the Forest)

Step 4 When you are prompted to enter a product identification number/CD key, enter the key for Cisco Unity Message Store 2000. The key is located on a sticker on the back of the CD sleeve.

Step 5 If a warning appears about this being an insecure domain, click OK.

Step 6 Follow the on-screen prompts.

Step 7 Click Finish.

Changes to the Active Directory schema may take 15 minutes or more to replicate throughout the forest. These changes must finish replicating before you can install Exchange. To determine whether changes have replicated and to force replication if necessary, use Replication Monitor, which is available when Support Tools is installed from the Windows 2000 Server disc. If the Cisco Unity server was purchased from Cisco, the disc is labeled Cisco Unity System Disc.

Exchange Server 5.5

Do the following three procedures, if applicable, in the order listed. The procedures apply to the compact discs that are shipped with Cisco Unity. If you are using different discs, the procedures may differ.

Caution If you are setting up failover, do not install Exchange 5.5 on either Cisco Unity server.

To Install Exchange Server 5.5

Step 1 If you are installing the Cisco Unity system into an existing Exchange site, log on to Windows by using the account that was used to install Exchange on other servers. Otherwise, use an account that has Services Account Administration permissions for the destination site and configuration containers.

If the disc does not run automatically, browse to the root directory, and double-click Launch.exe.

Step 4 Click Microsoft Exchange Server 5.5.

Step 5 Accept the license agreement.

Step 6 Click Complete/Custom.

Step 7 Uncheck the Outlook Web Access check box.

Optionally, you can save disk space by choosing not to install the MS Mail and/or cc:Mail connectors, if the site does not require them. In the list, click Microsoft Exchange Server, then click Change Option. Uncheck the MS Mail Connector or cc:Mail Connector check box. Then click OK.

Step 8 Click Continue.

Step 9 When you are prompted to enter a CD key, enter the key for Cisco Unity Message Store 5.5. The key is located on a sticker on the back of the CD sleeve.

Step 10 Click OK.

Step 11 Follow the on-screen prompts until you are prompted to choose between joining an existing site and creating a new site:

Join an existing site

When there is an existing Exchange site and you want to add the Cisco Unity server to that site.

Create a new site

When the Cisco Unity server is the only Exchange server.

or

When there are other Exchange servers, but you are installing the Cisco Unity system in the Voice Messaging Only configuration.

Step 12 Follow the on-screen prompts until you are prompted to run the optimizer.

Step 13 Click Run Optimizer. Note that the Exchange Optimizer may automatically move files to different hard disks unless you specify otherwise.

Caution If you installed Exchange 5.5 and Active Directory on the same server, you must change the LDAP port number. Otherwise, changing the LDAP port number is optional.

Step 2 In the site container, open the Configuration container.

Step 3 Under Configuration, click Protocols.

Step 4 In the right pane, double-click LDAP (Directory) Site Defaults.

Step 5 On the General tab, change Port Number to 379 (or another available port number).

Step 6 Click OK, and close the Exchange Administrator.

Microsoft recommends that all Exchange 5.5 servers on the network have the same service pack installed. Install Exchange 5.5 Service Pack 4 on the Cisco Unity server and on the other Exchange 5.5 servers in the site.

Step 3 In the Server Browser dialog box, click the name of the Cisco Unity server, and click OK.

Step 4 In the Connect to Server dialog box, click Set as Default, and click OK.

Step 5 If you changed the LDAP port number, restart the server.

Installing Only Exchange Administration Software on the Cisco Unity Server

Do this section if you are not installing Exchange 2000 or Exchange 5.5 on the Cisco Unity server. Note that Cisco assumes that the Exchange environment is already set up and working before the Cisco Unity system is installed.

Later in the installation, you specify an Exchange server on the network for the Cisco Unity server to connect with.

Step 8 When you are prompted to enter a CD key, enter the key for Cisco Unity Message Store 5.5. The key is located on a sticker on the back of the CD sleeve.

Step 9 Click OK.

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

Microsoft recommends that all Exchange 5.5 servers on the network have the same service pack installed. Install Exchange 5.5 Service Pack 4 on the Cisco Unity server and on the other Exchange 5.5 servers in the site.

With Exchange 2000, several changes need to be made to the Active Directory schema for Cisco Unity to work properly. To see the changes that the schema update program makes, browse to the directory Schema\LdifScripts on Cisco Unity CD 1, and view the file Avdirmonex2k.ldf.

Additional changes to the schema are required if you are setting up a Cisco Unity Bridge. To see the changes that the schema update program makes for the Bridge, view the file Omnigateway.ldf.

To update the schema, use either the following procedure or any tool that applies LDIF scripts (for example, the Microsoft Ldifde utility).

If you are setting up failover, you need to update the schema only once. (Both servers must be member servers in the same domain, so they use the same Active Directory schema.)

To Extend the Active Directory Schema

Step 1 Confirm that all domain controllers are online before making the schema updates. Schema replication will occur only if all domain controllers are online.

Step 2 On the domain controller that is the schema master, log on by using an account that is a member of the Schema Administrators group.

Step 3 Insert Cisco Unity CD 1 in the CD-ROM drive.

Step 4 Browse to the ADSchemaSetup directory.

Step 5 Double-click ADSchemaSetup.exe, and then double-click the dialog box that is displayed to proceed with the installation.

Step 9 When the schema extension has finished, Ldif.log and LDif.err files are saved to the desktop. View the contents of the files to confirm that the extension completed successfully.

Step 10 Wait for the changes to the schema to replicate throughout the forest before adding information to the primary location and to delivery locations. Changes to the schema may take 15 minutes or more to replicate.

Note To determine whether changes have replicated and to force replication if necessary, use the Replication Monitor, which is available when you install Support Tools from the Windows 2000 Server disc. If the Cisco Unity server was purchased from Cisco, the disc is labeled Cisco Unity System Disc.

Installing Windows Terminal Services or pcAnywhere (Selected Systems)

You install Windows Terminal Services or pcAnywhere because Cisco TAC may use it to perform troubleshooting.

If the Cisco Unity server was purchased from Cisco and if you installed Windows 2000 Server by using the Platform Configuration discs, revision G or later, Windows Terminal Services is already installed. Skip this section unless you want to use pcAnywhere instead of Windows Terminal Services.

If the Cisco Unity server was not purchased from Cisco or if you have old Platform Configuration discs, either install Windows Terminal Services or install and configure pcAnywhere.

The remote-access software can be installed on the Cisco Unity server in addition to Windows Terminal Services (which is the default remote-access software for the Cisco Unity server and is included with Windows 2000 Server). Use an external modem with pcAnywhere.

Recommended Configuration for pcAnywhere

Cisco recommends that you do the following three procedures to configure pcAnywhere to avoid video problems, screen-refresh problems, and a possible problem with the server not responding after pcAnywhere disconnects.

To Configure pcAnywhere So That It Does Not Start Automatically When You Restart the Server

To avoid a pcAnywhere problem with slow or partial screen refreshes on multiprocessor host computers, and a possible problem in which the host computer stops responding when pcAnywhere disconnects, Cisco recommends that you add a registry entry that sets pcAnywhere to run on one or more specific processors. (The problem is described in Symantec Knowledge Base article 199861984643.)

Be aware that setting pcAnywhere to run on a specific processor may affect performance on the Cisco Unity server if someone uses pcAnywhere to access the server during peak hours.

To Set pcAnywhere to Run on One or More Specific Processors

Step 1 Start Regedit.

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. (Refer to the "Restoring" topics in Registry Editor Help.) Note that for Cisco Unity failover, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated. If you have any questions about changing registry key settings, contact Cisco TAC.

Step 2 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 4 Add a DWORD value named ProcessorMask, and set the value depending on which processor you want to use (for example, to make pcAnywhere run on the second processor only, set ProcessorMask to 2):

0

All processors

1

First processor

2

Second processor

4

Third processor

8

Fourth processor

To allow pcAnywhere to run on more than one processor, set the value of ProcessorMask to the sum of the corresponding values. (For example, to make pcAnywhere run on the third and fourth processors, set ProcessorMask to 12 [4 + 8].)

Step 5 Either stop and restart the pcAnywhere host service or restart the Cisco Unity server.

Installing Virus-Scanning Software and Excluding from Scanning the Directory in Which Cisco Unity Is Installed

Note that scanning individual Exchange mailboxes can affect the performance of Cisco Unity.

Caution Do not configure virus-scanning software to block WAV attachments, or voice messages will be stripped of their recordings.

Step 2 Exclude from virus scanning the directory in which Cisco Unity is installed (the default directory is CommServer). Refer to Help for the virus-scanning software for information on excluding directories from scanning.

Installing and Configuring Cisco Security Agent

At the time this book was published, Cisco Security Agent had not been qualified for use with Cisco Unity, but we are planning to support it. For updated information on whether Cisco Security Agent is supported, and on how to install and configure it, refer to the section "New and Changed Support—Release 3.1(6)" in Release Notes for Cisco Unity Release 3.1(6), available on Cisco.com at http://www.cisco.com/en/US/partner/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Step 2 If virus-scanning software is installed on the Cisco Unity server, exclude from scanning the directory in which the Cisco IDS Host Sensor Agent is installed, so that Cisco IDS Host Sensor will work properly.

To Configure Cisco IDS Host Sensor

Step 1 On the Cisco IDS Host Sensor console server, create an agent group named Unity, and add the Cisco Unity server to the Unity agent group.

Step 2 On the console server, create a policy named Unity.

Step 3 Add the Unity agent group to the Unity policy.

Step 4 For High and Medium events, in the Reaction list, click Prevent.

Step 5 For Low and Info events, in the Reaction list, click Log.

Step 6 On the console server, for the Unity agent group, change the security levels to Low for the following 11 signatures:

•IIS Directory Traversal

•IIS Envelope—File Access by IIS Process

•IIS Envelope—File Access by IIS Web User

•IIS Envelope—File Modification by IIS Process

•IIS Envelope—Registry Access by IIS Process

•IIS Envelope—File Execution by IIS Process

•IIS Shielding—Configuration File Activity

•IIS Shielding—File Execution

•IIS Shielding—Registry Access

•IIS Shielding—Service Access

•IIS Shielding—SSI File Extension Request

Caution If you do not change the signatures, the Cisco Unity Administrator, Cisco Personal Communications Assistant (PCA), ActiveAssistant, Cisco Unity Visual Messaging Interface, and Status Monitor will not function correctly. In addition, Event Viewer event properties will be inaccessible.

Step 7 By default, an agent will operate in On-Warning mode after installation. We recommend that you run the agent in On-Warning mode for one week after installation, and then adjust other security levels as appropriate. Do not change the security levels that you set to Low in Step 6.

VERITAS Backup Exec

Follow the manufacturer instructions to install VERITAS Backup Exec.

Changing Windows Explorer Settings (Selected Systems)

If the Cisco Unity server was not purchased from Cisco, do the following procedure to ensure that all system files and folders are visible in Windows Explorer during troubleshooting. (Windows Explorer settings are automatically configured if Windows was installed by using the Platform Configuration discs that are shipped with Cisco Unity servers purchased from Cisco.)

With Exchange 2000, users and distribution lists are created in a location that you specify. If you want users and distribution lists to be created in custom organizational units (OUs), create the OUs now. Both OUs need to be in the same domain, but they do not need to be in the same domain as the Cisco Unity server. For information on creating OUs, refer to Active Directory Users and Computers Help.

You also have the option to create a custom mailbox store as the default for subscribers that are added through the Cisco Unity Administrator or that are imported from a CSV file. For information on creating a custom mailbox store, refer to Exchange System Manager Help. (You configure Cisco Unity to use the mailbox store during the Cisco Unity Setup program.)

If you are setting up failover, you must use the same custom OUs and mailbox stores for both Cisco Unity servers.

About the Accounts Required for the Cisco Unity Installation

This section describes the following domain accounts that are needed for the Cisco Unity installation:

The Account Used to Install Cisco Unity

During installation, Cisco Unity creates a number of Cisco Unity objects in Active Directory and in Exchange, so the account with which you log on to Windows to install Cisco Unity must have proper user rights and permissions to perform the necessary operations.

If you are installing more than one Cisco Unity server in a site (including setting up failover), you can use the same account to install Cisco Unity software on all of the servers.

The Account Used to Access the Cisco Unity Administrator

When you install Cisco Unity, you are prompted to choose the Windows domain account that you want to use to access the Cisco Unity Administrator (the website used to perform most administration tasks). During installation, the domain account is automatically associated with a Cisco Unity subscriber whose class of service allows Cisco Unity Administrator access. (Later you can create additional Cisco Unity subscribers who also can access the Cisco Unity Administrator.)

By default, the Cisco Unity administration account is the installation account. If you prefer to use an account other than the installation account to be the first Cisco Unity administration account, create an additional domain account for that purpose.

When the Cisco Unity server is a domain controller, the Cisco Unity administration account must be a member of the Domain Admins group. When the Cisco Unity server is a member server, the Cisco Unity administration account must be a member of the Local Admins group. Procedures later in this chapter explain how to add the account to the applicable group.

The Accounts That Cisco Unity Services Log On As

During Cisco Unity installation, you are prompted to choose one or two domain accounts that Cisco Unity directory and message store services log on as, depending on which version of Exchange you are using:

•For Exchange 2000, you use separate accounts that directory services and message store services log on as, because the permissions required by each services type conflict with the permissions required by the other.

Some procedures in this section assume that you have access to Active Directory Users and Computers because you installed Exchange 2000 or the Exchange 2000 administration software on the Cisco Unity server, or because the Cisco Unity server is a domain controller.

To create the accounts and set their permissions when Active Directory Users and Computers is not installed on the Cisco Unity server, do one of the following:

To Create Accounts for a System That Includes Exchange 2000 and Exchange 5.5 Servers

Step 1 Using Exchange 5.5 Administrator, create a mailbox in the Exchange 5.5 directory for the message store services account. You do not need to associate the mailbox with a Windows NT account or an Active Directory account.

Cisco suggests that you use the name UnityMsgStoreSvc. Do not use the following names:

•Unity_<servername>

•Unity Messaging System - <servername>

If there is more than one Cisco Unity server in the Exchange site, create one Exchange 5.5 mailbox for each Cisco Unity server. If you are setting up one or more failover systems, create one mailbox for each pair of failover servers.

The Active Directory Connector replicates the mailbox to Active Directory as a disabled account.

Step 2 After the mailbox replicates to Active Directory, enable the account in Active Directory Users and Computers, change the password, and move it to the Exchange 2000 server to which you want to connect Cisco Unity.

Ensure that the password for the account will never expire. If the password expires, Cisco Unity will stop working the next time the server is restarted.

Ensure that for the account that Cisco Unity directory services log on as, the password will never expire. If the password expires, Cisco Unity will stop working the next time the server is restarted.

Step 18 Close Active Directory Users and Computers.

Step 19 Restart the server.

Adding the Cisco Unity Administration Account to an Admins Group

If you created a Cisco Unity administration account in the "Creating the Accounts" section, you must add the account either to the local Administrators group—when the Cisco Unity server is a member server—or to the Domain Admins group—when the Cisco Unity server is a domain controller.

This section contains two procedures. Do the procedure that is applicable to your installation.

To Add the Cisco Unity Administration Account to the Local Administrators Group (Only When the Cisco Unity Server is a Member Server)

Caution The following procedure grants each account the rights to act as a part of the operating system, to log on as a service, and to log on as a batch job, and does so in the local security policy. If a domain security policy is in effect, confirm that the domain security policy does not deny the accounts these rights.

To Run the Cisco Unity Permissions Wizard With an Exchange 2000 Message Store

Step 1 Log on to the Cisco Unity server by using an account that:

•Is a member of the Domain Admins group in the domain in which the Cisco Unity server is being installed.

•Is either an Exchange Full Administrator or a member of the Domain Admins group in the domain that contains all of the domains from which you want to import Cisco Unity subscribers.

•Has the right to act as part of the operating system. A member of the Domain Admins group does not, by default, have this right.

Caution If you try to run the Permissions wizard by using an account that has less than the default permissions for a Domain Admin, the wizard may not be able to set all of the permissions required by the installation account and the services accounts. If the Permissions wizard cannot set all of the required permissions, either the Cisco Unity installation will fail or Cisco Unity will not run properly after it has been installed.

Step 2 Insert Cisco Unity CD 1 in the CD-ROM drive.

Step 3 Browse to the Utilities\PermissionsWizard directory, and run PermissionsWizard.exe.

•The organizational unit in which you want users to be created. This is where Cisco Unity example users will be created during Cisco Unity installation.

•The organizational unit in which you want groups to be created.

Step 13 Click Next.

Step 14 Choose the organizational unit where you want Cisco Unity location objects to be created.

Step 15 Click Next.

Step 16 If you do not want to use the Cisco Unity Administrator to create new Active Directory users, contacts, and groups, you may choose to not grant the Cisco Unity directory services account the necessary rights to create each type of Active Directory object.

If you uncheck a check box next to an Active Directory object type, you will not be able to create the associated type of Cisco Unity object by using the Cisco Unity Administrator. You may only import existing objects into Cisco Unity. (For example, if you uncheck the Users check box, you will not be able to create new Cisco Unity subscribers by using the Cisco Unity Administrator. You will only be able to import existing Active Directory users to make them Cisco Unity subscribers.)

Step 17 Click Next.

Step 18 Choose the Active Directory containers from which you want to import users, contacts, and groups to make them Cisco Unity subscribers, contacts, and public distribution lists. Note the following:

•You must choose a container for the domain that includes the Cisco Unity server.

•Choose only one container for each domain. If you will want to import users, contacts, and groups from more than one container in a domain, choose a common parent container that includes all of the containers from which you want to import. If the common parent is the domain itself, choose the domain.

Step 19 Click Next.

Step 20 If you are using the Cisco Unity Bridge to allow Cisco Unity to exchange voice messages with other voice messaging systems that support Avaya Octel analog networking, check the Cisco Unity Will Use Cisco Unity Bridge check box.

Step 21 If you are using the Cisco Unity Bridge, choose the Active Directory organizational unit in which you want Bridge contacts to be created.

Step 22 Click Next.

Step 23 A summary appears that lists the permissions that will be granted to each account. The information listed includes user rights, Active Directory rights, and membership in groups.

Click Next to grant the listed permissions. The Permissions wizard may take a few minutes to grant permissions.

Step 24 If the Permissions wizard failed to grant one or more permissions, an error message appears that lists the number of permissions it was not able to grant. Click OK.

Step 25 To display a report listing the operations that succeeded and those that failed, if any, click View Detailed Results.

In some cases, individual rights may be combined into a single entry. For example, the rights to read properties, write properties, list contents, read permissions, and modify permissions applied onto Group objects are all included in the single entry "SUCCEEDED granting Group read/modify rights."

Step 26 If one or more permissions could not be granted, fix the problems, and run the Permissions wizard again.

Caution If the Permissions wizard failed to set any permissions, either the Cisco Unity installation will fail or Cisco Unity will not run properly after it has been installed. You must successfully run the Permissions wizard before you can continue installing Cisco Unity.

Caution An Active Directory right being granted by the Permissions wizard may conflict with an existing right on an Active Directory container. (For example, an account may be denied the right to create user objects in one of the containers selected during the Permissions wizard.) The log file will explain that a conflict has been found, but the Permissions wizard will not resolve the conflict. You must resolve the conflict and then rerun the Permissions wizard.

Step 27 Click Finish.

Step 28 If the account that you logged on with in Step 1 is also the account that you want to use to install Cisco Unity (the account that you selected in Step 6), log off of Windows and log back on so the permissions set by the Permissions wizard will take effect.

Caution The following procedure grants each account the rights to act as a part of the operating system, to log on as a service, and to log on as a batch job, and does so in the local security policy. If a domain security policy is in effect, confirm that the domain security policy does not deny the accounts these rights.

To Run the Cisco Unity Permissions Wizard With an Exchange 5.5 Message Store

Step 1 Log on to the Cisco Unity server by using an account that is a member of the Domain Admins group and that has the right to act as part of the operating system. A member of the Domain Admins group does not, by default, have the right to act as part of the operating system.

Caution If you try to run the Permissions wizard by using an account that has less than the default permissions for a Domain Admin, the wizard may not be able to set all of the permissions required by the installation account and the services accounts. If the Permissions wizard cannot set all of the required permissions, either the Cisco Unity installation will fail or Cisco Unity will not run properly after it has been installed.

Step 2 Insert Cisco Unity CD 1 in the CD-ROM drive.

Step 3 Browse to the Utilities\PermissionsWizard directory, and run PermissionsWizard.exe.

Step 6 Click Change, and choose the account that you want to use to install Cisco Unity.

Step 7 Click Next.

Step 8 Click Change, and choose the account that you want Cisco Unity directory and message store services to log on as.

Step 9 Click Next.

Step 10 A summary appears that lists the permissions that will be granted to each account, including user rights and membership in groups.

Click Next to grant the listed permissions. The Permissions wizard may take a few minutes to grant permissions.

Step 11 If the Permissions wizard failed to grant one or more permissions, an error message appears that lists the number of permissions it was not able to grant. Click OK.

Step 12 To display a report listing the operations that succeeded and those that failed, if any, click View Detailed Results.

Step 13 If one or more permissions could not be granted, fix the problems, and run the Permissions wizard again.

Caution If the Permissions wizard failed to set any permissions, either the Cisco Unity installation will fail or Cisco Unity will not run properly after it has been installed. You must successfully run the Permissions wizard before you can continue installing Cisco Unity.

Step 14 Click Finish.

Step 15 If the account that you logged on with in Step 1 is also the account that you want to use to install Cisco Unity (the account that you selected in Step 6), log off of Windows and log back on so the permissions set by the Permissions wizard will take effect.

Setting Exchange Permissions

In general, the Cisco Unity Permissions wizard does not set Exchange permissions, so they must be set manually. (If you are using Exchange 2000, with or without Exchange 5.5, the Permissions wizard does add the message store services account to the Exchange Domain Servers group.)

The Exchange permissions that you set for the Cisco Unity installation and services accounts depend on whether Cisco Unity subscribers are homed on Exchange 2000, Exchange 5.5, or both. See Table 2-5 for a list of the permissions that must be set for each configuration.

If the system is using failover, set Exchange permissions only on the primary server.

Table 2-5 Required Exchange Permissions

WhereCisco UnitySubscribersAre Homed

Permissions

Exchange 2000servers only

Installation account: Exchange Full Administrator.

Cisco Unity directory services account: Exchange Full Administrator if you want to create Cisco Unity subscribers by using the Cisco Unity Administrator. Exchange View Only Administrator if you want to create Cisco Unity subscribers only by importing accounts from Active Directory.

Cisco Unity message store services account: Member of the Exchange Domain Servers group (set by the Permissions wizard).

Cisco Unity server: Member of the Exchange Domain Servers group (only if Exchange is not installed on the Cisco Unity server).

Cisco Unity directory services account: Exchange Full Administrator if you want to create Cisco Unity subscribers by using the Cisco Unity Administrator. Exchange View Only Administrator if you want to create Cisco Unity subscribers only by importing accounts from Active Directory.

Exchange Domain Servers group for the Exchange 5.5 site and Configuration container: Services Account Administration.

Cisco Unity message store services account: Member of the Exchange Domain Servers group (set by the Permissions wizard).

Cisco Unity server: Member of the Exchange Domain Servers group.

Setting the Required Exchange Permissions When Subscribers Are Homed Only on Exchange 2000 Servers

This section contains two procedures. Do the first procedure for all installations. Do the second procedure only when Exchange is not installed on the Cisco Unity server.

Do the following procedure for the installation account first, then for the directory services account.

To Grant Exchange Permissions to the Installation and Directory Services Accounts

Do the following procedure only when Exchange is not installed on the Cisco Unity server. You add the Cisco Unity server to the Exchange Domain Servers group in the domain in which the server is being installed to give the server permission to act as an Exchange server. (When Exchange is installed on the Cisco Unity server, the server is already a member of the Exchange Domain Servers group.)

Setting the Required Exchange Permissions When Subscribers Are Homed on Both Exchange 2000 and Exchange 5.5 Servers

When both Exchange 2000 and Exchange 5.5 users will be Cisco Unity subscribers, do the following three procedures in the order listed.

Caution If you want to home Cisco Unity subscribers both in Exchange 2000 and in Exchange 5.5, the Active Directory Connector must be installed, and there must be either a two-way connection agreement, or a one-way connection agreement that replicates data from Exchange 5.5 to Active Directory.

Do the following procedure for the installation account first, then for the directory services account.

To Grant Exchange Permissions to the Installation and Cisco Unity Directory Services Accounts

You add the Cisco Unity server to the Exchange Domain Servers group in the domain in which the server is being installed to give the server permission to act as an Exchange server. (If Exchange is installed on the Cisco Unity server, the server is already a member of the Exchange Domain Servers group.)

Step 4 When all virus-scanning services have been disabled, close the Services MMC.

Disabling Cisco Security Agent

At the time this book was published, Cisco Security Agent had not been qualified for use with Cisco Unity, but Cisco is planning to support it. For updated information on whether Cisco Security Agent is supported and whether you need to disable it before you install Cisco Unity software, refer to the section "New and Changed Support—Release 3.1(6)" in Release Notes for Cisco Unity Release 3.1(6), available on Cisco.com at http://www.cisco.com/en/US/partner/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Setting the IDS Host Sensor Agent to Run in On-Warning Mode

You disable the IDS Host Sensor Agent on the Cisco Unity server by setting it to run in On-Warning mode. If the IDS Host Sensor Agent is running in On-Protecting mode during the installation, the agent will prevent files from being copied to the Cisco Unity server, and the installation will fail.

The Cisco Unity Installation Guide alerts you when to reset the IDS Host Sensor Agent to run in On-Protecting mode later in the installation process.

Step 2 In the left pane of the Console, click Agents. The Agents view appears in the right pane.

Step 3 In the right pane, right-click the name of the IDS Host Sensor Agent on the Cisco Unity server, and click Set to Warning Mode. Note that it may take several minutes for the Current State to match the Requested State.

Installing Cisco Unity Software

There are two parts to installing Cisco Unity: Running the Cisco Unity Setup program and running the Cisco Unity Server Configuration wizard.

Cisco Unity Setup Program

To Run Cisco Unity Setup

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

Note If you have not already done so, disable virus-scanning services on the Cisco Unity server, set the IDS Host Sensor Agent on the Cisco Unity server to run in On-Warning mode, and possibly disable Cisco Security Agent, if applicable. Otherwise, Cisco Unity Setup may take several hours to complete or may not run.

Step 2 Insert Cisco Unity CD 1 in the CD-ROM drive.

Step 3 Browse to the root directory, and double-click Setup.exe.

Step 4 Follow the on-screen prompts until the System Key dialog box appears.

If the Confirm Demonstration License Settings dialog box appears first, one of the following problems has occurred:

•The system key is not fully attached or is not attached at all. Confirm that the key is fully seated.

Click Cancel, click Yes, and click Finish to exit Setup. Then resolve the problem, and rerun Setup.exe. (If you continue the installation without resolving the problem, Cisco Unity will be installed as a demonstration system.)

(When Cisco Unity was registered on Cisco.com, Cisco replied with an e-mail containing an attached file with an activation code for the system key. The instructions in the e-mail directed that the attached file be saved to a disk. For more information, see the "Cisco Unity Activation Code" section.)

Step 7 Browse to drive A, click the file on the disk, then click Open.

Caution If you are upgrading a Cisco Unity 2.x system to version 3.1, install and load the same phone languages on the Cisco Unity 3.1 system that were installed and loaded on the 2.x system. Otherwise, subscribers who are configured to use the missing languages will not be able to hear the system conversation in their language.

If you installed Windows 2000 Server by using the manufacturer's guided system-setup utility and a retail Windows 2000 Server disc, one of the languages you choose here must match the locale you chose when you installed Windows 2000 Server.

Caution If the locale you specified when you installed Windows 2000 Server does not match any of the installed Cisco Unity languages, Cisco Unity will log errors in the event log and may stop taking calls. The language you select here must exactly match the locale you selected when you installed Windows 2000 Server. For example, if you chose English (United Kingdom) for locale, you must also choose English (United Kingdom) as one of the Cisco Unity languages. English (Australia) will not work.

If you installed Windows 2000 Server by using the Platform Configuration discs that are shipped with the Cisco Unity server, the locale is automatically set to English (United States). The Cisco Unity Setup program always installs U.S. English, so you do not need to choose it as one of the languages to install.

Australian English, New Zealand English, and Colombian Spanish are not available as text-to-speech (TTS) languages. To use one of these languages for the phone language, you must also install another language for the TTS language:

English (Australian)

Also install English (United States) for TTS.

English (New Zealand)

Also install English (United States) for TTS.

Spanish (Colombia)

Also install Spanish (Spain) for TTS.

TTS is not available in Norwegian.

Step 16 Follow the on-screen prompts until you are prompted to restart the Cisco Unity server.

Caution If you are upgrading from Cisco Unity version 2.x to 3.1, and if you plan to transfer subscriber information from the existing system to the new, 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.

Step 17 If the server does not contain Intel Dialogic D/120JCT-EURO or D/240PCI-T1 voice cards, check the Yes, I Want to Restart My Computer Now check box, and click Finish.

If the server contains Intel Dialogic D/120JCT-EURO or D/240PCI-T1 voice cards, uncheck the Yes, I Want to Restart My Computer Now check box, and click Finish.

Caution If the Cisco Unity server contains Intel Dialogic D/120JCT-EURO or D/240PCI-T1 voice cards, do not restart the server now or you will not be able to access the Cisco Unity Administrator after Cisco Unity is installed.

Step 18 If the server contains Intel Dialogic D/120JCT-EURO or D/240PCI-T1 voice cards, do the procedure under "Software Settings" for your voice card in Appendix A, "Voice Cards." When you are finished, restart the Cisco Unity server.

Cisco Unity Server Configuration Wizard

This section contains procedures for completing the Cisco Unity installation on an Exchange 2000 system and on an Exchange 5.5 system. Do the procedure for your version of Exchange.

If you are installing the Cisco Unity system in the Unified Messaging in an Existing Exchange Site configuration and the site contains both Exchange 5.5 and Exchange 2000 servers, use the procedure for Exchange 2000.

Exchange 2000

To Run Cisco Unity Server Configuration

Step 1 Start the Cisco Unity server.

Step 2 Confirm that Exchange is running on the server where you want to create new mailboxes. If Exchange is not running, configuring the server will fail.

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

If the Welcome screen does not appear automatically, double-click the Configuration Setup icon on the desktop. If the Configuration Setup icon has been deleted from the desktop, browse to Commserver\ConfigurationSetup, and double-click Setup.exe.

Step 4 On the Welcome screen, click Next.

Step 5 Enter the password for the installation account, and click Next.

Step 6 Click Microsoft Exchange 2000, and click Next.

Step 7 Choose the Exchange server and mail store in which to create new mailboxes.

If you are setting up failover, you must choose the same Exchange server and mail store for both Cisco Unity servers.

For the Unified Messaging in an Existing Exchange Site configuration:

•All voice messages pass through the server you choose here on their way to user mailboxes. Use Microsoft guidelines to choose a server based on its ability to handle the additional traffic.

•If Exchange is configured for active/active clustering, choose either an Exchange server outside the cluster or the virtual server that is running Exchange Message Transfer Agent.

•If Exchange is configured for active/passive clustering, you may choose either a server outside the cluster or the virtual server in the cluster.

Step 8 Click Next.

Step 9 Select the domain in which you want Cisco Unity to create users and distribution lists.

If you are setting up failover, you must choose the same domain for both Cisco Unity servers.

Step 10 If you created custom organizational units for users or distribution lists, click the corresponding Modify button to specify them here.

If you are setting up failover, you must choose the same custom organizational units for both Cisco Unity servers.

Step 11 Click Next.

Step 12 By default, the installation account is automatically associated with the Cisco Unity subscriber named Installer, which has the right to administer Cisco Unity. If you want to use the default, skip to Step 13.

If you created an administration account in the "Creating the Accounts" section, click Modify. In the Select User dialog box, double-click the name of the administration account.

If you do not want to create Cisco Unity subscribers by using the Cisco Unity Administrator, meaning that you will always create subscribers by importing accounts from Active Directory or Exchange 5.5, click Import Accounts Only.

Step 16 Click Next.

Step 17 Select the account that you want Cisco Unity directory services to log on as. You created this account when you did the procedures in the "Creating the Accounts" section.

Step 18 Specify the password for the directory services account, and click Next.

Step 19 Select the account that you want Cisco Unity message store services to log on as. You created this account when you did the procedures in the "Creating the Accounts" section.

Exchange 5.5

Step 2 Confirm that Exchange is running on the server where you want to create new mailboxes. If Exchange is not running, configuring the server will fail.

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

If the Welcome screen does not appear automatically, double-click the Configuration Setup icon on the desktop. If the Configuration Setup icon has been deleted from the desktop, browse to Commserver\ConfigurationSetup, and double-click Setup.exe.

Step 4 On the Welcome screen, click Next.

Step 5 Enter the password for the installation account, and click Next.

Step 6 Click Microsoft Exchange 5.5, and click Next.

Step 7 Choose the Exchange server in which to create new mailboxes.

If you are setting up failover, you must choose the same Exchange server for both Cisco Unity servers.

For the Unified Messaging in an Existing Exchange Site configuration, we recommend that you choose one of the less busy Exchange servers in the site. All voice messages pass through the server you choose here on their way to user mailboxes.

Step 10 By default, the installation account is automatically associated with the Cisco Unity subscriber named Installer, which has the right to administer Cisco Unity. If you want to use the default, skip to Step 13.

If you created an administration account in the "Creating the Accounts" section, click Modify. In the Select User dialog box, double-click the name of the administration account.

If you do not want to create Cisco Unity subscribers by using the Cisco Unity Administrator, meaning that you will always create subscribers by importing accounts from Active Directory or Exchange 5.5, click Import Accounts Only.

Step 14 Click Next.

Step 15 Select the account that you want Cisco Unity directory and message store services to log on as. You created this account when you did the procedures in the "Creating the Accounts" section.

Step 16 Specify the password for the directory and message store services account, and click Next.

Step 17 When Server Configuration is complete, click Finish.

Resetting Security-Monitoring Software After the Installation Programs Have Been Run

Re-enabling Virus-Scanning Services and Excluding Two Directories from Scanning

When you re-enable virus-scanning services, you need to exclude from scanning the directory in which Cisco Unity is installed so that the Cisco Unity Administrator and the ActiveAssistant will work properly. If the Cisco Unity system is using Cisco IDS Host Sensor, you also need to exclude from scanning the directory in which the Cisco IDS Host Sensor Agent is installed, so that Cisco IDS Host Sensor will work properly.

To Re-enable Virus-Scanning Services and Exclude Two Directories from Scanning

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

b. On the General tab in the Startup Type list, click Automatic, and click OK.

c. In the right pane, right-click the service, and click Start.

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

Step 5 Exclude from virus scanning the directory in which Cisco Unity is installed (the default directory is CommServer). Refer to Help for the virus-scanning software for information on excluding directories from scanning.

Step 6 If the Cisco Unity system is using Cisco IDS Host Sensor, exclude from virus scanning the directory in which Cisco IDS Host Sensor Agent is installed.

Re-enabling Cisco Security Agent

At the time this book was published, Cisco Security Agent had not been qualified for use with Cisco Unity, but Cisco is planning to support it. For updated information on whether Cisco Security Agent is supported and whether you need to re-enable it after you install Cisco Unity software, refer to the section "New and Changed Support—Release 3.1(6)" in Release Notes for Cisco Unity Release 3.1(6), available on Cisco.com at http://www.cisco.com/en/US/partner/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Resetting the IDS Host Sensor Agent to Run in On-Protecting Mode

You re-enable the IDS Host Sensor Agent on the Cisco Unity server by setting it to run in On-Protecting mode.

Step 2 In the left pane of the Console, click Agents. The Agents view appears in the right pane.

Step 3 In the right pane, right-click the name of the IDS Host Sensor Agent on the Cisco Unity server, and click Set to Protecting Mode. Note that it may take several minutes for the Current State to match the Requested State.

Moving the Data Store Databases and Transaction Log Files

The Cisco Unity data store includes several databases and their corresponding transaction log files. Because the Cisco Unity and Reports databases and their log files are the fastest-growing data store files, you place them on the system in a way that makes optimum use of system storage capacity.

For more information on moving SQL Server or MSDE databases and transaction logs, refer to Microsoft documentation.

To Move the SQL or MSDE Databases and Transaction Log Files

Step 1 Stop Cisco Unity (right-click the Cisco Unity icon in the system tray, then click Stop Cisco Unity; if the Cisco Unity icon is not available, browse to the CommServer directory and double-click AvCsTrayStatus.exe).

Step 2 On the Windows Start menu, click Run, then run cmd.

Step 3 Start OSQL by entering OSQL -E on the command line.

Caution OSQL commands are case-sensitive. Enter the instructions exactly as they appear in the procedure.

Step 4 Detach the databases from the data store application by entering the following instructions on the command line:

Step 9 In OSQL, verify the change in the file locations by entering the following instructions on the command line:

a. Enter use UnityDb, and press Enter.

b. Enter go, and press Enter.

c. Enter sp_helpfile, and press Enter.

d. Enter go, and press Enter.

e. The file name column values should reflect the new locations.

Step 10 Enter exit, and press Enter to close OSQL.

Step 11 Optional: In Windows Explorer, rename each of the databases and log files in the old locations <Original file name and extension>.old. (For example, in its original location, rename UnityDb.mdf to UnityDb.mdf.old.)

Step 12 Restart Cisco Unity (right-click the Cisco Unity icon in the system tray, then click Start Cisco Unity; if the Cisco Unity icon is not available, browse to the CommServer directory and double-click AvCsTrayStatus.exe).