Re: GPO is FFiltered (EMPTY) WHY?????
- From: "Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 4 Oct 2005 22:29:10 -0500
Make sure that the user accounts that you want the logon script to apply to
are also in the OU since it is part of user configuration. --- Steve
"dave Admin" <dmackler@xxxxxxxxxxxxx> wrote in message
news:%23pOg$TEyFHA.1132@xxxxxxxxxxxxxxxxxxxxxxx
>
> We use Server2003, SP1. Downloaded and instaled the GPO MAnager.
> Practiced a logon script on a test server and workstation and it worked
> fine. Does not work in Production. When I do a gpresult on a workstation
> in the OU is is linked to only the Default Domain Policy is applied. The
> logon GPO is filtered with the caveat "Empty". This implies there is
> nothing set in the GPO; but there is, the logon script is set. The script
> works, we can execute it directly and the drive mappings properly appear
> and the users have read rights to the folder and vbs script.
>
> What would cause the script to appear empty, be filtered or simply not be
> applied to the OU it is linked to, it is enabled, and I set Enforced also
> daveM
>
>
.
- References:
- GPO is FFiltered (EMPTY) WHY?????
- From: dave Admin
- GPO is FFiltered (EMPTY) WHY?????
- Prev by Date: Re: IE Advanced/Security settings
- Next by Date: Re: Specify local machine accounts through domain policy?
- Previous by thread: GPO is FFiltered (EMPTY) WHY?????
- Next by thread: Re: Hide Hardware Tab and Advanced Tab
- Index(es):
Relevant Pages
|
