On Apr 6, 2005 11:23 AM, joe <[EMAIL PROTECTED]> wrote: > Danny, are you sure that is the output from that command? Did you cut and > paste that command?
Fresh install of Windows Server 2003 SP1. One AD user account for testing. I am 99.9% sure it's the correct output. I copied and pasted from RDP. > That filter would only show user objects and the output > you show is all objects which would be more of a filter like objectclass=*. > I just verified the command you used in my forest and it worked fine except > it returned computers and users (as expected from the filter) and didn't > return any proxyaddresses (again expected from that command). That sounds right. To be honest, we played with ldifde in school many moons back, but I am just starting to play with it again today. > You need to correct these issues. > > You should change the filter to be > > "(&(objectcategory=person)(objectclass=user)(proxyaddresses=smtp:*))" Interesting. Makes more sense. > And you should change the attributes returned to > > "proxyAddresses" > > So the whole command would look more like > > ldifde -f smtpaddress.ldf -s myserver -r > "(&(objectcategory=person)(objectclass=user)(proxyaddresses=smtp:*))" -l > "proxyAddresses" Worked as advertised. Now would this (ldifde) compare to your AdFind tool? > Note that this will filter down to just user objects with proxyaddresses > that have smtp in them. Note that it will still return x400 addresses and > other values in the proxyaddresses attribute. You can't pick which values > you want returned out of the proxyaddresses attrib, it is all or nothing. I would rather all in this case, then. Thank you, Joe. ...D List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
