dkitts
asked on
AD Group Policies not being applied to computers
I have just completed the migration of my NT4 domain to Windows2003/Active Directory.
I have created new logical OU's that make sense to our company and moved all computers, users and groups to appropriate OU structures.
My Group Policies are not working on any new OU that I create.
If I right click on mydomain.com, and go to the policies tab, I can edit the policies and those get pushed down fine. It only works at this level.
Here is what I have tried...
Made a new OU on the root of mydomain.com called TESTOU
I moved the computer that I want to push policies to into this OU.
I then created a group in this OU called MYPOLICYGROUP
Then I created a new policy and applied that policy to the group "MYPOLICYGROUP"
Edit the policy and took away the start/run.
Replicated Active Directory. (no errors)
Ran gpupdate /force from the client.
Rebooted the client.
I "DO NOT" get the new policy....ugh!
I then ran GPRESULT, it never shows the policy being applied or denied for any reason.
I can get this to work only if I put the user and computer into the same OU.
For many reasons this is not a viable solution.
Does anyone have any ideas why this may be doing this?
Thanks
DK
I have created new logical OU's that make sense to our company and moved all computers, users and groups to appropriate OU structures.
My Group Policies are not working on any new OU that I create.
If I right click on mydomain.com, and go to the policies tab, I can edit the policies and those get pushed down fine. It only works at this level.
Here is what I have tried...
Made a new OU on the root of mydomain.com called TESTOU
I moved the computer that I want to push policies to into this OU.
I then created a group in this OU called MYPOLICYGROUP
Then I created a new policy and applied that policy to the group "MYPOLICYGROUP"
Edit the policy and took away the start/run.
Replicated Active Directory. (no errors)
Ran gpupdate /force from the client.
Rebooted the client.
I "DO NOT" get the new policy....ugh!
I then ran GPRESULT, it never shows the policy being applied or denied for any reason.
I can get this to work only if I put the user and computer into the same OU.
For many reasons this is not a viable solution.
Does anyone have any ideas why this may be doing this?
Thanks
DK
Last Comment
Also, since you are using W2K3, you might consider dnloading GPMC and use it for seeing the RSOP for your network clients.. a very cool interface, about time MS put someting like this together..
Enterprise Management with the Group Policy Management Console
http://www.microsoft.com/windowsserver2003/gpmc/default.mspx
Enterprise Management with the Group Policy Management Console
http://www.microsoft.com/windowsserver2003/gpmc/default.mspx
ASKER
The computers have been rebooted a few times.
GPO's are set to READ AND APPLY for every group.
Ive used the GPMC and did not see any problems with the RSOP. The RSOP shows what should happen. But its not happening :(
GPO's are set to READ AND APPLY for every group.
Ive used the GPMC and did not see any problems with the RSOP. The RSOP shows what should happen. But its not happening :(
Darn.. Was hoping this would be easy.. lol, eh..? Got to go to a short meeting, but will be back soon to try something else..
FE
FE
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
You cannot apply Group Policy to groups - only to User and Computer objects.
If you are applying Computer settings, the Computer account must be in the OU.
If you are applying User settings, the User account must be in the OU.
If you are applying both....you get the idea.
If you are applying Computer settings, the Computer account must be in the OU.
If you are applying User settings, the User account must be in the OU.
If you are applying both....you get the idea.
hmm.. I completely missed that in the question.. Absolutely.. no groups and your users must either be in the OU, or the OU that you created that you placed them into must be assigned that GPO...
Or you can use loopback group policy processing to apply to the user the policies linked at the computer's OU...see above link and post
ASKER
I am trying to apply a Policy to an OU.
Shouldn't I be able to have an OU that contains users then an OU that contains the workstations and then a 3rd OU that contains terminal servers. Then manage different policies on the OU's?? Say a user from my user OU signs in to a terminal server that is in a terminal server OU... I would like a policy that tightens down users on this termserv OU but..... if that same user from the "users" OU signs in to his workstation that is in a different OU he/she would get a totally different policy?
To me it is impossible then to have different OU's????
Every server or workstation needs to belong in the same out as the users ????
Shouldn't I be able to have an OU that contains users then an OU that contains the workstations and then a 3rd OU that contains terminal servers. Then manage different policies on the OU's?? Say a user from my user OU signs in to a terminal server that is in a terminal server OU... I would like a policy that tightens down users on this termserv OU but..... if that same user from the "users" OU signs in to his workstation that is in a different OU he/she would get a totally different policy?
To me it is impossible then to have different OU's????
Every server or workstation needs to belong in the same out as the users ????
you can do what you want to do. When you have a policy that you want to apply to users when they log on to a specific machine, use loopback processing.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;231287
http://support.microsoft.com/default.aspx?scid=kb;EN-US;231287
Terminal Server OU should have loopback enabled.
Computer settings affect the computer in the OU. User settings are applied from the OU the User account exists.
You can either filter, loopback or block policies you don't want to apply in different scenarios.
Nobody said this was easy! This is why it's supposed to take several months to design AD - to avoid any bad design choices.
Computer settings affect the computer in the OU. User settings are applied from the OU the User account exists.
You can either filter, loopback or block policies you don't want to apply in different scenarios.
Nobody said this was easy! This is why it's supposed to take several months to design AD - to avoid any bad design choices.
yea.. I've been studying this stuff for a couple of years and getting a grip on it is just not that easy...
ASKER
Thank You everyone for your help.
The link that spareticus first sent was the fix. He gets the points :)
The link that spareticus first sent was the fix. He gets the points :)
ASKER
FYI,
I have another problem that I am working on too... Anyone want to give this a shot...
https://www.experts-exchange.com/questions/20924830/How-can-I-remove-a-Retired-Direct-Replication-Partner-from-the-Active-Directory-Schema.html
I have another problem that I am working on too... Anyone want to give this a shot...
https://www.experts-exchange.com/questions/20924830/How-can-I-remove-a-Retired-Direct-Replication-Partner-from-the-Active-Directory-Schema.html
glad that helped
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
Also, make sure that the GPO's security permissions are set correctly.. The READ and Apply must be set...
FE