search for: integer8

...102 52 54 45 52 56 101 102 45 98 49 54 53 45 50 55 100 102 52 52 54 56 56 52 51 98 46 95 109 115 100 99 115 46 99 111 109 112 97 110 121 51 46 100 100 0 schemaInfo OctetString 1 255 0 0 8 110 5 226 34 174 70 95 239 72 177 101 39 223 68 104 132 59 showInAdvancedViewOnly Boolean 1 TRUE -uSNChanged Integer8 1 0x61C4 -uSNCreated Integer8 1 0x1006 +uSNChanged Integer8 1 0x8 +uSNCreated Integer8 1 0x8 whenChanged GeneralizedTime 1 27.01.2016 13:11:42 whenCreated GeneralizedTime 1 27.01.2016 9:28:03 _____________________________ At finally, problem looks like WERR_DS_DRA_SCHEMA_MISMATCH replication p...

...t;* attribute and works for all Active Directory versions since Windows 2000: The attribute lockoutTime holds the date and time of the account lock event - but the value is stored in the complex format of a Microsoft DateTime Interval timestamp <http://www.selfadsi.org/deep-inside/microsoft-integer8-attributes.htm> (64-Bit Long 'Integer8': 100-nanosecond steps since 01/01/1600). Fortunately, we don't have to calculate a certain value in order to unlock the regarding account: It's enough to write a Null value into the lockoutTime attribute i.e. replace whatever is in loc...

Mandi! Rowland penny via samba In chel di` si favelave... > I think you are over thinking this ;-) I'm simply applying the policy... ;-) https://docs.microsoft.com/it-it/windows/win32/adschema/a-lockouttime say at the bottom: This attribute value is only reset when the account is logged onto successfully. This means that this value may be non zero, yet the account is not locked