Unity 4.0 (4) to 4.2 Migration with EX 5.5 to 2003 upgrade

Unanswered Question
Jun 18th, 2007

Hello All,

On 6/12/07-6/14/07, we were rebuilding the 2 new unity 4.2 MCS-7835 servers (Unity 4.0.4 to Unity 4.2 migration) for 1 of the 3 clusters in production environment while still waiting for EX 5.5 to EX 2003 upgrade to be completed. On 6/15/07, we ran into a problem with 15 user voicemail down and the primary unity admin database change down, pretty much relating to one new unity server trying to talk to exchange server down and the new unity trying to talk to CCM Sub-1 down. So, we are thinking it is imperative to build a full test lab to completely test it out before we move it to production network without disrupting user work.

Based on the above, do you have any recommendations:

1. What would be the full test lab senario, like CCM, Unity, Exchange server, Domain Controller, etc?

2. Do you or do you have any client/customer do the same path of Unity migration with same senarior (Unity 4.0.4 to Unity 4.2 migration with Ex 5.5 to Ex 2003 upgrade)? What are their successes and pitfalls?

3. Do you or does Cisco have any detail documentation about this path of Unity migration with same senario?

4. What are the best practices for this path of Unity migration with same senario?

Thanks for your kind and great help and

Best regards and have a nice day.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)


This Discussion