Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Excluding Domain Controllers from a GPO

Posted on 2009-05-08
7
Medium Priority
?
442 Views
Last Modified: 2012-05-06
Hello I am trying to exclude my domain controllers from a group policy that applies to our entire domain. How can I remove the domain controllers from this GPO?
I am new at GPO management and would greatly appreciate a step by step process to remove these DC's from the policy.

The policy simply maps a network printer to all computers when you login. I noticed that when I log into my secondary DC i get an error saying the script could not run, however it runs fine on our Primary DC and workstations (printer gets mapped). Not sure why only my secondary DC is getting the error msg at logon. I would like to remove it all together from getting the GPO.

Thanks

0
Comment
Question by:FLVS_407
7 Comments
 
LVL 3

Expert Comment

by:ISWSIMBX
ID: 24338576
Set the permissions on the GPO to Deny Apply group policy to the Enterprise Domain Controllers group.
0
 
LVL 4

Expert Comment

by:TG_Tech
ID: 24338604
Create a separate Organizational Unit and place your Domain Controllers in new OU.  Exclude the GPO from from in the newly created OU.
0
 
LVL 5

Expert Comment

by:AncientFrib
ID: 24338624
If you just want to affect the one DC then change the permissions of the GPO to deny "Apply Group Policy" to the one DC.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
LVL 57

Expert Comment

by:Mike Kline
ID: 24338748
What ISWSIMBX is suggesting is using security filtering.  Here are some step by step instructions for that
http://adisfun.blogspot.com/2009/04/security-filtering-and-group-policy.html
Follow up question is your script running as a computer or user based script?  Sounds like computer but just wanted to double check.
 
 
Thanks
Mike
0
 

Author Comment

by:FLVS_407
ID: 24339158
its running as a user script.

Here is what I tried.
In A.D. I created a new group called "GPO disable"
I added my 2ndary domain controller to that group.


then i opened up the group policy that has the script in group policy object editor and right clicked on the domain selected properties and clicked on the security tab.
I then added the new OU I created in AD and selected DENY for the "apply group policy" permission
I then did a gpupdate /force and tried logging into the server in question, still got the script error message..

i have noticed some other servers too are getting the error but not all servers..
0
 
LVL 57

Accepted Solution

by:
Mike Kline earned 2000 total points
ID: 24339269
You would have to reboot the DC in order to update the group membership/token but since this is a user script excluding the computer doesn't do much for you.
If you added your account and set the deny ACE then you should not get the script/GPO.
Thansk
Mike
0
 

Author Comment

by:FLVS_407
ID: 24339642
Turns out the error was because some of my servers didn't have the print spooler services running so it couldn't contact the network printer. Turned them on and no more errors!
Thanks
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
Transferring FSMO roles is done when an admin wants to split roles between certain Domain Controllers or the Domain Controller holding the Roles has been forcefully demoted using dcpromo / forceremoval
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

773 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question