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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Moving Unity 4.0.5 to new domain using DIRT

A new system has been rebuilt in the new domain and configured to attached to the new exchange server.

When running the Dirt restore all subscribers are being remapped properly but most of them are being created as internet subscriber only (No exchange message store)

About 10% of them are created correctly as mailbox user.

We can't seem to find what makes those users different than the others.

Does anybody know what is causing dirt to create a subscriber as internet only versus mailbox user?


  • Unified Communications Applications
Cisco Employee

Re: Moving Unity 4.0.5 to new domain using DIRT

DiRT version? Always a good idea to include this.

DiRT doesn't create the subscribers, the SQLSyncSvr does - couple things could be happening here. First, you could already have a contact in AD that matches the alias - in this case the syncher will bind to that account and not create a new user.

If the SubscriberType value in the SQL table for the user is "2" instead of 1 (for Exchange) or 3 (for Domino) then the syncher will create an internet subscriber instead of a full subscriber - this would have had to be in your backed up database of course - DiRT doesn't go through the subscriber tables and change this prior to synching with the directory or the like.

New Member

Re: Moving Unity 4.0.5 to new domain using DIRT

The problem seems to be related to an exchange migration tool we use from quest.

This software populates a hidden field called targetaddress.

We were able to get the DIRT import to work properly, however whenever the targetaddress is being populated, the subscribertype seems to be changed to 2 in unity. We don't know why.

We were able to workaround the problem by changing the type back to 1 manually in SQL but we are not sure if this is a valid operation since we don't know what is changing the subscribertype, when and why.

Cisco Employee

Re: Moving Unity 4.0.5 to new domain using DIRT

Not real sure what that migration tool is doing but it sounds like it's setting something for users that makes the synch svr think the user is not a user with a local exchange mailbox but a contact that redirects it's messages to another address (targetaddress sounds an awful lot like something along these lines) - not real sure right off hand.

If after doing the synch the users in AD all have valid mailboxes and the subscriber type in the SQL database for them is still "1" and the SMTP address matches that of the full user in AD (and is not, for instance, the target address) then it should be OK. But of course you're sailing uncharted waters here so I can't say for sure...