If using Feature Update Rings for over a year, but started with All at once, or in smaller groups. Could you tell me the expected behaviour if a device is left in an update ring that deploys a feature update. We seem to have a problem with the trigger of the updates. If I start the service manually the updates are downloaded and installed. What could be the problem here? Some device in the same update ring do get updates. Hi Paul, Are you saying that no updates are installing, or are you saying that the latest feature update is not installing?
Starting the service manually does not seem to be the solution either. Sometimes we have to support users and then it turns out that there are still a lot of updates waiting to be downloaded and installed. Some other devices in the same updatering like my own laptop , do receive the udates without any user interaction. This really puzzles us.
Is there a way to see some logs of this process? It seems that updates are working now. We have been working on getting rid of some conflicts between configuration profiles. Sometime there are too many places where you can make settings that are more or less the same.
Notify me of follow-up comments by email. Notify me of new posts by email. This site uses Akismet to reduce spam. Learn how your comment data is processed. Home Scripts Archive Contact About. Within Microsoft Intune the following policy types are provided to control updates: Windows 10 update rings : The Windows 10 update rings policy is a collection of settings that configures setting to control when Windows 10 updates get installed.
This policy type already exists for a while and enables administrators to create update rings that specify how and when Windows 10 devices should be updated with feature and quality updates. As long as the latest update is installed, the Windows 10 devices are up to date. Windows 10 feature updates : Currently public preview The Windows 10 feature updates policy brings devices to the specified Windows version and freezes the feature set on those devices until the administrator chooses to update them to a later Windows version.
While the feature version remains static, devices can continue to install quality and security updates that are available for their feature version. Introducing the Window 10 feature updates policy A Windows 10 feature updates policy is a pretty simplistic policy — from a configuration perspective — to control the Windows 10 feature updates on a device.
When deploying a Windows 10 feature update policy to a device that also receives a Windows 10 update rings policy, the following configurations should be in place within the configured update ring: The Feature update deferral period days setting must be set to 0. The feature updates of the Windows 10 update rings policy must be running. A Windows 10 feature update policy cannot be applied during the Windows Autopilot process, instead the policy will apply at the first Windows Update scan after a device has finished provisioning which is typically a day.
Prerequisites for the Windows 10 feature updates policy When starting with the implementation of a Windows 10 feature updates policy, the following prerequisites must be met — at this moment — by the assigned devices to guarantee the described behavior. Feature update deployment result More information For more information about configuring updates in Microsoft Intune, refer to the documentation about Manage Windows 10 software updates in Intune.
Thank you Reply. Regards, Peter Reply. Pingback: Windows 10 Feature Updates: Upgrade? Pingback: Windows Update for Business. Thank you, Reply. Hi Peter, Great article as always, it has been helpful! I am just starting to use this now and I can see the update ring control works pretty well. Thanks Shimal Reply. Hi Axel, Could it be that those settings are conflicting?
How come this does not work? These can be run during four phases of a feature update:. Custom actions run during a feature update that is installed by Windows Setup. For example, updating from Windows 10, version to Windows 10, version 20H2. Custom actions are not supported for feature updates that are installed via enablement packages.
Windows Setup automatically looks for these scripts in the following locations, and will run them if they are present:. Use this GUID to name a folder within the run and runonce folders. They work very well!
More to come on these in a future post. This is the next installment in my Windows 10 Feature Updates series. From the Microsoft Docs article: Custom actions are. These can be run during two phases of an upgrade: Pre-install phase: This phase is when Setup starts, but prior compatibility checks. Actions during this phase are specified in preinstall. Pre-commit phase: This phase is prior to the upgrade being applied and the system rebooting. Actions during this phase are specified in precommit.
Instead, the policies apply at the first Windows Update scan after a device has finished provisioning, which is typically a day. If you co-manage devices with Configuration Manager, feature updates policies might not immediately take effect on devices when you newly configure the Windows Update policies workload to Intune. This delay is temporary but can initially result in devices updating to a later feature update version than is configured in the policy. Sign in to the Microsoft Endpoint Manager admin center.
For Deployment settings , enter a meaningful name and a description for the policy. Then, Specify the feature update you want devices to be running. Complete the policy configuration, including assigning the policy to devices. Monitor the report for the policy. Select the policy you created and then generate the report. Devices that have a state of OfferReady or later, are enrolled for feature updates and protected from updating to anything newer than the update you specified in step 3.
See, Use the Windows 10 and later feature updates Organizational report. With devices enrolled for updates and protected, you can safely change the Windows Update policies workload from Configuration Manager to Intune. See, Switch workloads to Intune in the co-management documentation.
When the device checks in to the Windows Update service, the device's group membership is validated against the security groups assigned to the feature updates policy settings for any feature update holds.
Managed devices that receive feature update policy are automatically enrolled with the Windows Update for Business deployment service.
The deployment service manages the updates a device receives. The service is utilized by Microsoft Endpoint Manager and works with your Intune policies for Windows updates to deploy feature updates to devices. When a device is no longer assigned to any feature update policies, Intune waits 90 days to unenroll that device from feature update management and to unenroll that device from the deployment service. To keep a device at its current feature update version and prevent it from being unenrolled and updated to the most recent feature update version, ensure the device remains assigned to a feature update policy that specifies the devices current Windows version.
Specify a name, a description optional , and for Feature update to deploy , select the version of Windows with the feature set you want, and then select Next. Only versions of Windows that remain in support are available to select. Configure Rollout options to manage when Windows Updates makes the update available to devices that receive this policy.
0コメント