We are having a Unity VM only setup. Exchange 2000 is running in the unity server. We are going to implement failover of unity server. For this we need to change the unity exchange server to the new server.
Shall we install the unity discs to install the OS and exhange server ?
During the changing of the messaging server will be mailbox also be moved to the new exchange server?
- Install the new Exchange server on a new server. Add to domain, same Exchange forest, etc You can use any Windows 2000/2003 or Exchange 2000/2003 discs. The Cisco discs are not required, but recommended to use.
- Run the permissions setup, so Unity sees a new Exchange server for subscribers.
- Move your subscribers to the new Exchange store
- check to see that all subscribers are working on the new server, MWIs work, message retrieval, etc
- Install your Failover server for Unity. keep ing mind that all versions are the same, patching, etc match your primary server
Of course, these are all basic... there a few guides that reflect what you are trying to do. But remember, you are doing two separate tasks. Move to a new Exchange server adding in Failover.
I followed the steps and i was stuck during the change of the partner exchange server procdure. when we went tried to change the exchange server via control panel options we need to move the mail box a a procedure. Unfortunately we are not able to move the mailbox and we are receiving the messsage MAPI PROVIDER FAILED. UNABLE TO CONNECT TO THE SOURCE SERVER.
If you installed the new Exchange server in the same domain, Exchange Org, it show up automagically. Just click on the mailboxes to move, and move to the new store on that server. It will rehome the mailboxes, update AD, hence updating Unity. Re-run permissions and Exchange stuff for Unity and you should be set. Unity will be able to MWI, deliver, retrieve from the new store.
If you are in a different domain, then you have to use DiRT. Export, then import and pray your alias match.
Step 1 Use the same procedures that you use for moving ordinary subscriber mailboxes in Exchange 5.5, Exchange 2000, or Exchange 2003 as indicated in the "Introduction to Cisco Unity Data and Message Storage" section.
Step 2 To prevent messages from unidentified callers from getting stuck in the Unity Messaging Repository (UMR) after the move, do the following sub-steps:
a. On the Windows Start menu, click Programs > Administrative Tools > Services.
b. From the Services window, stop and restart AvUMRSyncSvr service.
Once the UMR service has restarted (it may take a few minutes), Cisco Unity exhibits the following behavior:
Messages from unidentified callers that are addressed to subscribers who do not have full mailboxes are delivered.
As expected, messages from unidentified callers that are addressed to subscribers who have full mailboxes are not delivered. However, when Cisco Unity attempts to send a nondelivery receipt (NDR), the NDR gets stuck in the Unity Messaging System mailbox, and is never forwarded to the Unidentified Messages distribution list.
Step 3 To release any stuck NDRs from the Unity Messaging System mailbox, stop and restart the Cisco Unity software by using the system tray icon.
I used these steps successfully, not the ones mentioned in the reconfiguration/upgrade guide.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...