Reconfiguration and Upgrade Guide for Cisco Unity Release 8.x (With Microsoft Exchange)
Changing the Domain Controller and Global Catalog Server for Cisco Unity 8.x
Downloads: This chapterpdf (PDF - 73.0KB) The complete bookPDF (PDF - 7.03MB) | Feedback

Changing the Domain Controller and Global Catalog Server for Cisco Unity 8.x

Table Of Contents

Changing the Domain Controller and Global Catalog Server for Cisco Unity 8.x

Changing the Domain Controller That Cisco Unity 8.x Monitors

Changing the Global Catalog Server That Cisco Unity 8.x Monitors for Directory Updates

Changing the Global Catalog Server with Which the Cisco Unity 8.x MAPI Client Communicates


Changing the Domain Controller and Global Catalog Server for Cisco Unity 8.x


This chapter contains the following sections:

Changing the Domain Controller That Cisco Unity 8.x Monitors

Changing the Global Catalog Server That Cisco Unity 8.x Monitors for Directory Updates

Changing the Global Catalog Server with Which the Cisco Unity 8.x MAPI Client Communicates

Note that all sections apply only to Exchange 2003.

Changing the Domain Controller That Cisco Unity 8.x Monitors

If a domain controller (DC) stops functioning, Cisco Unity automatically finds another one and resynchronizes the SQL Server 2005, SQL Server Express 2005, SQL Server 2000, or MSDE 2000 database on the Cisco Unity server with the directory on the new DC. However, if the current DC is being decommissioned, is malfunctioning, is being rebuilt, or will be off line for maintenance, you can use the DC/GC Reconnect Settings tool to:

Specify the DC that Cisco Unity automatically switches to when the current DC is taken off line.

Schedule the resynchronization of the Cisco Unity database with the Active Directory database on the new DC.

Manually change the DC that Cisco Unity monitors before the current DC is taken off line.


Note Changing the DC that Cisco Unity monitors requires that directory data on the Cisco Unity server be fully resynchronized with the Active Directory. This process is CPU intensive, so we recommend that you make the change during off-peak hours.


If failover is configured, the DC/GC Reconnect Settings tool will run only on the active server. In addition, you do not need to change settings on both servers because all of the data for the DC/GC Reconnect feature is stored in the Cisco Unity database and is automatically replicated between the two servers.

To Change the Domain Controller That Cisco Unity Monitors


Use the DC/GC Reconnect Settings tool, which appears under Administration Tools in the Cisco Unity Tools Depot. (The Tools Depot icon is on the Cisco Unity server desktop.)

Refer to Help for the DC/GC Reconnect Settings tool for information on how to use the tool, including options for manually changing the DC immediately or specifying the DC that Cisco Unity reconnects with if the current DC stops functioning.

If failover is configured, use the tool on the active server.


Changing the Global Catalog Server That Cisco Unity 8.x Monitors for Directory Updates

If a global catalog server (GC) stops functioning, Cisco Unity automatically finds another one and resynchronizes the SQL Server 2005, SQL Server Express 2005, SQL Server 2000, or MSDE 2000 database on the Cisco Unity server with the directory on the new GC. However, if the current GC is being decommissioned, is malfunctioning, is being rebuilt, or will be off line for maintenance, you can use the DC/GC Reconnect Settings tool to:

Specify the GC that Cisco Unity automatically switches to when the current GC is taken off line.

Schedule the resynchronization of the Cisco Unity database with the Active Directory database on the new GC.

Manually change the GC that Cisco Unity monitors before the current GC is taken off line.

If the Cisco Unity MAPI client is using the same GC that Cisco Unity monitors for directory updates, you also need to change the server that the MAPI client uses. Otherwise, voice messages will not be delivered. See the "Changing the Global Catalog Server with Which the Cisco Unity 8.x MAPI Client Communicates" section. (You do not need to use the same GC for both purposes. You only need to change both settings if one GC is currently being used for both purposes and that GC will not be available.)


Note Changing the GC that Cisco Unity monitors for directory updates requires that global data on the Cisco Unity server be fully resynchronized with the GC database. This process is CPU intensive, so we recommend that you make the change during off-peak hours.


If failover is configured, the DC/GC Reconnect Settings tool will run only on the active server. In addition, you do not need to change settings on both servers because all of the data for the DC/GC Reconnect feature is stored in the Cisco Unity database and is automatically replicated between the two servers.

