{"id":1605,"date":"2017-01-19T08:55:00","date_gmt":"2017-01-19T08:55:00","guid":{"rendered":"http:\/\/neu.koetzingit.de\/internet-browser-teil-2-google-chrome\/"},"modified":"2026-06-02T13:32:50","modified_gmt":"2026-06-02T13:32:50","slug":"internet-browser-teil-2-google-chrome","status":"publish","type":"post","link":"https:\/\/www.koetzingit.de\/en\/internet-browser-teil-2-google-chrome\/","title":{"rendered":"Web Browsers, Part 2: Google Chrome"},"content":{"rendered":"

D<\/span>This is a three-part article about web browsers in a Multi-user system<\/strong> such as Citrix Server VDA or Remote Desktop Services (RDS). This article explains how to deploy and configure web browsers so that they function as smoothly as possible in these environments. The most common browsers I encounter at client sites are Microsoft Internet Explorer, Google Chrome<\/strong> and Mozilla Firefox<\/strong> and so this is a three-part article.<\/p>\n

Please keep in mind that things may vary between browser versions, so you should test with each version.
This is the\u00a0Part Two<\/strong> via Google Chrome.<\/p>\n

<\/p>\n

\u00a0<\/p>\n

Note<\/strong><\/span>
This article is about deploying and configuring web browsers in multi-user environments, not about whether the browser is the best, fastest, coolest, or whatever.<\/p>\n

\u00a0<\/p>\n

About Google Chrome<\/span><\/h3>\n

Google offers a range of online services, so optimizing Chrome for them makes sense and may be the reason why Chrome is used. Google Chrome comes in two editions: Work and Enterprise. The latter is the one businesses want, and here is the link to it https:\/\/www.google.de\/chrome\/business\/browser\/admin<\/a> Google Chrome can also be configured using Microsoft Group Policy, which is always a plus for me. The current Group Policy templates can be found at the following URL http:\/\/dl.google.com\/dl\/edgedl\/chrome\/policy\/policy_templates.zip<\/a>\u00a0Always make sure to use the same versions of Group Policy and Chrome. Google frequently makes minor changes to Chrome\u2014and not necessarily for the better\u2014so you can never be entirely sure what will still work after an update. In addition, some features seem to stop working, and for me, it was the master_preferences<\/strong> File. The main drawback for me is that Avatar\/Profile\/Account Icon<\/strong> which could be removed in previous versions but can no longer be done in the current versions. Another problem is that Chrome can cause user profiles to become extremely bloated, thereby Registration times lasting several minutes<\/strong> may take some time.<\/p>\n

\"Blogs
Google Chrome \u2013 Avatar Icon\u00a0<\/p>\n

Deployment<\/span><\/h3>\n

Google Chrome Enterprise is available as an MSI file googlechromestandaloneenterprise.msi<\/strong> and can therefore be installed using the standard MSI parameters. There is an additional Chrome option that should be set, and it is NOGOOGLEUPDATEPING=1<\/strong><\/p>\n

The command line for an unattended installation:
MSIEXEC.EXE \/I \"%CURRPATH%\\GoogleChromeStandaloneEnterprise.msi\" NOGOOGLEUPDATEPING=1 \/q \/norestart<\/code><\/p>\n

Google installs update services, which can also be removed later via the command line.\u00a0<\/p>\n

sc stop gupdate<\/code>
sc delete gupdate<\/code>
sc stop gupdatem<\/code>
sc delete gupdatem<\/code><\/p>\n

If the master_preferences file ever works, it must be copied to the target installation directory after the installation is complete.<\/p>\n

\u00a0<\/p>\n

Configuration<\/span><\/h3>\n

There are several options for configuring Chrome in addition to Group Policy: a) command-line parameters, b) Chrome flags, and c) the master_preferences file. Chrome flags are for manual changes, and the master_preferences file should set these automatically. Group policies and command-line parameters are the combination you need to configure Chrome the way you want.<\/p>\n

The parameters are: \u2013no-first-run<\/strong> and \u2013disable-gpu<\/strong> and disables the initialization dialog and GPU usage when a virtual system is selected.<\/p>\n

The command line to launch Chrome
\"C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\" --no-first-run --disable-gpu<\/code><\/p>\n

Chrome stores a vast amount of data in the user's data directory, which is located by default in the AppData folder of the user profile. I recommend redirecting the folder to a network folder, such as the home folder (Home Drive), since a separate folder is required for each user. Of course, this can lead to performance or other issues (network errors), but a decision must be made here between login time and performance. So far, customers have not reported any problems with redirecting the folder to the network.<\/p>\n

NOTE:<\/strong> I recommend absolutely not\u00a0<\/strong>Redirecting the entire AppData directory! This can lead to a number of problems!<\/p>\n

Here a few important<\/strong> Chrome Group Policy<\/p>\n