RE: [ActiveDir] LDAP and related Exchange question

[joe]

Title: LDAP and related Exchange question

Yeah it is about aduc and *possibly* the cdoexm interface if you use that to insert addresses.   Note that even with those tools it is possible to get dupes, it all comes down to directory latency and what DCs are involved. You can for instance even force the RUS to produce duplicates by having RUSes talking to DCs that are "far" from each other in terms of latency.   Duplicate addresses in proxyaddresses is a pretty common issue in larger orgs or anywhere where scripts and some non-MS management tools are used. Checking for dupes in proxyaddresses is something worth doing occasionally as well as checking for duped legacyExchangeDNs.   You have a better chance of not running into dupes if you are good at maintaining unique samAccountNames and mailNicknames across the forest. It can still happen, but some of the easier ways of it occurring get avoided.      joe   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, March 03, 2005 9:34 PM To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] LDAP and related Exchange question I haven’t read the blog yet – I will – but uniqueness is enforced by ADUC (or any other provisioning mechanism that has the intelligence built into it). You can certainly shove colliding values into this attribute by other means.   Deji   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, March 03, 2005 5:58 PM To: ActiveDir@mail.activedir.org Subject: [ActiveDir] LDAP and related Exchange question   I was going through the You Had Me At Ehlo blog and ran across the most recent post which describes in some detail about how uniqueness is maintained in the proxyAddresses attribute.  I’m curious though… does this only apply for changes made through ADUC or does it apply to changes made through any mechanism (e.g. scripts, ldp, etc)? Here’s the link: http://blogs.msdn.com/exchange/archive/2005/01/10/350132.aspx. Some background… in all this madness to bring single-sign-on to fruition, we’re running into problems finding a unique value that can be used to tie AD to other directories when extracting information from a forest.  We were keying off samAccountName but found too many identical names from domain to domain. marcus c. oh \\.\core technologies\cox communications, inc. \\.\mvp\windows server systems\management [v] 404.847.6117     [c] 404.391.7097