Link to home
Start Free TrialLog in
Avatar of DCapen
DCapen

asked on

Hibernate/Standby Settings Changing Randomly

There are several XP Pro workstations in our domain that are changing the hibernate and/or standby settings on their own. When I config a new workstation I turn off hibernation and set the option for the power button to shutdown. My first thought was that somehowa Group Policy had been created that was causing this. A little research turned up nothing in Group Policy that would cause it. Since it started shortly after "upgrading" to SAV 10.1.6, my next thought was that SAV was causing it. I haven't been able to find any information in Symantec's KB and am not about to sit on hold for a couple hours waiting for someone who may (or more likely may not) be able to shed some light on this. Has anyone else heard or experienced the same problem? If so, is there a solution?

Any help would be greatly appreciated.
Avatar of Alex
Alex
Flag of Greece image

Please check and tell me which one of Power Schemes did you set?
Avatar of DCapen
DCapen

ASKER

Home/Office Desk

Avatar of DCapen

ASKER

Turn Off Monitor-Never
Turn Off HDD-Never
Syatem Standby-Never
Press Power Button-Shutdown
Enable Hibernation-box unchecked

Settings applied
ASKER CERTIFIED SOLUTION
Avatar of Alex
Alex
Flag of Greece image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of DCapen

ASKER

The settings in my last post are manually configured on every new workstation and checked upon deployment. I need to know what is causing the settings to change to the following:

Turn Off Monitor-Never
Turn Off HDD-Never
System Standby-Never
Press Power Button-STANDBY <<was configured for Shutdown
Enable Hibernation-box checked <<was configured with box unchecked

This is causing a real problem, especially hibernation enabling itself. The application we use to interface with our core processor crashes if the workstation goes into hibernation. We then have to call them and have the user's account reset and create a new password. That's at least a half hour of down time on that workstation.