Import existing Exchange2K & Unity subscribers to new Unity Server
I have a 3.1(2) Unity Server/Exchange2000 in production. We've purchased a new Unity 4.0(1) server/Exchange2000 and need to transfer all mailboxes & Unity subscriber info to the new server. I know in Exchange 2000 I can move mailboxes to a new server, but what about the Unity Subscriber info. I can't create/import a new subscriber because they already exist on the production server. Do I move the mailboxes, delete the old exchange & Unity accounts, and then create the new exchange user & Unity subscriber? Is there a tool to transfer both Exchange & Unity?
Re: Import existing Exchange2K & Unity subscribers to new Unity
Are the mail aliases between the two systems the same? If so then you can use the DiRT utility to move Unity subscriber information and, optionally, inbox messages as well. You can find the latest DiRT utilities here (be sure to use the latest ones):
there's a help file and training video out there as well that should get you from A to B.
If the mail aliases don't match it'll create new mailboxes for those users on the fly - you can then use the Migrate Subscriber Data tool to move the Unity information (and, optionally, the inbox content as well) to the correct corporate email account. You can get this tool (and training video and help file) 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...