Single Inbox Issue with Unity Connection 8.5 and Exchange 2003

[dan hale]

Hello Unity Gurus,

I recently upgraded our Unity server to Unity Conenction 8.5. We are pressing hard to have unified messaging. However theres always problems it seems.

We have several 2003 exchange servers, two of the exchange servers split up our organization and one has half of the users mailboxes and the other server has the remaining half. So far the only way that I can get Unified messaging is if I create two separate Unified Messaging Services one for one half, the other for the other half.

This becomes a problem since now when I create the Unified Message account I have to know what server the user is on and the problem being is that I have 700 voicemail users ill have to look up. Not only that but, if our employees move from one site to the next and if the mailbox gets moved then I imagine most likely break unified messaging for that account.

I've read the install guide for Unity connection Unified Messaging and I understand that the second option is to have Connection to search for Exchange servers via Active Directory however, when I set that up and test it via unified messaging services I get an error " searching network...failed to locate domain controller via DNS. Failed to locate an exchange 2003 server."

DNS seems to work if I create single Unified Messaging Service and use the host name that way.

Anyone have any thoughts or found a work around to this issue?

Thanks,

Dan

[Brad Magnani]

Hi Dan,

A common issue is that the UM server either doesn't contain domain\ in front of the username and/or the password typed in was mistyped.  Carefully re-type the password and make sure domain\ exists before your UM account username.

Hope that helps,

Brad

[matthubach]

Dan, running into the same issue. You ever discover a work around?

[maratimer_2]

We have 41 exchange UM services configured in Unity Connection on 10 clusters, each one to the 2003 exchange servers.  This is the only way it will work for us, as e2k3 can not search for and find other exchange services.  For 2010, it is able to search by AD domain and site name, and we only have one connector configured on each server to the e2k10 environment.  I believe this is the way it works, and is difficult to manage but works.  Just my two cents.