Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.microsoft.com/en-us/mem/intune/protect/windows-10-feature-updates below:

Configure feature updates policy for Windows 10 Windows 11 devices in Intune

With Feature updates for Windows 10 and later in Intune, you can select the Windows feature update version that you want devices to remain at, like Windows 10 version 1909 or a version of Windows 11. Intune supports setting a feature level to any version that remains in support at the time you create the policy.

You can also use feature updates policy to upgrade devices that run Windows 10 to Windows 11.

Windows feature updates policies work with your Update rings for Windows 10 and later policies to prevent a device from receiving a Windows feature version that's later than the value specified in the feature updates policy.

When a device receives a policy for Feature updates:

• The device updates to the version of Windows specified in the policy. A device that already runs a later version of Windows remains at its current version. By freezing the version, the devices feature set remains stable during the duration of the policy.

  Note

  A device won't install an update when it has a safeguard hold for that Windows version. When a device evaluates applicability of an update version, Windows creates the temporary safeguard hold if an unresolved known issue exists. Once the issue is resolved, the hold is removed and the device can then update.

  • Learn more about safeguard holds in the Windows documentation for Feature Update Status.

  • To learn about known issues that can result in a safeguard hold, see the applicable Windows release information and then reference the relevant Windows version from the table of contents for that page:

    • Windows 11 release information
    • Windows 10 release information

    For example, for Windows 11 version 21H2, go to the Windows 11 release information and then from the left-hand pane, select Version 21H2 and then Known issues and notifications. The resultant page includes details for known issues for that Windows version that might result in safeguard hold.

• Unlike using Pause with an update ring, which expires after 35 days, the Feature updates policy remains in effect. Devices won't install a new Windows version until you modify or remove the Feature updates policy. If you edit the policy to specify a newer version, devices can then install the features from that Windows version.

• The ability to Uninstall the Feature update is still honored by the Update Rings.

• You can configure policy to manage the schedule by which Windows Update makes the offer available to devices. For more information, see Rollout options for Windows Updates.

The following are prerequisites for Intune's Feature updates for Windows 10 and later:

• The core functionality of creating and targeting a feature update only requires a license for Intune. The core functionality includes creating the policy and selecting a feature update to update devices, using the Make updates available as soon as possible option or specifying a start date, and reporting. Capabilities supported by client policies on Professional SKU devices don't require a license.

• Additional cloud-based functionality requires an additional license. To use a cloud-based capability, in addition to a license for Intune, your organization must have one of the following subscriptions that include a license for Windows Autopatch:

  • Windows 10/11 Enterprise E3 or E5 (included in Microsoft 365 F3, E3, or E5)

  • Windows 10/11 Education A3 or A5 (included in Microsoft 365 A3 or A5)

  • Windows Virtual Desktop Access E3 or E5

  • Microsoft 365 Business Premium

  Beginning in November of 2022, the Windows Autopatch license is checked and enforced.

  The cloud-based capabilities requiring the additional license are indicated in the Create feature update deployment or policy creation page and include the following items and potentially new features:

  • Gradual rollout: The Gradual Rollout capability is a cloud only feature and includes basic controls for deploying a specified feature update and when to start making the update available to devices.

  • Optional feature updates

  • Windows 10 (SxS): The Windows 10 (SxS) feature is a cloud-only feature. If you're blocked when creating new policies for capabilities that require Windows Autopatch and you get your licenses to use Windows Update client policies through an Enterprise Agreement (EA), contact the source of your licenses such as your Microsoft account team or the partner who sold you the licenses. The account team or partner can confirm that your tenants licenses meet the Windows Autopatch license requirements. See Enable subscription activation with an existing EA.

