Support Request: Windows 7 Power Saving Disables Auto Login

Reproduction

To reproduce the issue (on a laptop) wait for the battery to run out of capacity. When the system is restarted the user may be prompted to press a function key to continue because the battery is critically low. If the user continues then the machine will not auto login to the SiteKiosk account but will be presented with the locked-down CTRL-ALT-DEL screen.

This issue has primarily been seen on a Dell Latitude E5540

Description

A batch of recently built Windows 7 machines running SiteKiosk 7 frequently return to the locked-down CTRL-ALT-DEL screen rather than automatically logging into the sitekiosk account. It would seem that the power saving features are causing the machine to shut down in a non-graceful manner which means that when it is restarted it cannot auto-login. Once the breakout key sequence is used (and the sitekiosk credentials are entered) the machine will then auto-login as expected. However we cannot give out this password to local staff for security reasons. I notice that there is an article in your knowledge base that mentions power saving settings for Windows 7, but these and many more have already been configured to no avail.

Answer: (3)

Re: Windows 7 Power Saving Disables Auto Login 7/1/2014 4:41 PM
The start settings do not reset, they are written to the Windows registry. Make sure you did not activate the option "On resume, dispay logon screen": http://www.pcworld.com/article/2048266/control-how-windows-locks-down-and-saves-power-when-youre-not-using-it.html.
Re: Windows 7 Power Saving Disables Auto Login 7/2/2014 10:56 AM
I have checked and that option is not selected. Do you have any other suggestions?
Re: Windows 7 Power Saving Disables Auto Login 7/2/2014 11:41 AM
Be aware that this setting is user dependent. Make sure to check it for the Windows user you are running SiteKiosk with. If it is the Restricted SiteKiosk User, have a look here: http://www.provisio.com/de-DE/CustomerSupportCenter/ArticleDetails.aspx?ArticleID=5826

Other than that, it might be a Group Policy setting or another application forcing that behaviour.
My Account
Login
Language (Tickets):