macdaddy Posted March 27, 2017 Posted March 27, 2017 We employ Group Policy to set Chrome Home Page and to suppress the Welcome page. For years this has worked great on Windows 7 Pro machines. The result is with a user logging in the first time and opening Chrome they only get their Home Page tab. We are now deploying Windows 10 Edu 1607 and Chrome with first time user gets the Welcome to Chrome tab and their Home Page tab. Has anyone else seen this issue? OS=Windows 10 Edu 1607 Chrome=v57 Using the latest admx and adml files in central store
Wubbalubbadub Posted April 1, 2017 Posted April 1, 2017 I also have this issue. I am still struggling with the start menu, so just added it to the loooooong list of issues with Windows 10! Hopefully someone with a bit more time on Windows 10, has found out why it does this?
rogerdnixon Posted April 1, 2017 Posted April 1, 2017 You need to set it as the default browser with a preference file - see: https://support.google.com/chrome/a/answer/7009292
macdaddy Posted April 3, 2017 Author Posted April 3, 2017 @rogerdnixon thanks for the idea but we already do this. I am beginning to think this problem is Windows 10. The same problem with Chrome Welcome page also occurs with Edge. IE works fine. Both Chrome and Edge are controlled by Group Policy to stop the welcome page. I believe the issue maybe that the registry keys needed to suppress the welcome page are not created until the user first launches the browser. This link touches on the subject. I have tried adding the powershell script during imaging with SCCM but did not work. Need to test this further.
Popular Post ADMaster Posted April 3, 2017 Popular Post Posted April 3, 2017 There is a first run file that gets created after you run chrome for the first time. I just create this file in the default user profile to stop the welcome screen. New-Item -ItemType file -Path "$OSDISK\Users\Default\AppData\Local\Google\Chrome\User Data\First Run" -Force 6
macdaddy Posted April 3, 2017 Author Posted April 3, 2017 @ADMaster You sir are Brilliant! Copied the "First Run" file from an existing profile that has logged into Chrome and pasted to your location mentioned. Had to create the subfolders in the process. Now just need to add this as a task in SCCM and off and running. It does appear 1607 made changes, a shame Google was not on top of this.
KibosJ Posted April 4, 2017 Posted April 4, 2017 There is a first run file that gets created after you run chrome for the first time. I just create this file in the default user profile to stop the welcome screen. New-Item -ItemType file -Path "$OSDISK\Users\Default\AppData\Local\Google\Chrome\User Data\First Run" -Force This small issue has bugged me for a little while now! Thanks
win Posted July 24, 2017 Posted July 24, 2017 Does this solution still apply to 1703 and latest version of chrome? I'm testing with mandatory profiles, 1703 education, and chrome 59.0.3071.115 (x64) enterprise, latest admx, copied the first run file to the default user folder, but annoyingly that first run screen still appears.
ADMaster Posted July 24, 2017 Posted July 24, 2017 Since v57 or 58 you have needed to make and copy a prefs file. See my other post https://www.edugeek.net/showthread.php?p=1572171
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now