There doesn't seem to be a clean upgrade process from UC 1.x to UC 2.x. Oly the export/migration utility from ciscounitytools.com Am I reading correctly, it will only migrate subscribers, not call handlers or other stuff? Anyone have a good process to follow?
My team ran into this problem while putting together a UC training program. We went to ciscounitytools.com and there was a VoD that explained how to do the upgrade. Hope that helps!
You guys have anymore insight or other documents on how to accomplish this? Im going to check out the VoD, but I cant find any documents on the upgrade process.
The migration tool for Connection 2.x only handles top level subscriber data and messages - it does not include call handler data or anything else. It's pretty light and done largely through CSV import.
As a side note, I've released a beta version of COBRAS (Cisco Object Backup and Restore Application Suite) which will eventually support Connection 7.0 when it releases - this will allow for migrations from Connection 1.2 or Unity 4.0(5) and later to Connection 7.0 and include subscribers, call handlers, messages, routing rules and public distribution lists (with membership info) - a bit more comprehensive then the top level subscriber data offered in 2.0.
Unfortunatley I wont be able to make this fly in 2.0 because there is no off box database or stream file access available without root access (a support no-no). In 7.0 there is (when it releases).
Also, COBRAS will support going between unity versions (i.e. a 4.0(5) backup to a 5.0(1) restore) - currently only unity to unity moves/migrations/merges are supported, but if folks are interested, I've posted the beta version that's currently being tested by a number of sites:
Your comments are always appreciated Jeff!
So what is best bet then? Use the CSV export and then rebuild the call handlers manually?
Or can I do I do an inplace upgrade from 1.2 to 2.0 then do DIRT.
I have had great luck with the Global Subscriber migration tools between Unity 4.x to 5.x, then just rebuild CH's on the other side. Seems to work the best in upgrading when the message store is the same.
Upgrade is next week for me on Wednesday I believe.
There is no in place upgrade possible. There is no option to do a DiRT restore from a backup of 1.2 so the CSV import is your only option at this point.
GSM can't run against 2.0 because it's locked down - that means no off box file or DB access.
That's correct. The TOI for this covers some of the details for getting messages on which requires use of SSH:
What about the license file. Will i have to obtain a new one. I used the software subscribtion and ordered the UNCN2-SM-VUP-K9, but there wasn't any new PAK in the box!
We are going to migrate the customer next week, the 27 and 28th.
You will probably have to checkout a new license file from the Product Upgrade Tool. Use the Smartnet contact to obtain this TODAY. Licensing takes awhile.
If not, email firstname.lastname@example.org and see they can do anything for you
You have to get a new license file - there is no migration of license files between the Windows based 1.x product and the Linux based 2.x product.
Is there anyway we can migrate 1.x to 2.x and include the subscribers greetings, settings, etc? Or is it just easier for them to re-record their personal greetings, reset their PINs, etc.
Some of the subscriber settings (including PIN) _are_ included in the migration tool - check out the TOI referenced earlier in this thread.
Items not included (greetings, notification devices etc...) will have to be rebuilt by hand by either the admin or subscriber.
OK, here is the first gotcha to look out for. In version 1.x we were able to use the custom key mapping tool, no longer available in CUC2.x.
yes - the admin interface for custom key maps did not make it into CUC 2.x (the key mapping engine is actually in there, you just can administer it since off box file access is denied and the web based admin could not fit the feature into the schedule).
Unity Connection 7.0(1) (in EFT soon - see Laura's post looking for folks to sign up for that) has all 3 custom key maps available in the web based admin now.
Next Gotcha, not too bad though, the import tool seemed to have expired all the users passwords, so they are forced to change them next logon.
I believe the password expiration value is pulled from the subscriber template selected for the restore process - by default this will be configured to require a PW change on first login.
Laura's EFT notice can be found here:
No, we changed the template before we migrated. It sets both the voicemail and web application to expired.
Thanks for the link.
I can attest that the greetings do not get migrated, only the voice names. It would seems simple enough.
My workaraound is that I performed a DIRT backup on the 1.2 version. I then went through every wav file and renamed them to the extension. Then set them using the media master under each user. Very labor intensive.
Understood that it's labor intensive - wish I could do something about it but I simply can't - the 2.x platform is a "security first" approach and off box file access is heavily restricted (hence the painstaking setup of the SFTP server required for the migration process). I know it _seems_ like it should be a no-brainer to include greetings in the mix but trust me, it's anything but.
As noted earlier, the Connection 7.0 product will have a far more robust migration scheme that will include greetings an just about all subscriber and call handler related settings as well as support for migrating from Unity 4.x and later as well as CUC 1.2. Off box file/DB access and stream server access is now an option (off by default, of course) which makes such things considerably easier to pull off.
The forced password reset thing sounds like a bug to me - it should be using the template for that, not forcing it on all the time. The admin crew should look at that.
That's where we drew the line. End users need to run through first time enrollment to set their personal greeting.
Also note, bulk edit tool will not handle 10 digits. Limited to 9. It's a bug they are working on.
Overall, I would advise that this is not an upgrade at all. Anyone interested going from unity connection 1.x to 2.x should consider and plan like it is a totally new installation.
Has anyone heard updates on this process. I am in a situation where I have to upgrade 1.21 to 2.x and can't seem to find any links on Cisco's website.
Any help would be appreciated.