• Devices must:

  • Run a version of Windows 10/11 that remains in support.

  • Be enrolled in Intune MDM and be Microsft Entra hybrid joined or Microsoft Entra joined.

  • Have Telemetry turned on, with a minimum setting of Required.

    Devices that receive a feature updates policy and that have Telemetry set to Not configured (off), might install a later version of Windows than defined in the feature updates policy.

    Configure Telemetry as part of a Device Restriction policy for Windows 10/11. In the device restriction profile, under Reporting and Telemetry, configure the Share usage data with a minimum value of Required. Values of Enhanced (1903 and earlier) or Optional are also supported.

  • The Microsoft Account Sign-In Assistant (wlidsvc) must be able to run. If the service is blocked or set to Disabled, it fails to receive the update. For more information, see Feature updates aren't being offered while other updates are. By default, the service is set to Manual (Trigger Start), which allows it to run when needed.

  • Have access to endpoints. To get a detailed list of endpoints required for the associated services listed here, see Network endpoints.

    • Windows Update
    • Windows Autopatch

• Enable data collection in Intune for devices that you wish to deploy feature updates.

• Feature updates are supported for the following Windows 10/11 editions:

  • Pro
  • Enterprise
  • Pro Education
  • Education
  • Pro for Workstations

  Note

  Unsupported versions and editions: Windows 10/11 Enterprise LTSC: Windows Update client policies does not support the Long Term Service Channel release. Plan to use alternative patching methods, like WSUS or Configuration Manager.

Intune policies for Feature updates for Windows 10 and later require the use of Windows Update client policies and Windows Autopatch. Where Windows Update client policies supports WPJ devices, Windows Autopatch provides more capabilities that aren't supported for WPJ devices.

For more information about WPJ limitations for Intune Windows Update policies, see Policy limitations for Workplace Joined devices in Manage Windows 10 and Windows 11 software updates in Intune.

• When you deploy a Feature updates for Windows 10 and later policy to a device that also receives an Update rings for Windows 10 and later policy, review the update ring for the following configurations:

  • We recommend setting the Feature update deferral period (days) to 0. This configuration ensures your feature updates aren't delayed by update deferrals that might be configured in an update ring policy.
  • Feature updates for the update ring must be running. They must not be paused.

  Tip

  If you're using feature updates, we recommend you set the Feature update deferral period to 0 in the associated Update Rings policy. Combining update ring deferrals with feature updates policy can create complexity that might delay update installations.

  For more information, see Move from update ring deferrals to feature updates policy

• Feature updates for Windows 10 and later policies can't be applied during the Windows Autopilot out of box experience (OOBE). 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.

  To prevent this initial delay from impacting your co-managed devices:

  1. Sign in to the Microsoft Intune admin center.

  2. Go to Devices > By platform > Windows > Manage updates > Windows 10 and later updates > Feature updates tab > Create profile.

  3. For Deployment settings, enter a meaningful name and a description for the policy. Then, specify the feature update you want devices to be running.

  4. Complete the policy configuration, including assigning the policy to devices. The policy deploys to devices, though any device that already has the version you've selected, or a newer version, won't be offered the update.

     Monitor the report for the policy. To do so, go to Reports > Windows Updates > Reports tab > Feature Updates report. Select the policy you created and then generate the report.

  5. 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 feature updates (Organizational) report.

  6. 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 Autopatch. The service manages the updates a device receives. Microsoft Intune uses this service 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, the device remains enrolled in Autopatch. This change allows time to assign the device to a different policy and ensure that in the meantime the device doesn't receive a feature update that wasn't intended.

As a result, when a feature updates policy no longer applies to a device, that device isn't offered any feature update until one of the following happens:

• The device is assigned to a new feature update profile.
• The device is unenrolled from Intune, which unenrolls the device from feature update management by Autopatch.
• You use the Windows Autopatch graph API to remove the device from feature update management.

1. Sign in to the Microsoft Intune admin center.

2. Select Devices > By platform > Windows > Windows 10 and later updates > Feature updates tab > Create profile.

