![]() Using Account Lockout Tool to Track Lockout Events To find the account lock source on all domain controllers, you can use the convenient LockoutStatus.exe tool ( Account Lockout and Management Tools ). Of course I can run rundll32.exe keymgr.dll, KRShowKeyMgr using Shell command and ask users to clear the network credentials on their own, but it's risky as they might accidentally delete something else. Open the Credential Manager (rundll32.exe keymgr.dll, KRShowKeyMgr) and remove all the saved credentials. Even when I delete the network drive by net use \\abcdefg\shared \delete, username and password is still cached, and needs to be cleared using keymgr.dll The only way to disconnect from \\abcdefg\shared is to clear the network drive credentials using keymgr.dll.Įven if user won't ever switch the accounts, I still want him to be able to disconnect from the network drive completely, and for that, clearing the network credentials is an essential step. Account2(username2, password2) has different privileges, and at the moment he wants to connect to the network drive with that account. For instance, someone is logged on \\abcdefg\shared with Account1( username1, password1). Well I am the network administrator, and I'm trying to build the program that would let users clear network drive's credentials on their own. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |