|
I’d definitely recommend using
generalized time (syntax 2.5.5.11 OMSyntax 24) or UTC Time (syntax 2.5.5.11
OMSyntax 23). It gives you the nicer ADSI/SDS data marshaling to date times
and is pretty easily searchable. I think using the FILETIME/integer8 thing is
ok, but kind of a pain and not that natural to deal with unless the native
format you are using is a FILETIME. I think the string is the least good way
to go as the DSA doesn’t validate it for you. Joe K. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Isenhour, Joseph I'm
looking for some opinions on a schema extension. I need to store a date
type in AD. I figure I have several options. Store
it as a long integer. To determine the date the consumer will need to
count the nano seconds from a certain date (the way that pwdLastSet works) Store
it as a date type (which I've never used, and looking at the current schema it
appears that most people do not choose this option). Store
it as a unicode string and come up with a format like: YYYYMMDD[ss][ss]
Does
anyone have an opinion on how this should be done? Thanks
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. |
Title: Storing dates in AD
- RE: [ActiveDir] Storing dates in AD joseph.e.kaplan
- RE: [ActiveDir] Storing dates in AD Gil Kirkpatrick
- RE: [ActiveDir] Storing dates in AD Isenhour, Joseph
- RE: [ActiveDir] Storing dates in AD Isenhour, Joseph
- RE: [ActiveDir] Storing dates in AD Mulnick, Al
- RE: [ActiveDir] Storing dates in AD Gil Kirkpatrick
- RE: [ActiveDir] Storing dates in AD Isenhour, Joseph
- RE: [ActiveDir] Storing dates in AD joseph.e.kaplan
