Re: Not all GPO settings not applied to client
From: Miha Pihler (mihap-news_at_atlantis.si)
Date: 11/27/04
- Previous message: Michael Feld: "Not all GPO settings not applied to client"
- In reply to: Michael Feld: "Not all GPO settings not applied to client"
- Next in thread: Michael Feld: "Re: Not all GPO settings not applied to client"
- Reply: Michael Feld: "Re: Not all GPO settings not applied to client"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 27 Nov 2004 17:13:09 +0100
Hi Michael,
I tested this in my lab and it works for me (I set the policy on Default
Domain Policy)
How did you set the policy? Did you set it like this
http://freeweb.siol.net/mpihler/ctrl-policy.jpg?
Additional steps that I took where:
* refresh the policy on the DC
* rebooted the client _and_ logged on (I was still required to press
CTRL+ALT+DEL). After successful logon I logged off and policy was applied (I
didn't need to press CTRL+ALT+DEL any more).
I hope this helps,
Mike
"Michael Feld" <mfeld@t-online.de> wrote in message
news:uJN$FfJ1EHA.1652@TK2MSFTNGP11.phx.gbl...
> Hello everyone,
>
> I have a problem with Group policies. I'm running a Win2K3 server in a
> test environment with an XP client. I have set up a policy on the server
> that should disable the "To log on, press CTRL+ALT+DEL" dialog on the
> client, but it doesn't work (the dialog is still displayed). I have
> searched through the internet and read several KB articles, but wasn't
> able to find the cause of this problem.
>
> I have not created any OUs yet and modified the Default Domain Policy
> directly. It appears that the settings under "Windows Settings\Security
> settings\Account policies" are successfully applied, while those under
> "Windows Settings\Security settings\Local settings" are not.
>
> Using "GPResult.exe" on the client gave me something like this (I had to
> translate it):
>
> Applied GPOs:
> - Default Domain Policy
>
> The following group policies were not applied because they have been
> filtered out:
> - Policies for local group
> Filtering: Not applied (empty)
>
>
> Using the MMC Resultset viewer snap-in on the client, I have verified that
> the setting is "enabled". In the local security policy for the client, the
> setting is "not defined". I think that's how it should be.
>
> I have found one event log error entry on the client from "SceCli",
> stating the the group policy could not be applied due to an "extended
> error". Following a KB article I enabled logging, but I really didn't get
> any clues from what it says in "$sysroot%\SECURITY\LOGS\winlogon.log":
>
> Processing group policy template gpt00000.dom.
> -------------------------------------------
> <Date>
> Use with administrator privileges has logged on.
> Parsing template C:\WINDOWS\security\templates\policies\gpt00000.dom.
> Error 1208: An extended error has occured.
> Error creating database.
> ----Config module has been initialized with one or more errors.----
> ----Config module is being deinitialized...
>
>
> Another KB article mentioned possible conflicts with admin accounts names,
> so I have renamed all local admin accounts to something that certainly
> isn't in use in the domain, but still no success.
>
> And for completeness: DNS is also correctly configured.
>
>
> Does anyone have an idea what else might be the problem here?
>
> Thanks in advance!
>
> Michael
>
- Previous message: Michael Feld: "Not all GPO settings not applied to client"
- In reply to: Michael Feld: "Not all GPO settings not applied to client"
- Next in thread: Michael Feld: "Re: Not all GPO settings not applied to client"
- Reply: Michael Feld: "Re: Not all GPO settings not applied to client"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
