I've been tasked with standardizing the address for our agency contained in AD as we're going with a standard email signature. I already have the script written to read from AD/LDAP for the signature.
We (our agency) are at the tree level in AD, and we don't house domain controllers, that is maintained by the power hungry overseers of all agencies. So all of my queries are done at a read only level, I can only modify my own DN.
What I am up against... I've used a number of LDAP browsers, ldapadmin, JXplorer, and ADExplorer. When I view the streetAddress field in the browsers, they show as plain text as does the attribute property. When I create an LDIF of my DN, it comes out as a random string of characters. I don't see in any of the browsers any sort of options that would be causing this. Am I missing something really stupid?
In the meantime, I am making a request of the powers above to give me an export of my individual OU using LDIFE directly on the DC to see if it comes out in plain text.
Of course once it is all figured out I need to submit to them a modified LDIF for their import...
I really hope that I am overlooking something really stupid. Most of my previous LDAP experience was with SunOne, not an AD based LDAP.
Matt
We (our agency) are at the tree level in AD, and we don't house domain controllers, that is maintained by the power hungry overseers of all agencies. So all of my queries are done at a read only level, I can only modify my own DN.
What I am up against... I've used a number of LDAP browsers, ldapadmin, JXplorer, and ADExplorer. When I view the streetAddress field in the browsers, they show as plain text as does the attribute property. When I create an LDIF of my DN, it comes out as a random string of characters. I don't see in any of the browsers any sort of options that would be causing this. Am I missing something really stupid?
In the meantime, I am making a request of the powers above to give me an export of my individual OU using LDIFE directly on the DC to see if it comes out in plain text.
Of course once it is all figured out I need to submit to them a modified LDIF for their import...
I really hope that I am overlooking something really stupid. Most of my previous LDAP experience was with SunOne, not an AD based LDAP.
Matt