On our domain, we use AD Group Policy to push out proxy settings to the computers/users. We also have enabled "Make Proxy Settings per machine."
"Disable changing proxy settings" is NOT configured at all.
Now, I'm trying to push out a change to the proxy settings. We have added an exclusion to the sites that bypass the proxy.
Logging in as a regular user that already has a local profile created (ie... they've logged in to that workstation before) fails to update the proxy settings with the new exclusion, and they cannot access the site. If I use Group Policy Management to run the GP Results for that user on that machine, the report says that they have the new exclusion, but the local workstation doesn't appear to update properly.
However, if I log in to that workstation as an administrator, the new proxy settings are downloaded and applied to ALL users, including the old regular user who coudn't receive the update before the admin login. We have 90 workstations spread out over 200 miles, and I'm not keen on logging in to every workstation as an administrator to force the update.
Why won't the ammended proxy settings replicate to the workstations when a regular user logs in even though GP Management says that they should have the new setting? Is there a way to force this change without logging in to every workstation administratively?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Under the group policy in GPMC on the delegation tab do you have the authenticated users with Read permission?
Also you may want to try right clicking on the gpo linked to the OU and select enforce on the menu.
Finally on the client machine try running GPUPDATE /FORCE a couple times followed by a reboot.
A couple of things we had to try when we had a similar situation in our environment:
- In GPMC under Computer Configuration->Administrati
- Drill down into your sysvol folder and make sure to give Everyone read permissions on the Policies folder. We had given read permissions to Authenticated Users, but we were applying the policy to computer objects, which are not considered authenticated users.
Hi, thanks for the replies. Here is some more information:
1) Yes, had already tried gpudate /force to no avail
2) Several reboots (because you never know when a fourth reboot will fix something lol)
3) Authenticated users have read/apply permisssions in all areas
I have double-checked the Sysvol permissions, and you are correct in that the Everyone group is not there, but Auth Users is. Just as an aside, computer objects which have been authenticated in a domain environment are considered part of the Authenticated Users group.
Any other changes made to the policy update properly. It's just the proxy settings that are not getting updated.
Good question, but the answer is no. There are other GPs being applied, but I have ensured that there are no contradictory settings in the other GPs. As a secondary verification, I have run the GP Results Query tool to confirm that the computer *should* have the new setting. For some reason, the new exclusion setting is only picked up after an administrative logon/logoff.
Okay, so I ran out of time and I used RDP to connect with an administrative login to every workstation in our organization. What a pain.
So, none of the suggestions offered up actually addressed what I saw as a problem, BUT some of you did suggest some work arounds that I think would work in a pinch. I'll assign split points in what I hope is a fair manner.
Here's why I think it doesn't work:
1) In GP, we have the "make settings per machine" enabled.
2) When a regular user connects, they don't get the updated settings because they do not have enough security clearance to update a "per machine" setting (which should theoretically require admin privileges).
3) Connecting to the machine as an admin will update the central proxy settings... thus allowing all users to receive the newly updated settings.
The more I think about it, the more I think it's probably working as intended, but I can't help this feeling that there must be a better way to push these settings out. I know that XXDCmast's suggestion of creating a new GPO (downstream) with the updated settings would work, but it still feels like a jury rig.
thanks everyone for their help.
This bulletin may clarify the behaviour going on with this issue. http://technet.microsoft.c
Business Accounts
Answer for Membership
by: marques_salazarPosted on 2008-10-29 at 13:52:01ID: 22835559
You could try having them open a command prompt and type: gpupdate /force then see what happens.