We just attended a seminar on Unity Connection 7.x and we are considering migrating to Unity Connection from our current Unity 4.2. Is there a migration path available for this? Does anyone here on Netpro have any experience with a migration from unity to unity connection? We went with Unity 4.2 with licensing for Unified messaging but our AD has issues that have been holding up unified messaging. We loved that now Unity Connection works with SMTP to forward voicemail wave files to on mailbox. Just trying to get a handle on what we would need to do to implement Unity Connection. Any insight or direction would be great.
We already have docs on the procedure:
Migrating from Cisco Unity 4.x or Later to Cisco Unity Connection 7.x
You can find all the install, configure, upgrade, migrate, etc docs here
if this helps, please rate
Hi Vicky -
Here is a link to the COBRAS tool used in the migration - http://www.ciscounitytools.com/App_COBRAS.htm
The training videos are excellent! I'm sure there are a number of us, myself included, preparing for this upgrade. I will be moving 5 Unity servers to Unity Connection - preparing the hardware order now. Unity Connection is integrated messaging - users can access their voice messages from Outlook using IMAP, if this is enabled on the Exchange servers.
Quick additional question. Our migration would involve moving a primary and secondary Unity 4.2(1) with a separate exchange message store box to Unity Connection 7.x. Would we still need our Exchange message store? What changes would the make in our server count?
Any guidance would be great!
I think this design guide will help - http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/design/guide/7xcucdg060.html
And the platforms guide shows the hardware config required for the cluster -
You will not need your Exchange message store - all voice messages will reside on the UC servers.
We did this (well, from Unity 4.0(5) anyways) to base 7.0(2) and ran into a horrible issue. When a user (via phone or PCA) or admin (via CUCA) changes the PIN, the user can no longer log in!
Make sure you read up on these two bugs:
There is no "fix" for the problem, so now we have to figure out what we're gonna do with these 3000 accounts.
I'm hoping that after we apply the patch, users can log into PCA and change their password.
if you read up on those bugs you will see that there is, indeed, a fix. The bug is in the Pw management layer - if you apply a recent 7.0(2) ES (or 7.1) prior to importing users (either via BAT or CSV or COBRAS) then you wont run into this issue. If you import and then apply the patch, it wont "fix" the users you've already imported.
as ever it's always a good idea to make sure you're at the most recent ES on the mainline if you can.
Thanks for clearing that up Jeff. I meant to say there was no fixing the users that were already imported. My apologies.
We're still getting our head around the new software release structure, especially since the ES's are not published to CCO, you never know what the last one is or when one was released.
I guess we could check every month with the TAC to see what the latest ES is.
Perhaps I'm missing something.