To Change the Global Catalog Server That Cisco Unity Monitors for Directory Updates


Use the DC/GC Reconnect Settings tool, which appears under Administration Tools in the Cisco Unity Tools Depot. (The Tools Depot icon is on the Cisco Unity server desktop.)

Refer to Help for the DC/GC Reconnect Settings tool for information on how to use the tool, including options for manually changing the GC immediately or choosing the GC that Cisco Unity reconnects with if the current GC stops functioning.

If failover is configured, use the tool on the active server.


Changing the Global Catalog Server with Which the Cisco Unity 8.x MAPI Client Communicates

If the global catalog server (GC) with which the Cisco Unity MAPI client communicates with Exchange is being decommissioned, is malfunctioning, is being rebuilt, or will be off line for maintenance, you need to specify a different GC. Otherwise, voice messages will stop being delivered to Exchange mailboxes.

If Cisco Unity monitors the same GC for directory updates that the Cisco Unity MAPI client uses, you also need to change the GC that Cisco Unity monitors for directory updates. Otherwise, data in the Cisco Unity directory will not be updated when data in the Active Directory is updated. (You do not need to use the same GC for both purposes. You only need to change both settings if one GC is currently being used for both purposes and that GC will not be available.)

If you also need to change the GC that Cisco Unity monitors for directory updates, see the "Changing the Global Catalog Server That Cisco Unity 8.x Monitors for Directory Updates" section.

If failover is configured, use the same GC for both the primary and secondary Cisco Unity servers.

If you already know the GC with which the Cisco Unity MAPI client communicates, skip to the second procedure, "To Change the Global Catalog Server with Which the Cisco Unity MAPI Client Communicates." If you need to determine the GC with which the Cisco Unity MAPI client currently is communicating, start with the first procedure.

To Determine the Global Catalog Server with Which the Cisco Unity MAPI Client Communicates


Step 1 If you know which account the AvCsMgr service logs on as, skip to Step 2.

If not, determine the account that the AvCsMgr service logs on as:

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

b. In the right pane, right-click AvCsMgr, and click Properties.

c. Click the Log On tab.

d. Make note of the account that the service logs on as.

e. Close the AvCsMgr Properties dialog box.

f. Close the Services MMC.

Step 2 Log on to Cisco Unity by using the account that AvCsMgr logs on as.

This is important because the value you need to change in the registry may not be visible if you log on to Windows by using another account.

Step 3 On the Cisco Unity server, start Regedit.

If failover is configured, you can start with either the primary or the secondary server.

Step 4 Expand the key
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Unity System Profile\dca...

(For example:
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Unity System Profile\dca740c8c042101ab4b908002b2fe182.)

Step 5 The name of the GC with which the Cisco Unity MAPI client communicates is displayed in the key 001e6602.

Step 6 Close Regedit.

Step 7 If failover is configured, repeat Step 3 through Step 6 on the other server.


To Change the Global Catalog Server with Which the Cisco Unity MAPI Client Communicates


Step 1 Log on to the Cisco Unity server by using an account that has the right to change the registry.

If failover is configured and you need to change the GC for both servers, you can start with either the primary or the secondary server.

Step 2 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 when Cisco Unity failover is configured, 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 3 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 Expand the key
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Unity System Profile\dca740c8c042101ab4b908002b2fe182.

Step 5 Change the value of the key 001e6602 to the name of the new GC (for example, 001e6602 = GCServerName.cisco.com).

Step 6 Close Regedit.

Step 7 Exit the Cisco Unity software.

Step 8 Restart the Cisco Unity software.

Step 9 Confirm that the Cisco Unity MAPI client is communicating with the GC:

a. For each Exchange server on which subscribers are homed, leave a voice message as an outside caller for at least one Cisco Unity subscriber homed on the server.

b. Confirm that the message waiting indicator for each subscriber is functioning properly.

c. Confirm that the message can be retrieved by using the phone.

d. If anything does not work correctly, confirm that you entered a valid GC in Step 5 and that you can ping the GC by name, fully qualified domain name, and IP address.

Step 10 If failover is configured and the MAPI clients now communicate with different GCs, repeat Step 1 through Step 9 on the other Cisco Unity server to configure it to use the same GC.