Discussion Locked

Group policies

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
There are 15 users/computers in our accounting department. We have created a group policy for their department. The policy changes the background to a company logo background, and takes away their ability to change it. There are 3 computers that havent applied the policy. All computers in the department are Win2000. The policy was created and applied 1 week ago. I have checked to make sure that the 3 pc's are logging into the correct domain... Anyone have any ideas on what I should checknext? Any suggestions would be appreciated.

15 replies

by dearshezi

well, Might be the users of those computers are the member of that group on which Group policy is not applying . Check it out from the Properties>seurity tab of the group policy. It may help you. If it doesnot work then delete their local profile and profile on the domain controller. I hope it will work. best luck

by cg it

humm as answer #1 said, sounds like those 3 users who log on are not part of the OU group in which you applied the new group policy.

by cg it

note: group policy applies to the user's log on profile stored in documents & settings, .

by sharon

I had a computer that I was working on in my office, which I logged on as one of the members of the acctng group whose policy wasnt working, and it worked on the test pc. I'm thinking that there has to be something different about the 3 computers that arent applying the policy..but, I cant figure out what it is...

by cul8rm8e

change the properties of the LOGO you created(the displa settings of the machines in question may not be capable of displaying the background .bmp at the settings set!

im certain this is whats causing this.

by itnetman

This may be obvious, but have you checked on replication if applicable. These users may not be getting the correct policies if you have more than one server acting as log-on server. Hope this helps

by ewgny

DNS
99% of al AD problems stem from a DNS problem.
And DNS shoud always be checked first
Although the 3 workstations seem to be logging in correctly kerberos authentication is probably failing and they are falling back to ntlm authentication

ipconfig /all on the workstations not getting group policy. If no DNS servers are listed
clean out all DHCP and DNS entries for the PC/NIC
of the three PC's

restart

by ewgny

You can also stick in a new NIC card to confirm my above theory. Group policy should then work since it now has a new Mac address

by tlath1972

i would have one of the other users not from the 3, try logging on to one of the 3 computer. This will see if its a computer issue or user issue. If its a user issue check to make sure the 3 users aren't part of another user group that would over ride that policy. the policy are applied in the following order local, site, domain, ou, sub out, user, computer.

by sharon

Well, whatever it was, it fixed itself. It took about a month, but the group policy finally started working for the last 3 people in the group. It wasnt a replication issue, because we've set up group policies for other groups with no problem. Thanks for all of the comments anyways!

This discussion is closed to new replies.