He knew the service account, svc_backup_acc , had been working fine for months. But after a rushed security patch earlier that day, something had broken. He needed to check if the account was locked, disabled, or had its permissions scrambled.
He started keeping a sticky note on his monitor: dsa.msc Bonus: Run as different user → runas /user:admin dsa.msc That night, Marcus saved three hours of troubleshooting not with a script or a complex tool, but with a four-letter command that put him exactly where he needed to be. Key takeaway from the story: The command dsa.msc launches Active Directory Users and Computers from the Run dialog, Command Prompt, or PowerShell. It's the fastest way to manage user accounts, groups, computers, and organizational units in an Active Directory domain.
But then his phone buzzed. Another alert. The HR-Share drive was inaccessible. Users were reporting "access denied" on a different folder. This time, it wasn't a locked account—it was a group membership issue. active directory users and computers command
He typed:
He opened the dialog (Windows + R). His fingers hovered over the keyboard. He couldn't waste time clicking through menus. He needed the command. He knew the service account, svc_backup_acc , had
Right-click. . The Account tab told him everything. A red X next to "Account is locked out" .
Instead of hunting through individual user objects, he used another command-line trick from the same console. He selected the HR department OU, clicked Find , and searched for a user, jdiaz . In her Member Of tab, he saw the problem: her primary group, HR-RW , was missing. A sync error had dropped her from the group. He started keeping a sticky note on his monitor: dsa
He added her back, told her to log off and on again, and the ticket closed.
