gjmcginn
Hi Kay,
Thanks for the reply.
The Windows version is Windows 7 Enterprise and happened simultaneously on a number of machines, I was giving a short intro to SuRun at the time. These are domain accounts, and we don't use any autlogon features of any kind. All accounts have passwords with a minimum of 8 characters, which must include some caps and special characters.
Kay
First: please use the latest SuRun 1.2.1.0 Beta for Windows seven. SuRun 1.2.0.9 has known incompatibilities.
[The release of SuRun 1.2.1.0 is scheduled before Christmas]
I just tried to create a scenario like yours (Win2003 server, Win7 x32 client; all standard).
I installed SuRun. After the installation was done, I pressed "cancel" (not "log off") and immediately restarted the system. My account was not locked.
I guess a system policy or HIPS causes your accounts to be locked after installing SuRun or after adding the accounts to the SuRunners group. Maybe SuRun does something that is "forbidden" for your account and the domain controller locks it. (?)
I'd like to find the cause for your locked accounts.
Is there any way that I can find out with my setup? (How do I need to adjust my virtual domain with W2k3 server to see what you got)
Do you have any event log entries specifying why the accounts got locked?
gjmcginn
I've found that the user account gets locked right after I install SuRun (1.2.0.9) and restart the computer. After unlocking the account, I'm able to log in and everything works fine. The setting for 'Store and use real user password' is set. Is this a known problem and is there any way to prevent this?
Kay
Sorry for the late answer! :blush:
SuRun usually does not cause any locking of your account.
What Windows version do you use?
Did you set a password for your account?
Do you use any preinstalled system (Lenove, HP, Dell etc) that had a preconfigured "Autologon"? (If yes, you can get it back using "control userpasswords2")