Matt, can you find a resoruce to get these strings updated in the ADM / ADMX files?

We should *never* be recommending pinning to anything more than the major version as Omaha does not continue to host older minor versions after the refresh.

We're not planning any further M63 releases. 

+abdulsyed@ (M64 release TPM)

blumberg@ Gentle Ping! This issue is marked as RB-Stable for M64, could you please let us know is there any latest update available on this issue?

Thanks!

RBS and milestones removed as this is a documentation change, no reason to block stable on it.

Changes should be reflected in this: https://support.google.com/chrome/a/answer/3204698 article.


Josh & Georges, can either of you confirm that we are only supporting 'major version' and not minor with this feature?   Just need confirmation so Matt W can update the HC article with the proper limitations.

That's correct, only the milestone number (major version) is supported.

Matt W,

Can you update the HC article in c#6 to explain that only current stable and n-1 are available and only the major version (not minor).

I've added this text:

"Note that you can only pin to a major release of Chrome (such as Chrome 63, 64, and not a minor version such as 63.0.3239.132)."

to this article draft: https://support-content-draft.corp.google.com/chrome/a/answer/3204698

Can you review and let me know if this looks good to publish, or if additional changes are needed?

-Let's give explicit examples
-Should include the . after major version to avoid any possible future mismatching

To prevent Windows machines from updating to versions of Chrome beyond the number you specify, use the TargetVersionPrefix policy. For example, you can pin the Chrome version "63." via the policy to prevent devices from updating past Chrome 63. Note that version pinning should only include the major release number of Chrome (such as Chrome 63. or 64. ). Attempting to pin to a minor release number will not work.

However, you should try to avoid version pinning. If you forget to unpin your users’ machines, they can fall behind on critical security updates and miss out on new features in Chrome.

Thanks for this update! I updated this text today, and it's live in this article: https://support.google.com/chrome/a/answer/3204698. Please email me if any additional updates are needed.

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time.
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!