3. Under Deployment settings:

   a. Name, Description: Specify a name, and a description (optional).

   b. Required/Optional updates: These options are only available when the target version is Windows 11.

   • When the default option Make available to users as a required update is selected, the device will automatically install the update based on device settings.
   • When the admin selects the option Make available to users as an optional update, then the selected updates are made available to users as an optional update. The rollout settings still control when the update is available to the device but then the user must choose to install the update before it is installed on the device.

   What the user sees on their device When the admin makes the update available as an Optional update, the user must navigate to the Windows update settings page to see and choose to install the update. It is recommended to communicate to end users through your communication channels that an optional update is available to them. When the user navigates to the Windows update settings page, they can see and choose to install the update when they're willing to take the update. Users have to click Download to install the update. Otherwise it doesn't get installed until the admin makes it a Required update. It's the same optional update experience that users are familiar with in their personal PCs.

   When the admin switches from Optional to Required, the following behavior is observed:

   • Updates aren't reinstalled for people who went ahead and opted to install the update back when it was an Optional update.
   • If a device has not started on an update, the next time the device checks for updates the update is treated and automatically installed as a Required update.

   When the admin switches from Required to Optional, the following behavior is observed:

   • Devices that have already installed the update are not impacted.
   • Devices that are pending restart are likely to continue to install the update as a Required update.
   • Switching only impacts devices that haven't started the update yet or were early enough in the update process so they could be changed to an Optional update.

   c. Feature update to deploy: select the specific version of Windows with the feature set you want deployed on your devices. Only versions of Windows that remain in support are available to select.

   d. Rollout options: Configure Rollout options to manage when Windows Updates makes the update available to devices that receive this policy. For more information about using these options, see Rollout options for Windows Updates, and then select Next.

4. Under Assignments, choose + Select groups to include and then assign the feature updates deployment to one or more device groups. Select Next to continue.

5. Under Review + create, review the settings. When ready to save the Feature updates policy, select Create.

You can use policy for Feature updates for Windows 10 and later to upgrade devices that run Windows 10 to Windows 11.

When you use feature updates policy to deploy Windows 11, you can target the policy to Windows 10 devices that meet the Windows 11 minimum requirements to upgrade them to Windows 11. Devices that don't meet the requirements for Windows 11 won't install the update and remain at their current Windows 10 version.

Another option is to select the checkbox When a device isn't capable of running Windows 11, install the latest Windows 10 feature update, then devices that don't meet the requirements for Windows 11 will get the latest Windows 10 feature update instead.

However, if a Windows 10 device that can't run Windows 11 is targeted with a Windows 11 update, future Windows 10 updates won't be offered to that device automatically. In this case, remove the not eligible device from the Windows 11 policy and assign the device to a Windows 10 feature update policy. See Update behavior when multiple policies target a device.

The first step in preparing for a Windows 11 upgrade is to ensure your devices meet the minimum system requirements for Windows 11.

You can use Endpoint analytics in Microsoft Intune to determine which of your devices meet the hardware requirements. If some of your devices don't meet all the requirements, you can see exactly which ones aren't met. To use Endpoint analytics, your devices must be managed by Intune, co-managed, or have the Configuration Manager client version 2107 or newer with tenant attach enabled.

If you're already using Endpoint analytics, navigate to the Work from anywhere report, and select the Windows score category in the middle to open a flyout with aggregate Windows 11 readiness information. For more granular details, go to the Windows tab at the top of the report. On the Windows tab, you'll see device-by-device readiness information.

Windows 11 includes a new license agreement, which can be viewed at https://www.microsoft.com/useterms/. This license agreement is automatically accepted by an organization that submits a policy to deploy Windows 11.

When you use configure a policy in the Microsoft Intune admin center to deploy any Windows 11 version, the Microsoft Intune admin center displays a notice to remind you that by submitting the policy you are accepting the Windows 11 License Agreement terms on behalf of the devices, and your device users. After submitting the feature updates policy, end users won't see or need to accept the license agreement, making the update process seamless.

This license reminder appears each time you select a Windows 11 build, even if all your Windows devices already run Windows 11. This prompt is provided because Intune doesn't track which devices will receive the policy, and its possible new devices that run Windows 10 might later enroll and be targeted by the policy.

