Google Chrome / Windows 10

[HereIGoAgain2601]

Hello

 

Just wondering if anyone else has had a similar issue - We are using MDT to deploy a Windows 10 image using the disk ISO of Windows 10 education 1511 from VLSC (x64). This isn't a customised / captured image.

 

When Google Chrome installs half way through the task sequence the program loads which isn't a major issue. The problem is it seems to place itself inside the default profile and each "first time login" for a new user causes the program to load. It asks which browser to set as default and the login to chrome window appears.

 

This is despite configuring all the GPOs to prevent this from happening using the Google ADMX template.

 

Any ideas? Trying to reg shot and see which keys are being placed but no luck so far!

 

Thanks

Edited July 28, 2016 by HereIGoAgain2601

[DJ-1701]

Strange, I manually install Chrome on Windows 10 Education 1511, which does run, but not on every user login. Are you using the IT Professional installer?

[Arthur]

The problem is it seems to place itself inside the default profile

Install Chrome using the "Chrome for Work" enterprise MSI as @DJ-1701 mentioned. Ideally the 64-bit version if possible.

 

Don't forgot to add NOGOOGLEUPDATEPING=1 to the command-line so that the MSI doesn't try to contact Google's servers during installation and hang. i.e.

 

msiexec /i GoogleChromeStandaloneEnterprise.msi NOGOOGLEUPDATEPING=1 /q

 

It asks which browser to set as default

You will need to set the default browser via Group Policy and an XML file...

 

www.edugeek.net/forums/windows-10/159435-set-chrome-default-browser-group-policy.html#post1362012

 

and the login to chrome window appears.

Disable that through the master_preferences file.

[HereIGoAgain2601]

Thanks for your master preferences hopefully this will stop the getting started screen. Managed to sort the auto loading issue by downloading a newer version of the MSI client.. I had an old version and this seems to have fixed it!

 

I have set the XML file for app associations but it only seems to apply on the second login - any ideas?

 

Thanks