You are an IT engineer with 20 years of experience. Create simple answers. If asked for…
- User
You are an IT engineer with 20 years of experience. Create simple answers. If asked for code or a script, test it to eliminate bugs before delivering it. If asked for expertise, provide it in a simple manner. Your organisation is using RMM software "NinjaOne". This software is able to inject any type of PowerShell or Batch script without connecting to the device - those commands are always executed as System, so no admin rights are needed. Your organisation is based on O365 and you are Azure and Intune expert. Your task is: Schedule windows 10 to windows 11 update using Intune. All Users Windows devices are enrolled as company owned. We have injected Win 10 to Win 11 restrictions based on Registry key that can be lifted anytime. How to tackle this upgrade? I want to avoid that end user device will be auto rebooting - user should have option to control it. Give me the most efficiant options
Assistant
Here are the most efficient options to schedule Windows 10 to 11 upgrades through Intune while giving users control over reboots:
Option 1: Feature Update Policy (Recommended)
This is the cleanest approach using Intune's built-in capabilities.
Steps:
- In Intune, go to Devices > Windows > Feature updates for Windows 10 and later
- Create a new profile targeting Windows 11 (version 23H2 or 24H2)
- Configure these settings:
- Set "First compliance deadline" to give users time (e.g., 7-14 days)
- Enable "Allow user to pause Windows updates"
- Set grace period for restarts (e.g., 3-5 days)
- First, lift the registry restriction via NinjaOne script for pilot groups
- Assign the policy to those groups
User Experience: Users get notifications about the update and can schedule restarts within the grace period.
Option 2: Update Rings with Controlled Deployment
More granular control over the update process.
Steps:
- Create Update Ring policy in Intune
- Configure:
- Feature update deferral: 0 days (since you want immediate availability)
- Quality update deferral: As needed
- Update notifications: Show all notifications
- Auto-restart deadline: 7-14 days
- Engaged restart: Enabled (gives users more control)
- Use NinjaOne to remove registry blocks in phases
- Deploy update ring to unblocked devices
Option 3: Windows Update for Business + Registry Control
Best for phased rollouts with maximum control.
PowerShell script for NinjaOne to manage the upgrade:
# Remove Windows 11 block Remove-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" -Name "TargetReleaseVersion" -ErrorAction SilentlyContinue Remove-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" -Name "TargetReleaseVersionInfo" -ErrorAction SilentlyContinue # Configure user-friendly update behavior Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" -Name "NoAutoRebootWithLoggedOnUsers" -Value 1 -Type DWord Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" -Name "AlwaysAutoRebootAtScheduledTime" -Value 0 -Type DWord # Force update check Start-Process -FilePath "UsoClient.exe" -ArgumentList "StartInteractiveScan" -WaitBest Practice Recommendations:
- Start with pilot group (5-10% of devices)
- Use Intune's Update Compliance reports to monitor progress
- Create device groups based on departments for phased rollout
- Set up compliance policies to track upgrade status
- Configure notification templates to inform users about the upgrade
User Communication Template:
- Send email 1 week before their scheduled upgrade
- Include instructions on how to schedule restart
- Provide support contact information
The Feature Update Policy (Option 1) is most efficient because it's native to Intune, provides the best user experience, and requires minimal scripting.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.