Discussion Locked

GPO policies not effective on OUs why?

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
hi I have a problem. I'm trying to implement policies on my OU and (frnakly speaking) on my domain and the GPO policies i'm configuring are not effective.I have two Domain Controllers(newly configured)and active directory installed.DHCP is there andcreated OUs and Users. But GPOs are not effective here. Please help me!!!!!!!!!

9 replies

by jack republic

gpo are applyed in this order :
local security policy,site gpo,domain gpo ,ou gpo.ou gpo is most effective unless
you check the "no overide" option in domain or site level gpo.
to check to who the groupe policy is applyed
go to active directoryusers and computers mmc. view scroll down menue and check the advanced features.go to gpo and select properties /security tab.you can add or remove groups.

by bentgellerich

I have a few questions:

1. First of, are your client machines running Windows 2000? (Group policy works ONLY with Windows 2000 clients)

2. Where are the GPOs you created applied?

3. Did you create them in the Group policy snap-in or did you actually link them to the OU.

4. Depending on the Policy you are trying to enforce it may take a logoff/logon.

5. Is this a Security policy?

6. Do you have a multiple DC environment.

by tellmewhy

hi.. Thanx and yes i have all my machines with windows2000. GPOs will apply on differnt OUS and basically i need to implement some policies on all the domain. No i just used the links and i don't have an independent GPO snap-in.(would u please guideme as to which is beeter). I alwaya logon/logoff the client computer. I'm implementing policies from administrative tools.I have two Domain Controllers.Helppppp!!!!!!!!!!!

by cportman

To apply GPO to Domain go into AD users and computers. Right click on your domain and go to properties. Go to group policy tab and link your GPO to the domain.

To make a customized console - go to start - run and type mmc (enter). a new console will appear - go to the top and say Console - add/remove snapin. Click add on the next screen and then find Group policy in the list.

good luck

by shanghai sam

Thanx but i did all this and still any policy is not effective.The Domain Controllers are for the time being in "mixed mode" but the policis are only to be implemented on win2000 clients.I have made customized console and linked it to domain but notworked and then to OU and still no work.

by bentgellerich

Well you seem to have an interesting problem. To answer your question regarding to which is better the snap-in or direct. Depends on your needs. Think of the snap-in as a container. You use this container to store all your GPOs until you are ready to link them. Therefore anything stored in the snap-in will still need to be linked to OUs.

95% of all settings in a GPO don?t need a logon/logoff?what you can do is at the command line issue the following command:

secedit/RefreshPolicyHere are some things to check:
1. Check for inheritance conflicts, not just site/domain/ou, but also check for multiple GPOs set at the same OU. Sometimes there is a conflict between computer and user settings. Computer settings almost always take precedence. Check for ?No Override? and ?Block Inheritance?

2. Permission Issues. Check the DACLs of the OU. Make sure they are applying the way you want. User and computer account must have both READ and APPLY GROUP POLICY permission on all GPO?s that need to be applied. Also check security group membership incase those accounts are members of one.

3. Check all GPO?s and make sure none have either the computer or User configuration disabled.

4. For multiple DCs make sure both AD and SYSVOL replication is working properly (use Replmon.exe; netdiag.exe would be handy here too. Found on the Server CD)

5. Don?t forget in a GPO Computer settings apply only to computers, and User settings to users. Therefore if you have set user settings on an OU filled with computers then nothing will apply.

Also you can enable diagnostic logging in the event viewer by doing the following in the registry:
1.Open HKEY_LOCAL_MACHINE\software\microsoft\windowsnt\currentversion
2.in the edit menu new>Key>type ?Diagnostics? press enter
3.Select Diagnostics edit>new>Dword value> type ?RunDiagnosticLoggingGlobal?>type 1 click OK

This discussion is closed to new replies.