Post-upgrade activities

After successful upgrade, the Preview Outbound seat count will not be carried forward in case of an upgrade from Unified CCX 7.0(2)ES03 to Unified CCX 9.0(x). By default, the Preview Outbound seat count will be initialized with the maximum supported value for the given hardware type. You need to manually modify the seat count in the System Parameters Configuration page of the Unified CCX Administration according to the usage.

Table 1 Maximum Preview Outbound seat count

Hardware Type

Maximum Preview Outbound Seat Count

Cisco MCS-7845

300

Cisco MCS-7835

75

Cisco MCS-7825

75

Cisco MCS-7816

50

Others

300

After successful upgrade, HTTP trigger will work on port 9080 in Unified CCX 9.0(x). Also, applications using the HTTP port 8080 should be changed to 9080. To change this, choose System > Applications on the Unified CCX 9.0(x) Administration interface, and then change the port in the applications using them.

Build second node in HA setup

To build the second node in an HA setup after the upgrade is complete on the first node, do the following:

Procedure

Step 1

Add the second node information to the first node using the Unified CCX 9.0(x) Administration web interface before you install the second node.

Caution

In case of HA setup, you should start installing the second node only after the upgrade on first node is completed successfully to avoid data conflicts.

Step 2

Install the second node and log in to the Unified CCX 9.0(x) Administration Web interface to perform the Add to Cluster operation (through LAN or WAN) so you can add the second node to the cluster.

Note

If you are upgrading Unified CCX (old version) setup having multiple device pools (for Call Control Groups) to Standalone Unified CCX 9.0(x), delete all device pool rows, choose a single device pool from device pool drop down list and click update to proceed.

If you are upgrading a two-node Unified CCX (old version) setup having multiple device pools (for Call Control Groups) to Unified CCX 9.0(x), performing initial setup configuration on the second node after the upgrade would merge all multiple device pools to a single default device pool. However, you can manually assign a different device pool to the Call Control Group if the default device pool is not the intended one.

Run configuration tool

After you complete upgrading the second node, you must run the Unified CCX Desktop Client Configuration Tool to create correctly-configured MSI files for the client applications. The Automated Update feature uses these MSI files to update the client desktops the next time users launch a Cisco Agent Desktop application.

Procedure

Step 1

Log in to the Unified CCX Administration web interface.

Step 2

Choose Tools > Plugin > Desktop Suite > Client Configuration Tool.

Note

Reinstall any Cisco Agent Desktop installations that had been previously deployed.