05-22-2013 05:17 AM - edited 03-19-2019 06:45 AM
We currently have both CUCM and Unity Connection systems running on the 8.5 version. We are starting to plan to move both systems to 9.1, we found the Cisco License Count Utility (UCT) tool that helps you plan for migrating your CUCM licensing from the DLU model in 8.5 to the UCL or CUWL model with ELM in 9.1. Does anyone have any information on how this transition works for Unity Connection licenses. we currently have close to 850 mailbox licenses on Unity Connection that we would like to merge into the CUWL licensing model post upgrade, but we aren't sure how the transition works.
Thanks,
05-22-2013 05:44 AM
Hi Ryan,
Here's how the license migration works;
These three scenarios are supported in order to migrate to Release 9.x Unity Connection licenses. In all three scenarios, the end result prior to the request for a Release 9.x license is that data is populated in the tbl_CUCLegacyLicenseInfo table in UnityDirDb database. Once this information is present, the same process is followed to request a migrated Release 9.x license.
In-place Upgrade of a Previous Version of Unity Connection to Unity Connection Release 9.x
License data is automatically copied into the table in the upgrade process.
Migration from a Previous Version of Unity Connection to a New Release 9.x Server via COBRAS
Download and run the latest version of Cisco Objected Backup and Restore Application Suite (COBRAS) Export for Unity tool from Cisco Unified Communication Tools.
Choose License Details for Migration to Connection 9.x and Later.
This option requires the OS administration credentials and NOT the application administration account used to run COBRAS.
Download and run the latest version of COBRAS Import for Unity tool, Release 1.2.10 or later, from Cisco Unified Communication Tools.
Choose at least one object to import. There is not a way to only import license data.
After the import is complete, the SQL table is updated if the import was successful.
Migration from Microsoft Windows-based Unity Connection to a New Unity Connection Release 9.x Server via COBRAS
Download and run the latest version of COBRAS Export for Unity tool, Release 7.0.121 or later, from Cisco Unified Communication Tools.
Run an export. The current license information will be included in the export data.
Note: There is not a specific option that needs to be checked. It will always be included.
Run the latest version of COBRAS Import for Unity tool, Release 1.2.10 or later, from Cisco Unified Communication Tools. For the wizard to proceed, choose at least one object.
After the import is complete, the tbl_CUCLegacyLicenseInfo SQL table is updated if the import was successful.
With data populated in tbl_CUCLegacyLicenseInfo by some combination of the above methods, complete these steps to request and install a migrated license file:
Note: The server must be registered with ELM first.
Log in to the ELM administration interface to which the server is registered.
Choose License Management > License Planning > Upgrade Licenses.
In the Product Type field, choose Unity Connection. Click Next.
In the Available Product Instances field, choose the server in question. Click the arrow to move the server name to Product Instances to Upgrade. Click Next.
Verify the license counts. Click Next.
Optionally, view/save the summary report.
Click Finish & Generate Request.
Follow the on-screen instructions to copy/save the text output and paste it into the Product License Registration migration portal.
Once the above steps are completed, the license file will be emailed.
To apply the license file in ELM, choose License Management > Licenses. Click Install License File and upload the received license file.
http://www.cisco.com/en/US/products/ps6509/products_tech_note09186a0080bf5921.shtml#concept3
Cheers!
Rob
"go easy...step lightly...stay free "
- The Clash
05-22-2013 05:50 AM
Rob,
I guess I need to clarify a little, the question isn't so much how the migration actually works, but what we get for licensing after the migration. On the CUCM side it's our understanding that you "exchange" DLUs for licenses, in which we can pick to get CUWL licenses, and if we get CUWL Standard licenses this should cover us for for the CUCM side and the messaging side. So what happens with our existing messaging licenses, do they also convert to CUWL licenses?
05-22-2013 06:16 AM
Hi Ryan,
Sorry about that my friend (my BAD!)
I believe you can choose UCL or CUWL licenses during the
final migration step (but we have not done this yet)
A: During the 9.x upgrade, all the unused DLU's will be taken into account. Only during the upgrade, this calculation is being done.
You can then define your UCL/CUWL requirement , while generating the " License Migration Request".
https://supportforums.cisco.com/docs/DOC-27483
Don't forget to check out the Drive to 9 docs as well
Cheers!
Rob
"go easy...step lightly...stay free "
- The Clash
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: