Updating the adm files
For more information, see A new or file is released with a new version of the software. Doing so prevents corruption of profile data, which might result when different user store structures (from different versions) exist.
Citrix recommends that you upgrade all computers to the latest version of Profile Management before enabling any new setting.
By default, the update payloads can’t be cached in most cases.
Usually, it isn't an issue for consumer instances of Chrome but it might be a problem for some enterprise environments.
For details, see the Registry settings section below.
Minimum number of minutes between automatic update checks.
Only Google applications that use Google Update are affected by these policies.
To prevent updates for a specific application, you should instead use the Update policy override Applications policy for that application.
Provides a hint for the update servers about the update payload URLs returned in the update response. When enabled, this policy might result in the server responding with a payload that could be cached by downstream proxies or similar types of content-caching solutions. The server can ignore it, depending on load and several other reasons.
You can apply a set of policies to managed computers using the Group Policy Management Console.
Or, you can use another way, such as logon scripts, to directly modify the registry values.
Search for updating the adm files:
To check whether a setting is new in the version you are using, see Profile Management Policies.