Windows Forum

Ask something
Discussion Locked

GPO problem!

0 helpful
12 replies

by mzpata

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Im having some problems with my home lab running
2000 server,my group policy only is effective on
the DC,and not on the member server.
What may be the problem(s)?

12 replies

by ctr2000

Try this on the member server. Start and run and type in this--secedit /refreshpolicy machine_policy--that should change it. Also it remember it is a member server and not a domain controller and what i remember is what is set on the domain is forthe domain. If this doesn't work then tell us what policies you are trying to set and maybe someone else can help out.

by mikel~t

Is the member sever part of the domain? If not, the policy will not apply to it.

Is the Group Policy you specified attached to the Domain Controllers OU, or is it attached to the Domain itself? Go to Active Directory Users and Computers, and right click on the domain name and select properties...group policy, and edit the one that is listed....make sure the policies you are looking to implement are listed, and if they are, then it's time to check the event viewer on the member server to find out why it isn't grabbing the policy....

Remember, that the group policy is applied in the following order...local, site, domain, organizational unit, so if the policy you created only applies to the Domain Controllers folder, or OU, then it won't apply to the member server since it is probably in the Computers Folder, or OU. If you apply the policy on the domain, it will spread to all of the OUs in your domain.

Hope this helps.

Mike

by timwalsh

If forcing a policy refresh as in answer 1 does not solve the problem, I would suspect that you have the policy to apply only the DC.
Under Administrative Tools, you have 3 different Security Tools: Domain Controller Security Policy, Domain Security Policy, and Local Security Policy. Make sure you use the one for the Domain.
One other possibility: because of the order in which GPOs are applied (site, domain, organizational unit (OU)), if the member server is a member of an OU and the OU has a seperate GPO applied, the OU GPO will take precedence over the domain GPO.
Hope this helps.

by geog

In a nutshell, there are two different policies that have to be set. One for the domain (which includes your member server). There is a separate policy specifically for domain controllers. So, do the same for the "domain security policy" that youdid for the "domain controller security policy."

by netadmintech

You could have a problem with the secedit.sdb file on the member server. If it is corrupt you will have to delete and re-create it.

This discussion is closed to new replies.