Networking a 4.2 Unity to a 5.0 Unity

[Dan Reynard]

Originally we were looking at doing a "Failover" setup. But due to hardware limitations this is not possible. So, here's the scenario: We have a 4.2 Unity Server up and running with 1966 subscribers on it. We have a 5.0 Unity Server licensed for 2000 subscribers and would like the two networked together in order for message transfers and call handler operations.

4.2 Server: Has OS 2000 and Exchange 2000 on it with an Active Directory

5.0 Server: Has OS 2003 and Exchange 2003 on it with an Active Directory

Both are domain controllers in their own domains. What are the main concerns I need to look out for? Does the 4.2 server need to be upgraded in order to avoid any major issues?

[Craig Cooper]

Hi Dan,

An upgrade wouldn't be necessary, however, unfortunately, if the two Cisco Unity servers are each in their own domains, and not in the same Active Directory forest, then they can't be digitally networked.   For Unity Digital Networking, you need to have the two servers on the same Active Directory forest.

Personally, I'd be tempted to just use COBRAS to Export everything I can from the version 4.2 server then COBRAS Import to bring it all back onto the Unity version 5.0 server (on the more recent version of OS and Exchange).

Kind regards,

Craig

[Dan Reynard]

Craig,

Thank you for the response. I was thinking that may be what we needed to do. But wanted to check to see if anyone else had done it. Just to see what if any issues arose.

Along those lines, would I really need to run COBRAS? Wouldn't the GSM tool do what I need? And that would be to move the Active Directory contents(subscribers info) to the 5.0 server. Reason I ask is this, it's my understanding that COBRAS moves all subscriber info and call handlers associated with the Unity Platform and GSM moves all Active Directory content. If I'm incorrect in this please let me know.

Thank you,

Dan

[Craig Cooper]

Hi Dan,

GSM is best used to move the subscribers between servers if they are on the same AD, particularly where their mailboxes can also remain on the same AD domain and Exchange server... however, if they're in different domains then COBRAS updates the new Active Directory with all the information required for the users that are being migrated (as well as creating mailboxes for them, in Exchange, if they don't already exist, or have mailboxes, on the new domain).

Kind regards,

Craig