Imanami Community

Hi everyone,

I'm testing out DTM hoping to synchronise/create mail-enabled contacts from our CRM (SQL) to Active Directory, I’ve imported a few records (fields etc) into access and set up a DTM job to create the contacts with email addresses, names, etc.

I‘ve setup a contact with a test email address and also put the same email address into the access database to test for duplication. When I preview a job I get an error message “Error occurred after object was being added, Message: Email address exists in organization” which I assume is a good thing.

The problem however is when I run the job for real, it ignore the duplicate email address and creates a new contact regardless. This is obviously a problem, as I can’t have duplicate email address in AD.

Can anyone point me to a solution, I'm assuming I’ve set the job up incorrectly?

Thanks in advance for any help

Regards,

Nick

Hello Nick,

In the DTM wizard on the Destination directory page there is a browse button that displays the Active Directory tree structure.  In the case of creating objects it is used to search for objects in Active Directory that already exist.  You will need to click on the browse button and select the domain (your.domain.com) at the top of the tree.  The next page in the wizard is the Create Objects page, which also has a browse button to display the Active Directory tree.  You will use this to select the organizationalUnit the objects will reside when they are created.

Did this work for you?

Hi Robin,

Thanks for your relpy. I tried what you suggested an DTM is still creating contacts in AD using email addresses that already exist.

One thing i note is that i'm using our CRM's auto generated number ID as the key field in DTM (adding it as a custom attribute), when i change the primary key to be targetaddress (email) it recogises the pre-existing email address and updates that record with the changed fields.

If possible i need to use the CRM ID as the primary key, however i guess i could delete all AD contacts then import all from scratch...

 Any ideas?

On a side note any ideas on how DTM handles orphaned contacts? Best case for me to be able to remove the contact once they are not present in the access database (which queries the SQL CRM).

Thanks very much,

Nick

Hello Nick,

In order for DTM to locate the pre-existing contact in Active Directory, I recommend using targetAddress as a key; however, DTM will allow multiple primary keys to be used.  So, you can use both the CRM ID and targetAddress to locate pre-existing contacts in Active Directory.  Would this work for you? 

DTM has the ability to delete orphaned contacts from Active Directory.  To perform this task, please follow the instructions provided in the Imanami Forum post at the link below:

http://forums.imanami.com/ShowPost.aspx?PostID=4188

Hi Robin,

Thanks for your help again. I tried what you said about having the two primary keys, still no luck, also i need to be able to update email addresses but when it is a primary key it will only look at new objects.

I tried writing a VB script to check AD before creating the CRM Id, but i realised after that System.DirectoryServices isnt allowed to run... So Im not sure where that leaves me, im surprised that DTM doesnt check for pre-existing email addresses before creating the contacts? how does everyone else wants to creates contacts, users etc achieve this?

Regarding the deletion of orphans, thanks for the link, i've setup the databse to include the extra fields etc, how do I get DTM to then delete? I can only see the option for creation of new objects not their removal...

 Once again thanks very much for your efforts,

 Regards,

Nick

DTM does have a PowerTool that may help to resolve the issue with contacts being duplicated in Active Directory.  In order to make a request for the tool, please contact Imanami Client Services by emailing: support@imanami.com for more information. 

We highly recommend the accounts be disabled before taking steps to delete the accounts in the destination.  With that being said; when Active Directory is the destination directory in the DTM wizard there is a suedo attribute called, "Delete Account" within the schema.  If you add this attribute with a "Static" transform value of "True" it will delete the accounts that are located in the source file.  It would be best to use a .csv file that contains a list of the account to be deleted from the destination, as well.  

Have a great day.