Google Chrome : Welcome Screen

[protocol]

Has anyone managed to get this sorted for local user profiles? We don't use roaming or mandatory. I can get a modified master_preferences copied to the Chrome application folder on the local machine but when a user logs on Chrome creates the following directory C:\Users\\AppData\Local\Google\Chrome\User Data\Default\ and in there is a Preferences file which isn't keeping the settings from the master_preferences file. When they open Chrome they are getting their homepage tab and a 'Welcome to Chrome tab'.

 

The Chrome documentation states:

 

When users launch Chrome for the first time, the user’s preference file is copied from the master_preferences file.

 

I've disabled the 'Enable showing the welcome page on the first browser launch following OS upgrade' disabled at both Computer and User level. Can't see any other policies that would be linked to welcome tab. I'm testing this by deleting the profile on our test PC. Once I know I can get rid of the welcome tab, I'll then need a way of sorting it for users who already have a profile on the local machine.

Edited September 29, 2017 by protocol

[ADMaster]

I answer this in post #10

http://www.edugeek.net/forums/enterprise-software/178319-google-chrome-welcome-screen.html#post1572171

 

Copy the code I give into the preferences file and create a first run file.

The last I tested this was 60 on 1703.

 

 

Has anyone managed to get this sorted for local user profiles? We don't use roaming or mandatory. I can get a modified master_preferences copied to the Chrome application folder on the local machine but when a user logs on Chrome creates the following directory C:\Users\\AppData\Local\Google\Chrome\User Data\Default\ and in there is a Preferences file which isn't keeping the settings from the master_preferences file. When they open Chrome they are getting their homepage tab and a 'Welcome to Chrome tab'.

 

The Chrome documentation states:

 

 

 

I've disabled the 'Enable showing the welcome page on the first browser launch following OS upgrade' disabled at both Computer and User level. Can't see any other policies that would be linked to welcome tab. I'm testing this by deleting the profile on our test PC. Once I know I can get rid of the welcome tab, I'll then need a way of sorting it for users who already have a profile on the local machine.

[protocol]

I answer this in post #10

http://www.edugeek.net/forums/enterprise-software/178319-google-chrome-welcome-screen.html#post1572171

 

Copy the code I give into the preferences file and create a first run file.

The last I tested this was 60 on 1703.

 

I saw that post but wasn't sure if it would be a fix in my scenario as computers here don't have a C:\Users\Default\AppData\Local\Google\Chrome\User Data\Default\ folder to copy the preferences file into. Does it just need created?

 

I saw you mention a 'first run' file in post #4. What content does the file have or it is just blank?

 

Edit: Found the first run file you mentioned in C:\Users\\AppData\Local\Google\Chrome\User Data but again these Chrome files aren't created until after Chrome is first launched.

Edited October 2, 2017 by protocol

[ADMaster]

The copy-item command in my script will create the directory.

The first run file code is posted around here somewhere I think in another thread. but it will create the directory too. Here it is again.

 

New-Item -ItemType file -Path "$OSDISK\Users\Default\AppData\Local\Google\Chrome\User Data\First Run" -Force

 

My script puts the files in the default users directory so any new user will get the settings. These are part of my OSD.

If you are deploying to existing users you will need to loop through their profiles and put the files in the correct location.

Edited October 2, 2017 by ADMaster
spelling

[protocol]

So you're installing it as an application in SCCM but as an install script? What script language is your script in? Struggling to get some of the commands to work when I run it manually.

 

Thanks for your help so far.

[Arthur]

What script language is the script in?

It's PowerShell.

Edited October 3, 2017 by Arthur

[ADMaster]

It's PowerShell.

 

What he said.

[davephs]

After exhausting all the above options, I managed to get rid of the welcome page on Win 10 - By enabling the "Disable synchronization of data with Google" gpo. This is what the welcome page was effectively trying to get a user to do, by signing in...

[DavR]

After exhausting all the above options, I managed to get rid of the welcome page on Win 10 - By enabling the "Disable synchronization of data with Google" gpo. This is what the welcome page was effectively trying to get a user to do, by signing in...

 

Interesting - I've got that setting in place, but we still get the Win 10 welcome page

 

Is there any chance you could share your policy settings to see if it's a magic combination? What, for instance, are your restrictions around Chrome sign-in?

[davephs]

Oh I have doubts now, maybe its not fixed? Although I have tried on various PC's.

 

Also what we have in place is a script which completely wipes the AppData\Local\Google\Chrome\User Data\Default Folder at logoff so chrome needs to recreate this next time its used. Maybe this is wiping out other settings that are saved somewhere? Then in terms of user bookmarks these are copied back at login. - In my experience this tends to keep chrome in working order, and cleans out all the rubbish... Try manually deleting this folder on a pc and trying again ? There are no other settings in the GPO orientated around logins, just the usual [TABLE=class: info3]

[TR]

[TD]showing the welcome page on the first browser launch following OS upgrade set as disabled for the welcome page.[/TD]

[TD][/TD]

[/TR]

[/TABLE]

[DavR]

Yeah, I've got that one set, plus the various import at first run settings, but can't recreate what you've done sadly!

 

