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

Complex Unity Domain Issue

College campus running separate Unity servers with IMAP/Off-box Exchange message stores; one for faculty/staff, one for students. Both servers point to an existing AD structure though under separate OUs. The client's existing AD user accounts didn't have Exchange enabled - they use a different mail system - which prompted us to go this route. Due to issues with password synchronization (e.g., they can't change Unity PCA passwords without logging into the domain with their Unity accounts) and just having separate domain IDs (we're using the extension as the Exchange Alias), they want to have their existing domain accounts be the Unity alias. They essentially want both Unity servers and their existing domain accounts under one OU.

I imagine moving the OUs, having the customer enable Exchange on the existing domain accounts, deleting all of the existing Unity accounts and re-importing everything back from AD - now with the single domain account.

Is this possible? What issues can we run into here? Will this fix our synchronization problem? Can this be done with two separate Unity servers pointing to one OU?


Re: Complex Unity Domain Issue

There is a tool you can use with DiRT to re-map aliass. From what I gather in your issue, you are trying to merge it all into one domain. But you want to change the aliases to match a new scheme.

In DiRT, you can do this. Create a DiRT backup, open up the MDB in access or whatever and update the aliases to what you want them to be.

in your new domain, you can either create new accounts with the new alias, or have DiRT create the accounts when you do a restore.

If you are only moving voicemail from one server to another and not the settings, you can use ExMerge to export all the subscriber voicemails to PST. Rename the PSTs to whatever you want them to be now, then re-import them to the new accounts with the udpated alias.... of course.. if you have 1000 accounts, it could be brutal and the DiRT database maybe a better option.

Re: Complex Unity Domain Issue

Hi -

There is also another tool you may want to consider using - Migrate Subscriber Data Tool. Here is a Cisco link - there is a self-executing video and help for it. Make sure you use the correct version. It is TAC supported, so you could always check with them on its applicability to your situation.

Also, you may want to rerun Permissions Wizard to make sure your containers have the correct permissions needed for the unitydirsvc and unitymsgstore accounts. As long as the OUs do not block inheritance from permissions set at the domain level, you should be OK.


CreatePlease login to create content