How updates are handled in Microsoft Managed Desktop
Microsoft Managed Desktop connects all devices to a modern cloud-based infrastructure. Keeping Windows, Office, drivers, firmware, and Microsoft Store for Business applications up to date is a balance of speed and stability. Deployment groups will be used to ensure operating system updates and policies are rolled out in a safe manner.
Updates released by Microsoft are cumulative and are categorized as quality or feature updates. For more information, see Windows Update for Business: Update types.
Microsoft Managed Desktop uses four Azure AD groups to manage updates:
- Test: Used to validate Microsoft Managed Desktop policy changes, operating system updates, feature updates, and other changes pushed to the tenant. There should not be any end users placed in the test group. The test group is exempt from any established service level agreements and end-user support. This group is available for use to validate compatibility of applications with new policy or operating system hanges.
- First: Contains early software adopters and devices that could be subject to pre-release updates. Devices in this group might experience outages if there are scenarios which were not covered during testing in the test ring.
- Fast: Prioritizes speed over stability. Useful for detecting quality issues before they are offered to the Broad group. This group serves as a next layer of validation but is generally more stable than the Test and First groups.
- Broad: Last group to have feature and quality updates available. This group contains the majority of users in the tenant, and therefore favors stability over speed in deployment. Testing of apps should be done here as the environment is most stable.
If you need to move a user to a different update group, submit a support request. See Support for Microsoft Managed Desktop for more information on submitting support requests. If you move a user yourself, the move will be reverted.
For more information roles and responsibilities with these deployment groups, see Microsoft Managed Desktop Roles and responsibilities
How update deployment works:
- Microsoft Managed Desktop deploys a new feature or quality update according the schedule specified below.
- During deployment, Microsoft Managed Desktop monitors for signs of failure or disruption (based on diagnostic data and the end-user support system). If any are detected, then the deployment to all current and future groups is immediately paused.
- Example: if an issue is discovered while deploying a quality update to the First group, then update deployments to First, Fast, and Broad will all be paused until the issue is resolved.
- Compatibility issues can be reported by filing a ticket in the Microsoft Managed Desktop Admin portal.
- Feature and quality updates are paused independently. Pause is in effect for 35 days by default, but can be reduced or extended depending on whether the issue is remediated.
- Once the groups are un-paused, deployment resumes according to the schedule below.
- This deployment process applies to both feature and quality updates, though the timeline varies for each.
|Update deployment settings|
|Quality updates for operating system||0 days||0 days||0 days||3 days|
|Feature updates for operating system||0 days||30 days||60 days||90 days|
|Drivers/firmware||Follows the schedule for quality updates|
|Anti-virus definition||Updated with each scan|
|Office 365 ProPlus||Follows Office's Monthly Channel|
For more information about the Monthly Channel for Office 365 ProPlus, see Overview of update channels for Office 365 ProPlus.
These deferral periods are intentionally designed to ensure high security and performance standards for all users. Furthermore, based on data gathered across all Microsoft Managed Desktop devices and the varying scope and impact of updates, Microsoft Managed Desktop reserves flexibility to modify the length of the above deferral periods for any and all deployment groups on an ad hoc basis.
Microsoft Managed Desktop conducts an independent assessment of each Windows feature release to evaluate its necessity and usefulness to its managed tenants. Consequently, Microsoft Managed Desktop might or might not deploy all Windows feature updates.
Windows Insider Program
Microsoft Managed Desktop does not support devices that are part of the Windows Insider program. The Windows Insider program is used to validate pre-release Windows software and is intended for devices that aren't mission critical. While this is an important Microsoft initiative, it is not intended for broad deployment in production environments.
Any devices found with Windows Insider builds might be put into the Test group and will be exempt from update service level agreements and end-user support from Microsoft Managed Desktop.
We use Delivery Optimization for all operating system and driver updates. This minimizes the download size from the Windows Update service by seeking updates from peers within the corporate network.
Učitavanje povratnih informacija...