Two Unity 3.1(5) servers with Exchange 5.5 upgrding to one Unity 4.0(3)
I have a customer that has 2 sites with Unity 3.1(5) installed with Exchange 5.5 on the back end. They wish to combine both servers and upgrade them to Unity 4.0(3) with Exchange 2003 as the mail store (with both Unity and Exchange on new seperate hardware). Is there a way of doing this easily, or would we have to install Untiy 3.1(5) on the new system, Use DiRT to copy and restore the settings, then Upgrade to Exchange 2003?
Re: Two Unity 3.1(5) servers with Exchange 5.5 upgrding to one U
No, that doesnt sound quite right
First, you can install your new 4.0(3) server connected directly to Exchange 2003 and do the import from a backup where it was pointed to 5.5 theres no need for step 4 there if Im understanding what youre doing.
Next, DiRT will bind to existing accounts for user automatically (if a match is found) or create new users in AD/Exchange (if a match is not found) so step 6 should not be necessary. Check the DiRT help file for details on how the search process works in the directory you can get the latest help file off its home page here:
Finally, if the goal is to end up with a single Unity server with all your subscribers on it instead of two separate servers then the last step doesnt fly DiRT does not merge users from another box its used to migrate entire boxes configurations onto a new box. It requires that you run it on a clean install of the same version of Unity that you backed up for this reason. If you wish to move users onto a single box you can upgrade both boxes separately with this procedure (i.e. end up having two Unity 4.0(3) servers with your users on them) and then use the Move Subscriber Data component of the Global Subscriber Manager tool to move one user at a time from one Unity 4.0(3) server to the other and merge you boxes that way this is not a batch operation, however youll have to move each user one at a time. You can check out the help file and training videos for Global Subscriber Manager on its home page here:
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...