Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

"lastLogonTimestamp" is not updated after you perform an LDAP simple bind operation in Windows Server 2016


View products that this article applies to.

Symptoms

After you perform a Lightweight Directory Access Protocol (LDAP) simple bind operation against a Windows Server 2016-based domain controller, the lastLogonTimestamp attribute on Active Directory user accounts is not updated.

↑ Back to the top


Resolution

This problem is fixed in the following update for Windows 10 and Windows Server 2016:

September 20, 2018—KB4457127 (OS Build 14393.2517)

↑ Back to the top


Keywords: lastLogonTimestamp not update

↑ Back to the top

Article Info
Article ID : 4131507
Revision : 8
Created on : 10/10/2018
Published on : 10/10/2018
Exists online : False
Views : 680