Hey guys, I just wanted to add - Using computer management, my manager and I attempted to determine the reason behind the user's continuous AD account lockouts, which struck us as peculiar. Through a thorough joint investigation, we discovered that the user had an active session on another computer with certain applications running in the foreground. To address the problem, we requested a colleague's assistance in locating these workstations and completely shutting down the specific PC causing the issue. Once this was done, I tested the login credentials to confirm if the problem persisted, and fortunately, the solution worked. Notably, the event log did not show any security-related entries, highlighting the importance of identifying the root cause before drawing conclusions. If anyone encounters a similar issue, I would strongly recommend taking the time to pinpoint the source of the problem before taking any hasty actions. Thanks, AJ
Great video and very very important information, wish to see more videos regularly related to all kinds of scenarios for Active Directory troubleshooting and Windows Server troubleshooting scenarios
In live infra there were too many users so that editing group policy will apply to other users too. What solution we can apply for a single user in an infra which does not affect the other users.
Very informative. Great job.
Excellent work! (Helping video) brother (Love you Darling )
Hey guys, I just wanted to add -
Using computer management, my manager and I attempted to determine the reason behind the user's continuous AD account lockouts, which struck us as peculiar. Through a thorough joint investigation, we discovered that the user had an active session on another computer with certain applications running in the foreground. To address the problem, we requested a colleague's assistance in locating these workstations and completely shutting down the specific PC causing the issue. Once this was done, I tested the login credentials to confirm if the problem persisted, and fortunately, the solution worked. Notably, the event log did not show any security-related entries, highlighting the importance of identifying the root cause before drawing conclusions. If anyone encounters a similar issue, I would strongly recommend taking the time to pinpoint the source of the problem before taking any hasty actions.
Thanks,
AJ
Great video and very very important information, wish to see more videos regularly related to all kinds of scenarios for Active Directory troubleshooting and Windows Server troubleshooting scenarios
Very impressive. Covered a lot of different topics and super helpful. I subscribed.
That's quality work! Subscribed.
Excellent work!
Most useful video brother. Thanks a lot
Happy to help
Awesome video bro
Today I spent 30 mins time wirthly😊
Thanks
Welcome
💯
In live infra there were too many users so that editing group policy will apply to other users too.
What solution we can apply for a single user in an infra which does not affect the other users.
Hello Sir, is it possible to know which service/executable file caused the failed event from the caller computer?
If the client address is the address of the DC with fsmo roles, what does that mean when the user's lockout is not available under event ID 4625?
Has anyone been able to use the lockoutstatus tool successfully from command line?
hi can you enter the command for this 04:00 - How to check if user accounts are locked in AD?
How can we find sources when caller computer name is empty?
I see you explain this, thank