Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Changing the Exchange Server to which Unity 3.1(3) connects

I have unity 3.1(3) which is connected to Exchange 2000. Unity is already configured to connect to this Exchange server and is working fine. Exchange Server has to be installed on a new Machine. Is it possible to configure Unity to connect to this new Exchange Server.

Cisco Employee

Re: Changing the Exchange Server to which Unity 3.1(3) connects

How this SHOULD work is you simply uninstall the configuration setup and rerun it and pick a new Exchange server and you’re done. Unfortunately with Ex2K to Ex2K moves this is busted bigger than life itself.

The good news is this is working in 3.1(5) the way it should. The bad news is you’re not at 3.1(5) (it’s not shipping yet). The good news is you can do this manually without having to reinstall Unity. The bad news it’s a little hairy – but it can be done. This is kind of long, but it’s not as bad as it looks… take it one step at a time. Here's a somewhat edited set of steps from an internal QA document on how to do this:


"How to rehome Unity from one Exchange 2000 server to another"

NOTE: This has only been tested on Unity 3.1.

· Stop Unity.

· In AD Users and Computers, move user mailboxes from OldE2KSvr to NewE2KSvr. This includes the Unity Messaging System Account, example subscriber and example administrator accounts as well as the default distribution lists (all subscribers, unaddressed messages, system event messages).

· Open DohPropTest and force a full resynch of the AD monitor and the GC monitor. You do not need a password for this, just ignore the password and open DOHPropTest in read only mode. You can get this in the tools depot or in \commserver\techtools. The resync buttons are in the lower right – be sure to do a total synch of both the AD and GC monitors. There’s no indication when it’s done, I normally just watch the CPU monitor and when it settles down it’s done.

· Stop the AD Monitor (AVDSAD) and GC Monitor (AVDSGlobalCatalog) via the Services applet.

· Delete the following registry setting:++ HKEY_USERS > .Default > Software > Microsoft > Windows NT > Current Version > Windows Messaging Subsystem > Profiles > Unity System Profile

This is the message profile for the Unity messaging system account and it’s still pointing to your old box – if you delete it here and reboot Unity (later) the profile will get built to point at the mailbox on the new server automatically.

· Change the following registry settings to reflect the new server name. Be aware that some of these registry settings contain more than one reference to the previous Exchange server!

++ HKLM > Software > Active Voice > Doh > 1.0 > Mail Server Name++ HKLM > Software > Active Voice > MalEx > 1.0 > ServerName

++ HKLM > Software > Active Voice > Directory Connectors > DirSynchAD > 1.0 > Directory > DefaultMailboxStore

++ HKLM > Software > Active Voice > Directory Connectors > DirSynchAD > 1.0 > Domains > {your domain name} > Mailusers > MailboxStore

**NOTE** In more recent versions of Unity, the above registry setting is in GUID format. If your registry setting is a GUID, the change needs to be made in DOHPropTest (it’ll convert your server name into the GUID string for you). Open DOHPropTest (again it can be in read only mode here) and hit the “AD Monitor” button in the lower right. Select your domain on the left and in the right list box select “Mailbox_Store” and update the string to contain the new server name instead of the old. Press the “set” button when you’re done.· Start the GC monitor (AvDSGlobalCatalog) and AD monitor (AVDSAD) services in the SCM.

· Restart Unity

New Member

Re: Changing the Exchange Server to which Unity 3.1(3) connects

Are these steps valid for Unity 3.13?

Cisco Employee

Re: Changing the Exchange Server to which Unity 3.1(3) connects

In they are valid, but you might want to upgrade to 3.1.5 if possible. Doing this stuff by hand has been error prone with some other sites.

There were some problems with the E2K disconnect/reconnect that were fixed in 3.1.5 (see CSCdw58477)

On a side note, the E55 disconnect/reconnect to another E55 server would work just fine in 3.1.3.

On another side note, an E55 disconnect to a E2K re-connect didn't work all that well until 3.1.5 (see CSCdy35994).