Group policy is applied to Win 10 computer, but the Win 10 computers settings do not change

Group policy is applied to Win 10 computer, but the Win 10 computers settings do not change.  Specifically, we are testing a new WSUS server on the network.  We're using a Windows 10 machine for testing.  We've verified by using the Group Policy Wizard that the machine had the correct GPO applied, which has all the new WSUS server settings in it.  After confirming the GPO was "applied" to the test machine, when we pull up the GPEDIT on the Win 10 machine, we see that NONE of the GPO settings were actually applied - everything was default and not enabled.  What causes a machine to "ignore" GPO settings, when that GPO was successfully applied??  The AD server is 2008R2.

Thanks for your help
Damian GardnerIT AdminAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Raj-GTSystems EngineerCommented:
You will not be able to see or edit the policies applied to a machine using gpedit. GPedit is purely to edit the local machine policy and not the domain policy. If you want to see domain policies applied to your Win10 desktop then you have to run "gpreuslt.exe /H report.htm" from the Win 10 desktop and check the resulting report.htm file.
brtl1000sCommented:
From Administrative command prompt: Run gpupdate /force... see if there are any error messages

Run gpresult /R

See how many gpo's are being applied, one might be blocking the required result
DonNetwork AdministratorCommented:
You can also from this test machine run rsop.msc

Or from a command prompt

REG QUERY "HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate"  /s

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Damian GardnerIT AdminAuthor Commented:
Raj-GT - thanks for the help.  I created a results files, and its pretty difficult to read - its in HTML and IE doesn't seem to format it. so not much help unfortunately.  

BRT - thanks for your suggestion.  I had done the gpupdate before, but ran it again to double-check for errors, and there are none.  I assume that if any GPOs were being blocked, they would show up under the "filtered out" section.  the only one filtered out that I see, is the "local group policy" because it is empty.  

Donald - thanks for your suggestion - I ran the RSOP.msc on the test machine, and I do see that it seems to have taken the changes from my test GPO.  I was thinking that it hadn't because I was incorrectly checking the GPEDIT screen.   So - now I need to figure out why the test machine is not being seen by the WSUS server, since it looks likt he client actually does have the correct WSUS server specified.


Thanks everyone.
Raj-GTSystems EngineerCommented:
Running gpresult is the official way to validate group policy. The file generated should open fine on IE or any other browser, check for any prompts from the browser as you open the file. It needs javascript enabled, and most modern browsers disable javascript when you open a local file.
DonNetwork AdministratorCommented:
"So - now I need to figure out why the test machine is not being seen by the WSUS "

Are you using client side targeting in the WSUS console ??

Use the Solarwinds WSUS tool to find out what may be the problem

https://www.solarwinds.com/free-tools/diagnostic-tool-for-the-wsus-agent
Damian GardnerIT AdminAuthor Commented:
thanks for everyone's help.  As it turned out, my client was taking the correct changes thru the GPO, but the server firewall was blocking the WSUS communication.  Everything is working good now.  thanks again
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.