|
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] 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. \\.\core technologies\cox
communications, inc. \\.\mvp\windows server
systems\management [v]
404.847.6117 [c] 404.391.7097 |
Title: LDAP and related Exchange question
- RE: [ActiveDir] LDAP and related Exchange question deji
- RE: [ActiveDir] LDAP and related Exchange question joe
- RE: [ActiveDir] LDAP and related Exchange question Mulnick, Al
- RE: [ActiveDir] LDAP and related Exchange question Marcus.Oh
- RE: [ActiveDir] LDAP and related Exchange question Mulnick, Al
- RE: [ActiveDir] LDAP and related Exchange question Gil Kirkpatrick
- RE: [ActiveDir] LDAP and related Exchange question Mulnick, Al
- RE: [ActiveDir] LDAP and related Exchange question Mulnick, Al
