Replacing our Unity Server

Unanswered Question
Apr 25th, 2003
User Badges:

Currently in our production system, we are running 2.4.6(161) and Call Manager 3.0(12). We are planning on upgrading the Call Managers to 3.2 and installing new Unity servers in failover mode running 3.1(5).

We have already built the two Unity servers running 3.1(5) but have not configured them yet. We have a lab built with two Call Managers and we were wondering how we could test the Unity servers in the lab. Would we need to have a domain controller and an exchange server in order to test?

Also, is there a procedure to migrate the subscribers from teh 2.4.6 server to the new Unity servers or we have to do a flash cutover?



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
lindborg Fri, 04/25/2003 - 11:44
User Badges:
  • Cisco Employee,

Yes, Unity needs to be in a domain and have an Exchange or Domino (for 4.x) server to connect to.

The process of upgrading from 2.x to 3.x is documented in the install guide. Here's a link to the 3.1(x) install guide for the 2.x upgrade section:

vcornett Mon, 04/28/2003 - 10:55
User Badges:

Let's say that we build a test environment with the same domain name and we build an exchange server for our lab. Do you see any potential problems from the test integration when we moved the Unity servers to our production environment ?



sallwine Mon, 04/28/2003 - 11:10
User Badges:

Yes, the SIDs will be different in the new environment ... which I believe does not play nice with SQL. Also I believe unity uses SID information and objectIDs for some of its table, which would probably not be happy either.

vcornett Mon, 04/28/2003 - 13:09
User Badges:

Sounds like testing in the lab is not going to get us anywhere. would it be possible to intsall the new Unity servers parallel to the existing production server, create some uone ports that point to the new Unity servers, then setup a few test group users and forward them to the new Unity voice mail ports


This Discussion