Just a reminder, if you are reading the Spark!, Spice it

Today is International Sign Languages Awareness Day. Welcome to your Friday Spark! I hope it brightens your day, enlightens you and educates! And. Spark! Pro series – 23rd September 2022 Spiceworks Originals.We noticed a 3rd user's laptop (same model) was doing the same thing, so running psexec on that computer fixed the lockouts, as well. (Perhaps this was even in the Credential Manager, just overlooked.) I can't remember exactly what item under the 'Stored User Names and Passwords' was doing the lockout, but it definitely had my username on it! Removing it fixed the problem immediately. While this doesn't normally lock my account out, now that people are working from home, like User2, when they start a VPN session, it locks out my account due to that mapped drive being 'poked' by Word. That drive was mapped under my credentials - I believe a mistake I made configuring the image for that laptop model.

We used the psexec tool from the 'account lockout troubleshooting guide' that Ryan (Netwrix) linked to.Īlso as Ryan mentioned, it seems like Word was possibly checking on 'Recent documents' that were on a mapped drive. We've tried running procmon64 to filter for my username on any processes on his computer and it always comes back with no results. After a reboot, we started installing Office again and it immediately locked out my account during the install. It kept locking out, so we've uninstalled Office from his computer.

Is there a quick fix for this bizarre occurrence? We've de-registered Office from his computer and re-registered. We noticed that if they close out off all Office products, my account no longer locks out. After looking at AD logs, it turns out it's locking out from User2's computer. After that, my account started getting locked out every 52 minutes. I recently changed my network password (it's the same email we use in Azure AD for Office 365). I was in charge of the deployment and I had one of my fellow IT employees (User2) install one of the first instances of Office 365 on his computer. We migrated from Office 2013 to 365 ProPlus a few months ago.

Procmon64