I've noticed that around 150 computer objects in my Active Directory are displaying a `lastLogonTimestamp` value that shows a future date, about a month ahead of the current time. I'm trying to figure out how this could have happened. There don't seem to be any replication issues, and the PDC role holder is using an external NTP source for time synchronization. Also, all our domain controllers are running on virtual machines with Windows Server 2019. Any insights?
4 Answers
US date format strikes again! Seriously, there should be a strike force for these kinds of issues. I thought my sister-in-law was going to miss her citizenship hearing because of a date mix-up, but thankfully my brother caught it in time.
Sometimes the simplest explanations are overlooked—could just be a timezone issue or misconfigured settings. Just make sure everything's syncing correctly between your DCs and the NTP source.
This happened to us too! It sounds like you might be experiencing an issue with the secure time seeding feature in Windows. There was a report about it causing problems by resetting system clocks based on random data. I recommend you disable secure time seeding on your domain controllers. If they're virtual machines, double-check to ensure that time synchronization from the host is turned off in the VM settings. Also, take a look at any servers with scheduled tasks; they can mess up timestamps too if not configured properly.
I feel you! It’s like a glitch in the matrix. Sometimes you just wonder how these timestamps get so messed up! Have you checked your date format? Is it MM/dd or dd/MM? That can also cause confusion, especially when it comes to scheduled tasks.
Absolutely! We had the same issue with gMSA accounts stopping working because their "password last updated" date was being incorrectly set to the future. It took us a while to figure it out, but disabling time seeding fixed everything.