Chromebooks are headed to work this fall, thanks to a new program that Google introduced today. The new Chrome Enterprise bundle provides enterprises with a set of services that help bring Chromebooks on par with Microsoft Windows PCs.
Chrome Enterprise will give IT administrators a cloud-based management portal for handling a fleet of Chromebooks, support for virtualized desktop applications, theft prevention, and a host of other features. One of the most important features in the bundle for many enterprises will be support for authentication through Microsoft Active Directory, even when the directory server is held in an on-premises environment.
For windows OS, a bundle, which consists of chrome standalone installer (64-bit msi), ADM templates, admx-adml files and a list of applicable registry settings, can be downloaded from Chrome Enterprise download page.
To modify or create google chrome homepage registry settings, go to HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome and configure HomepageLocation and/or HomepageIsNewTabPage registry settings.
To modify or create google chrome startup page registry settings go to HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome and configure RestoreOnStartup and RestoreOnStartupURLs registry settings.
To modify or create google chrome new tab registry settings go to HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome and configure NewTabPageLocation registry setting.
Once the files from the downloaded Google chrome bundle have been extracted, go to GoogleChromeEnterpriseBundle64/Configuration/admx and copy chrome.admx and google.admx to the policy definition folder inside sysvol directory of your domain. Then also copy over corresponding adml files.
Google has rolled back an experimental WebContent Occlusion feature that caused major disruption for enterprise users using Chrome in a multi-user terminal server environment. While the issue is now fixed, enterprise admins are furious that this feature was enabled in the first place without their knowledge or permission.
This is for example the OMA-URI to manage the Homepage Location./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Startup/HomepageLocationLet`s split up the OMA-URI in seperate parts.This is default for managing applications using an ADMX file:./Device/Vendor/MSFT/Policy/Config/The part that comes next is not always the same, we need to follow some rules:/Chrome~Policy~googlechrome~Startup/It start with Chrome (the ADMX file name), like in the ADMXInstall URI, followed by Policy. Between every part we have the ~ sign.After Policy we see the name of two categories. These categories can be found in the Chrome ADMX file.When we open the ADMX file in a text editor, we can see there are several categories. The first categorie we find in the ADMX file is the top category and as we can see that is googlechrome. We put this in the OMA-URI after Policy.
Hi Peter,I have managed to perform these steps for Chrome and they work great.I wanted to add some trusted sites on my google chrome, how I can perform as I cannot find anything related to it on ADMX file. Normal GPO, google takes from Internet Explorer so can you please help me.RegardsKumar
BackgroundModeEnabled./Device/Vendor/MSFT/Policy/Config/chrome~Policy~googlechrome/BackgroundModeEnabledSetting the policy to Enabled turns background mode on. In backgroudn mode a Google Chrome process is started on OS sign-in and keeps running when the last browser window is closed allowing background apps and the browsing session to remain active including any session cookies. The background process displays an icon in the system tray and can always be closed from there.
We are interested in windows folder only. Open the windows\admx folder and we can see chrome.admx & google.admx including various language folders containing supported language file required for admx ie. Chrome.adml & google.adml.
Permits the option of injecting key-value pairs via XML into an app when it launches in User Mode. Bundled data can include application parameters, user data or any other information consumable by the application as an Android Intent. This feature can be used with User-Mode apps, Kiosk apps, auto-launch apps and those resulting from wildcard searches. When used with apps specified using the wildcard attribute, all apps receive the same data. The Bundle tag must be configured within the enterprisehomescreen.xml file. Bundle is not supported for Admin-mode apps or for use with links or services.
Since most of the organizations use Windows 10 OS, we will download the Windows 64 bit version of chrome. For your information, when you download Google Chrome enterprise for Windows 10, the package includes the following. 2b1af7f3a8