Configuring Group Policy for Google Chrome to Maintain Manifest V2 Extensions

As Google Chrome transitions from Manifest V2 to Manifest V3, enterprise users who still rely on Manifest V2 extensions like SessionBox Legacy can configure their systems to continue supporting these extensions. This guide provides detailed steps on how to use Group Policy to manage this setting within your organization.

Step-by-Step Guide

1. Download the Policy Templates:

   • First, ensure you have the latest Chrome policy templates. You can download them from the Chrome Enterprise Policy List.

2. Add the Templates to Group Policy:

   • Extract the downloaded zip file.

   • Copy the contents of the Policy_Templates folder to your Group Policy Central Store. This is typically located at \\<DomainName>\SYSVOL\<DomainName>\Policies\PolicyDefinitions.

3. Configure the Group Policy:

   • Open the Group Policy Management Console (GPMC).

   • Create a new Group Policy Object (GPO) or select an existing one where you want to apply the settings.

   • Right-click the GPO and select “Edit” to open the Group Policy Management Editor.

4. Navigate to Chrome Policies:

   • Under the Group Policy Management Editor, go to Computer Configuration > Administrative Templates > Google > Google Chrome > Extensions.

5. Enable ExtensionManifestV2Availability:

   • Locate the policy named ExtensionManifestV2Availability.

   • Double-click to open the policy settings.

   • Set the policy to “Enabled” and choose your desired configuration option:

     • Keep allowing: This will allow Manifest V2 extensions to continue running.

   • Click “OK” to apply the changes.

6. Deploy the GPO:

   • Link the GPO to the appropriate Organizational Unit (OU) containing the computers where you want this policy to apply.

   • Ensure the policy is updated on the target machines by running gpupdate /force from the command line or waiting for the next policy refresh cycle.

Testing and Validation

After applying the Group Policy, it’s crucial to test and validate that the settings are effective:

• On a client machine, open Google Chrome and navigate to chrome://policy to verify that the ExtensionManifestV2Availability policy is listed and correctly configured.

• Check that Manifest V2 extensions like SessionBox Legacy are functioning as expected.

Additional Resources

For more detailed information and troubleshooting, refer to the Chrome Enterprise documentation and the Google Chrome Enterprise Help Center.

By following these steps, enterprise IT administrators can ensure a smooth transition while maintaining the functionality of essential extensions during the phased rollout of Manifest V3