In ILM 2007 implementation with only a one way synchronization of users and contacts from AD to ADAM, we uniquely identified MV objects based on anchor (cn and dn attributes for that record inAD) along with another custom attribute.Now in ILM "2" RC evaluation I am exploring provisioning of new users and contacts from multiple authoritative data sources, and re-thinking ways to uniquely identify MV objects forsearches, joins etc. I was thinking of usingobjectGUID and/or objectSID in conjunction with cn and a custom attribute. Any thoughts?Thanks.Anu

You are right on the money!You might want to take a look at the Design Concepts for Correlating Digital Identities.This document should answer your questions.To answer your current question - the ideal Correlation ID doesn't change and does not contain any kind of encoded information.This pretty much eliminates SIDs as CID.In general, GUIDs are a good thing to use for this purpose.Cheers,MarkusMarkus Vilcinskas, Technical Content Developer, Microsoft Corporation

Thanks Marcus - great to share an "ah-ha" moment.Cheers.Anu