AccountExpires is similar functionality to PwdEndTime form Draft-behera-ldap-password-policy
We recommend when an account is created and the account never expires, then set this value to "0".
A value of:
What we found out was the MMC Account Tab raises an error if it attempts to read the large value. If a user object has an expiration date, and then you remove this date in ADUC by selecting "Never" on the "Account" tab, the GUI sets AccountExpires to 0.
Thus, the values 0 and 2^63 - 1 both really mean "Never".[1]
If you use the Microsoft Management Console to set the account to expire on July 15, 2007, the eDirectory attribute of Login Expiration Time is set to expire on July 16, 2007 at 12:00 a.m. Because the Microsoft Management Console does not allow for a value of time to be set, the default is 12:00 a.m.
Setting the value of AccountExpires to "-1" in AD will cause eDirectory to be set to: Feb 7, 2106 1:28:15 AM EST (21060207062815Z).
Several "Date" attributes in Active Directory have a data type (LDAPSyntaxes) called LargeInteger or LDAPWiki use LargeInteger Date and are also referred to as integer8