For more information including general licensing details, see the Windows 11 documentation.

To deploy Windows 11, you'll create and deploy a feature updates policy just as you might have done previously for a Windows 10 device. It's the same process though instead of selecting a Windows 10 version, you'll select a Windows 11 version from the Feature update to deploy dropdown list. The dropdown list displays both Windows 10 and Windows 11 version updates that are in support.

Also, the admin can choose to deploy the latest Windows 10 update to devices that are not eligible for Windows 11. To enable this feature, the admin must select the checkbox When a device isn't capable of running Windows 11, install the latest Windows 10 feature update in the deployment policy. This capability is only available if you choose a Windows 11 version from the Feature update to deploy dropdown list, and if the tenant meets the licensing requirements defined at the beginning of this document.

With this capability, you do not need to create two different deployment policies or two different feature updates. With a single policy, you can get your Windows 10 devices that can't go to Windows 11 to upgrade to the latest Windows 10 version and all the devices that can go to Windows 11 to upgrade to a Windows 11 version that you choose.

You cannot set the checkbox for an existing policy because changing the checkbox value ends the current deployment and starts two new deployments. To change your deployment settings, delete the current feature update policy and create a new policy with the checkbox selected.

• Deploying an older Windows version to a device won't downgrade the device. Devices only install an update when it's newer than the devices current version.
• Deploying a Windows 11 update to a Windows 10 device that supports Windows 11, upgrades that device.

Consider the following points when feature update policies target a device with more than one update policy, or target a Windows 10 device with an update for Windows 11:

• Each Windows feature update policy supports a single update. When a device is targeted by more than one policy, it might be targeted with multiple update versions.

• The Windows Update service can only offer a device one feature update at a time, and always offers the latest update version that targets the device.

• Because Windows 11 updates are considered to be later versions than Windows 10, the service always offers the Windows 11 update to a device targeted by both Windows 10 and Windows 11 updates. This is done because deploying a Windows 11 update to a Windows 10 device is a supported upgrade path.

• Using the checkbox When a device isn't capable of running Windows 11, install the latest Windows 10 feature update when using multiple policies avoids the problems mentioned in this section and configures the service to detect when the Windows 11 is not eligible for a device and instead offers the latest Windows 10 feature update.

Note

If you create two policies with the same device/s, where one is set to Required and the other set to Optional and both policies target the same feature update version, then the update is offered as Required.

In the admin center, go to Devices > By platform > Windows > Manage updates > Windows 10 and later updates > Feature updates tab to view your profiles.

For each profile you can view:

• Feature Update Version – The feature update version in the profile.

• Assigned – If the profile is assigned to one or more groups.

• Support: The status of the feature update:

  • Supported – The feature update version is in support and can deploy to devices.
  • Support Ending - The feature update version is within two months of its support end date.
  • Not supported – Support for the feature update has expired and it no longer deploys to devices.

• Support End Date – The end of support date for the feature update version.

Note

The date provided is for the Enterprise and Education editions of Windows. To find the support dates for other editions supported by Windows Autopatch, see the Microsoft Product Lifecycle site.

Selecting a profile from the list opens the profiles Overview pane where you can:

• Select Delete to delete the policy from Intune and remove it from devices.
• Select Properties to modify the deployment. On the Properties pane, select Edit to open the Deployment settings or Assignments, where you can then modify the deployment.

Note

The End user update status Last Scanned Time value will return 'Not scanned yet' until an initial user logs on and Update Session Orchestrator (USO) scan is initiated. For more information on the Unified Update Platform (UUP) architecture and related components, see Get started with Windows Update.

There are multiple options to get in-depth reporting for Windows 10/11 updates with Intune. Windows update reports show details about your Windows 10 and Windows 11 devices side by side in the same report.

To learn more, see Intune compliance reports.

• Use Windows update rings in Intune
• Use Windows update compatibility reports
• Use Windows update reports for Windows 10/11 updates
• Also see Windows Autopatch in the Windows deployment content for an alternative solution

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4