Jun 16 2022 08:08 AM
Apologies in advanced if this is to specific 🙂
Historically we used Windows Feature Update profiles (coupled with Windows Update Ring policies) in Intune to manage our OS upgrades, i.e. Win10 20H1, 20H2, 21H1, 21H2. To do this we needed to deploy a configuration profile as well to set the TargetReleaseVersion (TRV) here : -- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Update
This would allow a limit to set to keep devices on a certain OS's.
We are seeing that deploying using Feature Update Profiles alone seems to handle things a lot better. Are you able to confirm that using those alone is enough without the need to set the TRV in the reg?
We are currently co-managed with MECM\Intune(MEM) and we under the impression that setting the TRV was kind of a workaround for a specific issue a while back where co-managed devices were upgrading beyond the Feature Update OS version that was targeted at them???
Jun 16 2022 08:15 AM
@nlmitchell absolutely, Feature Update profiles are designed to keep devices on the targeted feature update until the device is assigned to a feature update profile with a newer feature update version. So we recommend NOT setting the TargetReleaseVersion property when using feature update policies, as they can conflict with each other.
HTH,
-David Guyer
Jun 16 2022 08:20 AM
Jun 16 2022 08:33 AM