Discussion Locked

Group policy not feeding down to clients

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Windows 2003 Server network (2 Domain controllers, 3 XP clients and a file server). Group policy feeds down to all the servers but not the clients. As a consequence the clients have full access. The Group policy modeling tool shows that the policy is applied correctly to a specified user group. The clients are slow at logging on though. Could this be a DNS problem?

5 replies

by p.j.hutchison

Are the clients and servers in the same OU. Have you linked policy to correct OUs? Policies will only apply to linked OU and lower ones not across OUs. Do policies apply to computers or users?

by smogmonster

Thanks, the last 3 lines helped. Guess what. It was XP's SP2 Firewall that was stopping the GPO implimentation. Dooh! Thanks for the response! Poster rated this answer.

by curlergirl

It is probably not a DNS problem unless you are having other issues with your network. There are a couple of possibilities however. Have you checked the workstation event logs to see what errors are occurring? Normally, you would see Userenv errors in your Application log on the workstations when user-level group policies are not able to be applied. These can give you a clue as to what's going on.

The other thing would be to be sure you are making your changes to the correct group policy object. The easiest, most basic way to set up group policies is to edit the Default Domain policy, which you can open by going through AD Users and Computers; right-click the domain name, go to Properties, then go to the Group Policy Tab, highlight the Default Domain Policy and click Edit. Whatever settings you make in this policy will apply to ALL users and ALL computers in the domain.

Slow logon could be caused by the computers not being able to download group policies successfully, but could be caused by other things. Again, look in your event log after logging on to see if there are any errors.

Hope this helps!

by smogmonster

Thanks, the last 3 lines helped. Guess what. It was XP's SP2 Firewall that was stopping the GPO implimentation. Dooh! Thanks for the response!

This discussion is closed to new replies.