RE: Screensaver policy on some PCs
From: Denis Wong _at_ Hong Kong (_at_)
Date: 11/03/04
- Next message: Denis Wong _at_ Hong Kong: "RE: I have some workstations that don't seem to get computer assigned"
- Previous message: Peter: "ADM Template Policy (inf) files - Delete a Registry Key"
- In reply to: Steve Stormont: "Screensaver policy on some PCs"
- Next in thread: Steve Stormont: "Re: Screensaver policy on some PCs"
- Reply: Steve Stormont: "Re: Screensaver policy on some PCs"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 2 Nov 2004 19:25:01 -0800
Simply speaking, you should link the GPO to an OU, and PUT ALL YOUR USER
OBJECTS IN THAT OU. And make sure your users can read and apply the GPO.
HTH.
BR,
Denis
"Steve Stormont" wrote:
> I first tried to setup a default screensaver policy in the "Default
> Domain Policy" but it was only sent out to some PCs. I then went ahead and
> created a new GPO called "Screensaver Policy". In that policy, I have
> changed the following settings:
>
> User Configuration -> Administrative Templates -> Control Panel ->
> Display
>
> Hide Screen Saver tab = Enabled
> Activate Screen saver = Enabled
> Screen saver executable name = Enabled (logon.scr)
> Password protect the screen saver = Enabled
> Screen Saver Timeout = Enabled (1800 seconds)
>
> Security on the policy only has a Universal Security Group which each
> user is a member of and the group has "read" and "apply group policy"
> permission set. ( I can use a security group for this, correct? I can't
> only use an OU?)
>
> The settings are being used on some PCs, but not others. I have tried
> to run secedit /refreshpolicy user_policy /enforce and then waited ten
> minutes. I then ran gpresult with the /s switch and got this:
>
> The user received "Registry" settings from these GPOs:
>
> Screensaver Policy
> Revision Number: 5 (Active Directory) 0 (Sysvol)
> Unique Name: {removed}
> Domain Name: omni.imsweb.com
> Linked to: Domain (DC=omni,DC=imsweb,DC=com)
>
> But next it says:
>
> The following settings were applied from: Screensaver Policy
>
> And it doesn't list the actual keys like it does on other PCs.
>
> I last made changes 1 1/2 days ago, so any changes should have
> propogated by now (we have the default group policy refresh time set).
>
> Possibly related, while looking at the results from gpresults, it shows
> a old logon script specified and there are some old GPO Names that we don't
> use anymore in the Application Management section. Where are they coming
> from? They don't show up in the Current group Policy Object links for out
> domain.
>
> Steve
>
>
>
- Next message: Denis Wong _at_ Hong Kong: "RE: I have some workstations that don't seem to get computer assigned"
- Previous message: Peter: "ADM Template Policy (inf) files - Delete a Registry Key"
- In reply to: Steve Stormont: "Screensaver policy on some PCs"
- Next in thread: Steve Stormont: "Re: Screensaver policy on some PCs"
- Reply: Steve Stormont: "Re: Screensaver policy on some PCs"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|