GPO not applying to 1 workstation correctly

I created a Chrome GPO to apply to both users and computer settings

1) sets home button
2) opens home button url on startup


It works on most workstations.  However, on one workstation the home button, and on startup settings are not working.  

After the GPO is applied, the workstations Chrome settings show:
Show home button:
-settings are managed by administrator (greyed out) but....
- new tab page radio button is checked
- home page url radio button is not checked, but it has the correct greyed out URL

On startup:
- Open a specific page or set of pages radio button is selected, greyed out, and has the correct homepage url.    However, when a new instance of the browser is started, it goes to another older homepage url that is no longer listed.  

How do I set the GPO to force this workstation's chrome install to have the homepage url radio button checked, and go to the correct page on Startup?
tike55Asked:
Who is Participating?
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.

Andrew CeohanSys & Net AdminCommented:
Have you tried running gpupdate /force on that workstation?  Have you used the Group Policy Results Tool to see if things apply correctly?
Brian MurphySenior Information Technology ConsultantCommented:
Did you deploy Google Chrome Enterprise edition?
https://cloud.google.com/chrome-enterprise/browser/download/

Assumption: Using Central Repository for GPO | Did you make the GPO settings for Google Chrome Enterprise on a machine of the same operating system whereby GPO's are specific to OS? (Example; 2008/Windows 7 or Windows 10/Server 2016)?
https://support.google.com/chrome/a/answer/187202?hl=en 

- You can get mixed results with GPO's if the down level client does not match the OS or perhaps domain controller and this is further convoluted by service pack/build number.
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
gpos

From novice to tech pro — start learning today.