UCCX 7 to 8

Unanswered Question
Aug 30th, 2010

My customers #1 concern is no down time if possible. They have agreed to a new install option on rls 8 with a new IP address, to run in parallel with UCCX 7 for a short time. I have thought about all the basic things (move a few agents over at cut time, reinstall clients, and remove the triggers from the old and build in the new, etc). My worry is the package that they ordered from Cisco, and the old rls 7 licenses. Here is what was ordered.

SOFTWARE

CCX-UPG-EHA-70-80=  / CCX ENH HA 7.0 TO 8.0 HA ENH UCSS Major Upgrade x2

Secondly, can I apply the 7 licenses to UCCX 8, or will I have to get new ones issued? Thanks in advance.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Anthony Holloway Mon, 08/30/2010 - 13:00

First of all, you need to make sure your CUCM version supports both UCCX 7 and 8.  Check the compatibility guide for that one.

You don't need to reinstall CAD, as it has a feature built in to auto upgrade.  The only required action would be to point CAD at the new server.  There are a couple different ways to tackle this, so look into either running postinstall.exe on each client and typing the new ip address, or modifying the registry of each client (which is what postinstall.exe does).

The license you listed will upgrade an existing UCCX Enhanced High Availability cluster from 7 to 8.  I hope that is what you have, versus Premium, etc.  As with any upgrade you would apply the license files from your 7x system, along with the new 8x license to the new 8x server.  Granted you are doing a fresh install, but this will still work.  I have done it several times.  Simply zip your .lic files (no folder) and upload the zip when you are going through the license upload piece of the install.

Build your triggers and cti ports on the new system with new numbers, then swing your translation patterns at the moment you want to convert.

Give your app users new names.  If you haven't done so in the past, now is a good time to rename them something meaningful:  uccx_rmcm, etc

Actions

This Discussion