I am configuring a notebook for one of our staff. The notebook has a
local machine account administrator (Administrators group) and one
domain user account (e.g. domainuser.DOMAIN) set up as a restricted
user on the XP notebook.

HOW do I set the domain user's screensaver timeout to be 360 seconds (6
minutes), not 30 minutes??

It is always grayed out for the restricted user.

I have changed every registry value I could find and changed every
Group Policy setting I could find, all to no avail.

I also tried giving the domain user account permissions to change the
specific registry setting that is stuck at 1800, to no avail.

I tried temporarily moving the domain user into the Administrators
group, but this was only a temporary fix.

I also tried giving Users and Restricted permissions to the particular
registry setting, but this did not "stick," I don't know why.

I am sure there is a straightforward answer and I would appreciate your
help.

Thank you, Tom

"tlyczko" <tlyczko@gmail.com> wrote in news:1133883277.714832.49050
@o13g2000cwo.googlegroups.com:

> I am configuring a notebook for one of our staff. The notebook has a
> local machine account administrator (Administrators group) and one
> domain user account (e.g. domainuser.DOMAIN) set up as a restricted
> user on the XP notebook.
>
> HOW do I set the domain user's screensaver timeout to be 360 seconds (6
> minutes), not 30 minutes??
>
> It is always grayed out for the restricted user.
>
> I have changed every registry value I could find and changed every
> Group Policy setting I could find, all to no avail.
>
> I also tried giving the domain user account permissions to change the
> specific registry setting that is stuck at 1800, to no avail.
>
> I tried temporarily moving the domain user into the Administrators
> group, but this was only a temporary fix.
>
> I also tried giving Users and Restricted permissions to the particular
> registry setting, but this did not "stick," I don't know why.
>
> I am sure there is a straightforward answer and I would appreciate your
> help.
>
> Thank you, Tom
>
>

Group Policy.

User->Admin->Control Panel->Display->Screen Saver Timeout

Install and configure this:

Microsoft Shared Computer Toolkit for Windows XP
http://www.microsoft.com/downloads/d...displaylang=en

--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/

-------------------------------------------------------------------------------------------

"tlyczko" wrote:

| I am configuring a notebook for one of our staff. The notebook has a
| local machine account administrator (Administrators group) and one
| domain user account (e.g. domainuser.DOMAIN) set up as a restricted
| user on the XP notebook.
|
| HOW do I set the domain user's screensaver timeout to be 360 seconds (6
| minutes), not 30 minutes??
|
| It is always grayed out for the restricted user.
|
| I have changed every registry value I could find and changed every
| Group Policy setting I could find, all to no avail.
|
| I also tried giving the domain user account permissions to change the
| specific registry setting that is stuck at 1800, to no avail.
|
| I tried temporarily moving the domain user into the Administrators
| group, but this was only a temporary fix.
|
| I also tried giving Users and Restricted permissions to the particular
| registry setting, but this did not "stick," I don't know why.
|
| I am sure there is a straightforward answer and I would appreciate your
| help.
|
| Thank you, Tom

I already did this, it did not work. Thank you, Tom

I know about the Shared Computer Kit, but it seems to assume one is
starting from scratch with installing XP, etc.

I am reconfiguring an XP notebook that came from Dell with no installer
CD (they're supposed to send me one but i am not hopeful it will
arrive)...so I worked on re-configuring the existing setup rather than
re-installing from scratch etc.

And I am unfortunately behind schedule with the notebook so several
more days setting everything up again is not really an option.

I just need the timeout value fixed for the one user without making her
an Admin user, restricted is better for protecting from malware, etc.

Thank you, Tom

Clarification: "I already did this, it did not work. Thank you, Tom"
means that I already tried the Group Policy suggestion from Asher_N
*before* I posted to these NGs.

I explained what I have already tried to do, but without success.

Thank you, Tom

Look at the Application Event log for that workstation. Make sure the group
policy is applied. Better yet, download the Group Policy Management snap-in
from MS. it will allow you tho see the resulting GPOs for any user on any
wkstn. I use those settings here and they always work. Something may be
either blocking the GPO or overiding it. Also try to run GPRESULTS from te
workstation.

"tlyczko" <tlyczko@gmail.com> wrote in news:1133884635.994858.302950
@z14g2000cwz.googlegroups.com:

> Clarification: "I already did this, it did not work. Thank you, Tom"
> means that I already tried the Group Policy suggestion from Asher_N
> *before* I posted to these NGs.
>
> I explained what I have already tried to do, but without success.
>
> Thank you, Tom
>
>

As a quick and dirty, make 'Everyone' a member of the local admin group,
logon as the user and set the timout. Remove 'Everyone' from the admin
group.


"tlyczko" <tlyczko@gmail.com> wrote in news:1133884526.571641.203110
@g44g2000cwa.googlegroups.com:

> I know about the Shared Computer Kit, but it seems to assume one is
> starting from scratch with installing XP, etc.
>
> I am reconfiguring an XP notebook that came from Dell with no installer
> CD (they're supposed to send me one but i am not hopeful it will
> arrive)...so I worked on re-configuring the existing setup rather than
> re-installing from scratch etc.
>
> And I am unfortunately behind schedule with the notebook so several
> more days setting everything up again is not really an option.
>
> I just need the timeout value fixed for the one user without making her
> an Admin user, restricted is better for protecting from malware, etc.
>
> Thank you, Tom
>
>

Hi Asher, thank you for responding, I will try your QED solution first
and hopefully I don't have to use your longer suggestion.

Thank you, Tom

"tlyczko" <tlyczko@gmail.com> wrote in news:1133887126.384928.252310
@g47g2000cwa.googlegroups.com:

> Hi Asher, thank you for responding, I will try your QED solution first
> and hopefully I don't have to use your longer suggestion.
>
> Thank you, Tom
>
>

You should still try to troubleshoot why the policy does not get applied. A
quick fix only removes the symptom, not the cause. You don't want to rely
on wotkarounds for every problem and every machine that you set up.