• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 433
  • Last Modified:

Problem applying a custom Group Policy

I am having issues with a particular group policy on Server 2008 R2. I
 am logging on to a 2008 Terminal server. The terminal server is in it's own OU, with a loopback GPO and 2 custom GPOs in it. At the user OU level I have a custom user config GPO.
If I have my loopback GPO enabled, my custom user config GPO doesn't apply. With the loopback GPO present, if I go to do a gpresult, the custom GPO is not mentioned at all. It's not in the applied GPO section or the filtered ones.
With the loopback GPO disabled, I just get the custom user GPO (at the user level), and not the other 2 GPOs I have at the Terminal Server Ou level.

0
lineonecorp
Asked:
lineonecorp
  • 3
  • 2
1 Solution
 
lineonecorpAuthor Commented:
It turned out to be the loopback setting.
It was set to replace. I changed to merge, and it works now.
0
 
EmilenethCommented:
Taken directly from:
http://support.microsoft.com/?scid=kb%3Ben-us%3B231287&x=14&y=5

The lookback will replace entirely your user GP if it's on Replace mode, that's why it wouldnt be visible at a gpresult query, I think you want to use the Merge mode
0
 
lineonecorpAuthor Commented:
Is this a new twist to 2008 as we have a template for TS setups that we have followed in 2000 and 2003 and we used the Replace option for Loopback Processing with them? That is what I usually find as recommended for TS setups in pretty well everything I read.  For instance in this link I just came across they use the 'Replace' function.  http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_24579654.html

Is it a matter that it can work with the Replace but we have to change something else?
0
 
EmilenethCommented:
I've read the other Ex.Ex. question.

The behaviour hasn't changed, according to MS KB papers.
I have my concerns towards updating versions of windows server, things may not go right all the time.

Elitematrix user said he just delted and recreated the policies and every thing worked as usual.

What I dont get it, why it was working that way on previous versions, as for this new version seems to be logical, maybe there was a sutile change, like some default value change. Something that may be missed during the upgrade.
0
 
lineonecorpAuthor Commented:
Thanks for the help. We'll work with the merge function if that's what it takes.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now