unlocking an account

[Ed Siff]

the correct syntax is:

cusrmgr -u username -m domaincontroller +s AccountLockout

Ed

 

[Bill Stewart]

the correct syntax is:

cusrmgr -u username -m domaincontroller +s AccountLockout

When I type cusrmgr without parameters, I see the following:

usage: -u UserName [-m \\MachineName] \\ default LocalMachine
....
....

So, it's on good authority that I prefixed the DC name with "\\".

Regards,

Bill

 

[Bill Stewart]

it does indeed unlock the account.

I used it all the time in both NT and 2k domains

That may be the case, but as I pointed out, it may be an unintended
side-effect that might get "fixed" in a later version.

Regards,

Bill

 

[Ritchie]

place....but...i'm sort of new to IT stuff. I locked
myself out of my computer, i have forgot the admin
password, but, i did set another username with admin

http://www.petri.co.il/forgot_administrator_password.htm

 

[Joe Richards [MVP]]

If this is in Active Directory the coolest way to do it is with unlock.exe.

It is freeware and is located on the free win32 tools page of www.joeware.net

It works with delegated users unlike NET USER and cusrmgr.

It also will tell you WHO is currently locked out. For real, not the misinformation given in ADUC.

Also you can bulk unlock users at once based on filter.

As seen on page 176 recipe 6.9 (I didn't pick that recipe number but it sure is easy to remember...) in Robbie Allen's
Active Directory Cookbook (O'Reilly). Actually if anyone is doing AD Scripting, this is the book to have next to your
machine.

joe