Re: Why doesn't Group Policy work if I put a local group in the affected OU instead of the actual user account?
- From: "Claus Greck" <c.greck[spamfree]@qitcon.de>
- Date: Tue, 27 Jan 2009 21:46:02 +0100
Group Policies only apply to USER ACCOUNTS and COMPUTER ACCOUNTS ! They don't apply to Group Accounts!
So your experinece was to be expected ;)
You can only filter GPO scope through its DACL to a group (or any individual account).
Claus Greck
"CS" <masssheltie@xxxxxxxxxxx> schrieb im Newsbeitrag news:mWIfl.39265$aG1.22644@xxxxxxxxxxxxxxx
Windows 2003 Server. AD domain. Created an OU so that I can apply a Group Policy to a collection of users. As per Msoft instructions, I created a Local Group, and put that local group inside the OU. Created a Global Group, added users to the Global Group, and then added the Global Group to this local group. I then created a Group Policy - User Config, and set up the restrictions. I applied the GP to the OU, and did a GPUPDATE / FORCE.
The result is that this GP doesn't affect the pc where the user above logs in. If I take the local group out of the OU, and just put the individual user account into the OU (instead of the local group), the GP works fine when that user logs into a PC.
Any ideas why this won't work when I use groups to add users to the OU, and thus to the Global Policy world?
Thanks
CS
.
- References:
- Prev by Date: Why doesn't Group Policy work if I put a local group in the affected OU instead of the actual user account?
- Next by Date: Re: Why doesn't Group Policy work if I put a local group in the affected OU instead of the actual user account?
- Previous by thread: Why doesn't Group Policy work if I put a local group in the affected OU instead of the actual user account?
- Next by thread: Re: Why doesn't Group Policy work if I put a local group in the affected OU instead of the actual user account?
- Index(es):
Relevant Pages
|