Michael Ströder wrote:
> Also a reason why one should not bother with retrieving a recent AD
> schema at all. I vaguely remember even more mess with e.g. inetOrgPerson
> class when installing Exchange before W2K3R2 schema etc.
> 
> Conclusion: Make your AD-specific scripts simply work even if it looks
> not LDAPv3 compliant and leave the schema mess to your AD admins. :-)

I'm extremely sorry to hear this.
And wished I was able to leave it to the AD admins, but alas I can't.

Anyway, thanks Michael for the information.

-- Roland

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Python-LDAP-dev mailing list
Python-LDAP-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Reply via email to