Service Desk Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Active Directory Primary Key for Sync

Highlighted
MichelleR
Occasional Contributor

Active Directory Primary Key for Sync

We are in the process of implementing the export/import from AD to SD 4.5 sp17. In order to ensure that we don't get duplicates when a name changes, we'd like to use something for a primary key. I've tried the SID from AD, but it's binary and doesn't work. We don't currently use employee numbers, so I'm wondering what everyone else out there is using. Look forward to seeing your responses!
4 REPLIES
Jonathon Druce
Honored Contributor

Re: Active Directory Primary Key for Sync

Will the CN change? If so it is a real issue. There is nothing that is able to be used as a key in your data. Remember you can use a combination of attributes.
Radovan Skolnik
Honored Contributor

Re: Active Directory Primary Key for Sync

CN or DN could be worth attempting (if they're not about to be changed). Also e-mail address could be a good one (if you have it inside AD). Login name as well.
Vasily Kamenev
Honored Contributor

Re: Active Directory Primary Key for Sync

HI, I'm use uSNCreated and set it in SourceID. Working half of year , no problem yet.

Vassili
MichelleR
Occasional Contributor

Re: Active Directory Primary Key for Sync

Thanks for all of the responses thus far. Yes, the CN and DN could change in the event that we have someone get married/divorced/gender change. M
//Add this to "OnDomLoad" event