Part 1: Install the Chrome ADMX Templates
You will need the Chrome ADM/ADMX templates before you can configure the Guidde browser extension via GPO.
Download the appropriate Chrome ADM/ADMX templates from https://chromeenterprise.google/browser/download/
Note: Scroll down to "Need to stick with on-premise management" and download both the Policy and Update templates.
Unzip both downloads. You will need the following 6 files:
Google.admxGoogleUpdate.admxChrome.admxGoogle.admlGoogleUpdate.admlChrome.adml
Open
GoogleUpdate.admxin a text editor and delete the following line:
<using prefix="windows" namespace="Microsoft.Policies.Windows" />
4. Open Chrome.admx in a text editor and delete the following line:
<using namespace="Microsoft.Policies.Windows" prefix="windows"/>
5. Copy the .admx files to your domain controller's PolicyDefinitions folder:
C:\Windows\SYSVOL\domain\Policies\PolicyDefinitions\
6. Copy the .adml files to the language subfolder (e.g., for English):
C:\Windows\SYSVOL\domain\Policies\PolicyDefinitions\en-US\
7. Confirm all files are in place before proceeding to Part 2.
Part 2: Configure the Group Policy Object
Open the Group Policy Management Console (GPMC) on your domain controller.
Create a new GPO or select an existing one to edit.
Link the GPO to the relevant Organizational Unit (OU).
Right-click the GPO and select Edit.
Navigate to: Computer Configuration >> Policies >> Administrative Templates >> Google >> Google Chrome >> Extensions
Open "Configure the list of force-installed apps and extensions".
Set the policy to Enabled.
Click Show and add the following value:
oacmmmjedhheaijfjidilonpngccnhdl;https://clients2.google.com/service/update2/crx
9. Click OK to save.
10. Close the Group Policy Management Editor.
To test immediately on a target machine, run:
gpupdate /force
Otherwise, the policy will apply automatically on the next Group Policy refresh cycle.
Note: It can take up to 90 minutes for Group Policy to propagate across the domain. Once deployed, the Guidde extension will appear as installed in Chrome.
Silent SSO: Automatic Sign-In for Managed Installations
When the extension is deployed via managed installation, Silent SSO is automatically triggered on the user’s device - no user interaction required.
What happens:
No browser tabs are opened, no prompts or alerts are shown to the user
The extension identifies the org’s SSO domain using the email associated with the user’s Chrome profile
It authenticates the user against the Guidde backend and SSO provider
The auth token is set for both the extension and app.guidde.com
This means users will be signed in and ready to use Guidde without any manual login step.
If the user isn’t logged into the SSO provider yet: The extension will retry authentication every 60 seconds. Once the user signs into any application that triggers an SSO session, the Guidde extension will authenticate automatically.