none
Windows SteadyState 2.5 logging accounts off for no reason RRS feed

  • Question

  • We've been using SteadyState 2.0 at work with no issues.  We upgraded some of our boxes with various updates, including SteadyState 2.5, some using the older Microsoft Shared Computer Toolkit.  Pcs are running Windows XP with all updates including Service Pack 3 applied.   The problem that we are trying to narrow down is an issue with the SteadyState mysteriously logging out the accounts from time to time.  The pcs are usually logged in to a limited profile that is locked down with the Steady State software, however on occasion for no apparent reason some, not ALL, of the pcs will log out on their own.  Settings to enable this are not selected, we leave them logged into the same profile all day.


    The Weez
    Monday, February 9, 2009 3:59 PM

Answers

  •  

    Hi Weezul, this issue can be caused by either Windows SteadyState settings or Windows XP system issue. I suggest you first try the following steps to troubleshoot the issue:

     

    1.       Disable all restrictions in Windows SteadyState and see if this happens again.

    2.       If this still occurs, let's temporarily remove SteadyState and check the result.

    3.       If the issue still occurs, you can try Clean Boot:

     

    1)      Click Start, type "MSCONFIG" (without the quotations) in Run and Press "Enter" to start the System Configuration Utility.

     

    2)      Note: Please click Continue if the "User Account Control" window pops up.

     

    3)      Click the "Services" tab, check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray).

    4)      Click the "Startup" tab, click "Disable All" and click "OK".

    5)      Restart the computer and test the issue.

     

    Note: Clean Boot is a troubleshooting step. If some programs have been disabled, we can re-enable them later. If you see the System Configuration Utility, check the box of "Don't show this message" and then click "OK".

     

    Please test this issue in the Clean Boot environment. If the issue disappears, we can use a 50/50 approach to quickly narrow down which entry is causing the issue.

     

    Hope this helps!


    Sean Zhu - MSFT
    Thursday, February 12, 2009 2:55 AM
    Moderator