I've been deleting the AppData\Local\Google\Chrome\User Data each time in my testing to create a first run experience. FYI, deleting the AppData\Local\Google\Chrome\User Data\Default folder as your script does will not recreate the first run experience as this is determined by files in the route of AppData\Local\Google\Chrome\User Data. This may be giving you false positives.

 

When you copy in bookmarks, are you copying a number of files to this User Data\Default folder, or just the single bookmarks file? I wonder if something there is fooling Chrome into thinking it's already done the first run.

[kennysarmy]

After exhausting all the above options, I managed to get rid of the welcome page on Win 10 - By enabling the "Disable synchronization of data with Google" gpo. This is what the welcome page was effectively trying to get a user to do, by signing in...

 

Adding this to our Google Chrome GPO seems to have suppressed the Welcome Screen for us

[OrangeExige]

Adding this to our Google Chrome GPO seems to have suppressed the Welcome Screen for us

 

Same here. Adding this policy appears to be working for us also.

[jtotheb]

+1 for "Disable synchronization of data with Google" removing the Welcome to Chrome signing page.

[Davida1992]

Sorry to jump into this post, I am having similar issues, we are testing windows 10 at the moment ready to role out... We are on build 1706 with chrome pushed via MSI (62.0.3202.94)

 

I have been having 2 issues with Chrome:

 

1. First launch - user would see a welcome to chrome message...etc etc....

2. Second launch - User would be asked to sigh in to Chrome.

 

After reading through this, I seem to have resolved part 2 with the "Disable Sync of data with Google" in group policy so this is all good...

 

The issue now for me is part 1 - I have tried pushing a blank file called "First Run" to the default profile as shown in the image below:

 

 

I can then go to the user who has logged in and I can see the same file in their profile as below:

 

 

But, when I open Chrome I am still given the welcome page on first launch telling me I should set chrome as my default browser and telling me how to do it etc....

 

We are moving away from roaming profiles in win 10 and mandatory profiles, so I am testing with redirected folders only.

 

Any ideas anyone

[Arthur]

when I open Chrome I am still given the welcome page on first launch telling me I should set chrome as my default browser and telling me how to do it etc....

That's because you missed an important step.

 

You also need to create a 'Preferences' file telling Chrome that the welcome page has been seen. e.g.

 

$OSDISK = (Get-WmiObject Win32_OperatingSystem).SystemDrive
$Prefs = '{"browser":{ "has_seen_welcome_page":true }}'

New-Item -Path "$OSDISK\Users\Default\AppData\Local\Google\Chrome\User Data\Default\Preferences" -Value "$Prefs" -Type File -Force
New-Item -Path "$OSDISK\Users\Default\AppData\Local\Google\Chrome\User Data\First Run" -Type File -Force

Start -Wait msiexec -ArgumentList "/i GoogleChromeStandaloneEnterprise64.msi NOGOOGLEUPDATEPING=1 /qn"

[Davida1992]

This doesn't seem to help, I am pushing the files via GPO not via the Powershell script though.

 

The files are created as a computer policy on startup, I have checked the files are being created in the 2 locations above under the Default profile and they are being created.

 

However, users receiving the below on first launch:

 

 

Not sure what I would be doing wrong here

[Arthur]

This doesn't seem to help, I am pushing the files via GPO not via the Powershell script though.

That was just an example since you didn't mention you had already deployed the Preferences file. Group Policy also works.

 

Not sure what I would be doing wrong here

Based on your screenshot it also looks like you aren't setting Chrome as your default browser through Group Policy. I can post the XML you need a bit later if you don't already have it.

[Davida1992]

That was just an example since you didn't mention you had already deployed the Preferences file. Group Policy also works.

 

 

Based on your screenshot it also looks like you aren't setting Chrome as your default browser through Group Policy. I can post the XML you need a bit later if you don't already have it.

 

Yes please

[Davida1992]

I think I have sorted it, there is a item in GPO called "Set Google Chrome as Default Browser". I thought this was set to disabled, but it was not configured, I have set this to disabled and everything works now.

I believe I still needed the Preferences and First Run file as mentioned above though.

The combination of these things seems to mean it is working for me.

Thanks for your help

[Arthur]

Yes please

Just in case you need it, should you want to set Chrome as your default browser you will need to enable the GPO called "Set Google Chrome as Default Browser", export your default app associations with the DISM command below and then use the generated XML file with the Set a default associations configuration file GPO.

 

DISM /Online /Export-DefaultAppAssociations:"%UserProfile%\Desktop\FileAssociations.xml"

 

Your XML file should look like this, but with a lot more file associations in it.

 

[color="#800080"]  
 
 
 
 
 
 [/color]
 
 

 

Doing all of this will hide the screen shown in your screenshot.

[DavR]

I think I have sorted it, there is a item in GPO called "Set Google Chrome as Default Browser". I thought this was set to disabled, but it was not configured, I have set this to disabled and everything works now.

I believe I still needed the Preferences and First Run file as mentioned above though.

The combination of these things seems to mean it is working for me.

Thanks for your help

 

THIS! This is what I've been looking for!

 

I've been stuck with the same "welcome-win10" screen for ages. I was fixing this with a file bodge, but this is the setting I wanted. I'd overlooked it as I knew I didn't want to set Chrome as default, but using it as an inverse has done the trick.

 

I've now got my Chrome deployment running with no first-run annoyances, using GPO and the master preference file ONLY, no additional files or bodges required