XP Challenging registry issue

[Linflas]

I set HKU\.Default\Control Panel\Desktop\ScreenSaveActive to 0 so that the login screensaver will not activate. The setting applies and does not change until the system is rebooted at which time it goes back 1 again. This is not something that is coming from Group Policy as far as I can tell so I am stumped as to where the system is reading in the .Default hive after reboot. Anyone know the XP registry in depth enough to give me a clue where to look next?

 

[yinan]

Is there a local policy setting it?

 

[seepy83]

This is not something that is coming from Group Policy as far as I can tell

Can you be more specific about that statement? Are you the person responsible for setting group policy on the network? If you are, have you run gpresult, rsop, etc to confirm that it's not being set by a GPO?

 

[Linflas]

Nothing that I can find anywhere. I have checked the local security policy to see if there is a setting in there for it but do not see one.

 

[Linflas]

Can you be more specific about that statement? Are you the person responsible for setting group policy on the network? If you are, have you run gpresult, rsop, etc to confirm that it's not being set by a GPO?

The Group Policy is pushed from Novell Zenworks, there is no entry for that in Group Policy under XP so we actually push it out through a registry entry to disable the login screen saver. For some reason my workstation is not picking up that push which is what I am trying to figure out along with what is resetting it after a reboot. I have logged the workstation in locally after a reboot so the pushed group policy does not apply and the setting is still there so I am pretty confident it is not a GP issue.

 

[sm625]

If you disconnect your network cable before turning the machine on, then let it boot up and sit at the login screen, does it work correctly?

 

[Linflas]

If you disconnect your network cable before turning the machine on, then let it boot up and sit at the login screen, does it work correctly?

Thanks that was a great suggestion. It did not change it when I rebooted with no net connection so it is definitely something being pushed somehow. I suspect it is leftover from an earlier push but at least I now know where to look.