Managing Updates for Windows 10: VMware Workspace ONE Operational Tutorial
The VMware Workspace ONE UEM Operational Tutorial: Managing Windows 10 Updates consists of a series of exercises that walk through managing Windows 10 updates with Workspace ONE UEM.
This operational tutorial provides you with discussions and exercises to help with your existing VMware Workspace ONE® production environment. VMware provides operational tutorials to help you with
- Common procedures or best practices
- Complex manual procedures
Note: Before you begin any operational tutorial, you must first deploy a production environment. For information about deployment, see the VMware Workspace ONE Documentation.
This operational tutorial is intended for IT professionals and Workspace ONE administrators of existing production environments. Both current and new administrators can benefit from using this tutorial. Familiarity with networking and storage in a virtual environment is assumed, including Active Directory, identity management, and directory services. Knowledge of additional technologies such as VMware Identity Manager™ and VMware Workspace ONE® UEM (unified endpoint management), powered by VMware AirWatch, is also helpful.
Configuring Update Management for Windows 10
This exercise introduces you to managing Windows 10 updates in Workspace ONE. The procedures are sequential and build upon one another, so make sure that you complete each procedure in this section before going to the next procedure.
Before you can perform the procedures in this exercise, you must satisfy the following requirements:
- Workspace ONE UEM Console version 9.3 and later, with admin credentials
Important: Do not access the Workspace ONE UEM Console from the same machine you are managing.
- Active Directory integrated with Workspace ONE
- Enrolled virtual machine or spare Windows 10 Pro+ Device v1703+
- Administrative rights to the virtual machine or spare Windows device
- Telemetry Data enabled — verify Active Directory GPO or other local policies are not blocking this feature
- Active Directory set up with the following test Organization Units (or User Groups):
- Early Adopters
- Technical Field Engineers
Understanding Patch Management
The Workspace ONE UEM update service for Windows 10 provides tailored functionality to address the unique constraints of mobility and the cloud. Traditional operating system upgrades use a wipe-and-replace model. In contrast, the update-as-a-service model pushes periodic operating system and feature updates. Windows 10 updates occur on a frequent and dynamic basis to ensure that end users always have access to up-to-date operating system features.
Windows 10 Patch Management Options
Deploying Windows 10 fixes, patches, and updates on a variety of client servicing plans creates overhead. By using branches, you can create a customized deployment schedule based on preference and update sensitivity.
Figure: Windows 10 Patch Management Options
Review the following descriptions to understand the available patch management options.
|Update Branch||Description||Feature Updates||Quality Updates||Use Case|
|Windows Insider Build - Fast||Among the first to receive development builds from Microsoft; ability to provide direct feedback to Microsoft||Not supported||Not supported||Used to provide feedback to Microsoft before builds are moved to slow ring|
|Windows Insider Build - Slow||More stable than fast ring and includes fixed reported during fast ring||Not supported||Not supported||Used to provide feedback to Microsoft before builds are moved to release ring|
|Release Windows Insider Build||Close to public release but still early access, not on the development branch||Not supported||Not supported||Used to provide feedback to Microsoft before builds are moved to public builds; IT pros and other interested employees|
|Semi-Annual Channel (Targeted)||Semi-Annual Channel||Not supported||Not supported||Pilot deployments used for testing feature updates and for users such as developers. Use various teams for a wide sample set.|
|Semi-Annual Channel||Semi-Annual Channel||0-180 days||0-30 days||Board deployment of features, you can choose from the ranges to build your distribution rings across organization|
Logging In to the Workspace ONE UEM Console
To perform most of the steps in this exercise, you must first log in to the Workspace ONE UEM Console.
1. Launch Chrome Browser
On your desktop, double-click the Google Chrome icon.
3. Authenticate In to the Workspace ONE UEM Console
- Enter your Username. This is the name provided in the activation email.
- Enter your Password. This is the password provided in the activation email.
- Click the Login button.
Note: If you see a Captcha, be aware that it is case sensitive.
Syncing Active Directory Organization Units to Workspace ONE UEM
Leverage existing Active Directory Organization Units (OUs) or User Groups to create distribution rings in Workspace ONE UEM.
Note: Organizations that used Active Directory to create distribution rings can skip this step.
2. Open User Group Settings
- Select Add.
- Select Add User Group.
3. Add a User Group
- Select Directory as the Type.
- Select Organizational Unit for External Type.
R&Dinto the Search Text field.
- Click Search.
- Click Save.
4. Add the Remaining Organization Units
Repeat step 3 for the remaining Organization Units (or User Groups). When complete, your User Group List View should resemble the screenshot shown.
Creating Distribution Rings Using Smart Groups
2. Add a Smart Group
Click the Add Smart Group tab.
3. Configure Smart Group Settings
Production (Broad) Distribution Ringas the Name.
- Expand the User Group drop-down menu.
- Click Selected.
- Deselct Early Adopters and IT, who will be added to the other rings.
- Click Save.
Note: Previously enrolled devices that match the criteria will appear in a list on the right.
4. Configure Remaining Smart Groups
Repeat steps 2 and 3 to create the remaining distribution ring Smart Groups. When complete, your Smart Groups List View should resemble the screenshot above.
After creating Smart Groups for your distribution rings, you are ready to create a Windows Update profile.
Creating an Updates Profile
1. Navigate to Profile Settings
In the upper-right corner of Workspace ONE UEM Console:
- Select Add.
- Select Profile.
1.1. Select the Platform
Select the Windows icon.
Note: Make sure that you select Windows and not Windows Rugged.
1.2. Select the Device Type
Select Windows Desktop.
1.3. Select Profile Context
Select Device Profile.
2. Define the General Settings
- Select General if it is not already selected.
- Enter a profile name such as
Windows Update Production Ringin the Name text box.
- Copy the profile name into the Description field.
- Switch Allow Removal to Never to keep users from removing this profile in the self-service portal.
- If necessary, scroll down to Assigned Groups. Click the field and select Production (Broad) Ring from the list of Assignment Groups that populate.
Note: Do not click Save & Publish at this point. This interface allows you to move around to different payload configuration screens before saving.
3. Configure the Updates Payload
3.1. Open the Update Payload
- Select the Windows Updates payload in the Payload section on the left.
- Click the Configure button to continue setting the Windows Updates payload.
Note: When initially setting a payload, a Configure button will show to reduce the risk of accidentally setting a payload configuration.
3.2. Configure Branching and Deferral Settings
Configure Branching and Deferral settings to determine the timeline for applying updates.
- Select Microsoft Update Service as the Windows Update Source.
- Select Semi-Annual Channel as the Update Branch.
120into the Defer Feature Updates Period in Days text box. Feature Updates add new functionality two to three times per year.
- Leave Pause Feature Updates Disabled.
14into the Defer Quality Updates Period in Days text box. Quality Updates provide security and reliability fixes at least once a month.
- Leave Pause Quality Updates Disabled.
- For 1511 or earlier versions only, select Enable Settings for Previous Windows versions and configure the following settings:
- Defer New Features: 6 Months
- Defer New Updates: 2 Weeks
- Keep Pause Deferrals Disabled.
Note: Deferment Periods are only available for the Semi-Annual Channel branch.
3.3. Configure Update Behavior
- Scroll down to the Update Installation Behavior section.
Review the Windows recommended settings, which populate by default. Edit these settings to reflect corporate policies and preferences, or leave them as-is to align with the steps in this exercise.
- Automatic Updates — Use Install Updates Automatically reboots devices and applies updates as soon as they become available.
- Active Hours Max Range In Hours — Block out an 18 hour range during which the device cannot reboot or restart to apply updates. Then, specify the start time and end time. Paired with automatic updates, this prevents random reboots from hindering end-user productivity.
- Auto Restart Deadline Period In Days — Reboot for updates becomes mandatory after 7 days.
- Auto Restart Notification Schedule in Minutes — Issue a notifications 15 minutes prior to an auto-restart.
- Auto Restart Required for Notification Dismissal — Dismiss notifications using auto-dismissal.
- Engaged Restart Deadline in Days - Automatically schedule and execute a restart outside of active hours after 2 days.
- Engaged Restart Snooze Schedule In Days — Allow users 3 days to snooze engaged restart reminders.
- Schedule Restart Warning In Hours — Issue a warning 4 hours before an auto-restart.
- Schedule Imminent Restart Warning In Minutes — Issue a final warning 15 minutes before an auto-restart.
3.4. Configure Update Policies
- Scroll down to the Update Policies section and configure more granular update settings as dictated by corporate policies and preferences.
22as the Update Scan Frequency In Hours.
- Disable the Dual Scan For Deferral Policies to prevent dual scans and allow users to configure as many deferral policies as necessary.
- Set the Mobile Operator App Download Limit to DoNotIgnore to disable unlimited downloading over a cellular network for apps and their updates.
- Set the Mobile Operator Update Download Limit to DoNotIgnore to disable unlimited downloading over a cellular network for OS updates.
- Since this profile applies to standard users, allowing insider builds is likely inappropriate, set Insider Builds to Not Allowed. However, for the profile that applies to the internal IT department user group, set Insider Builds to Allowed, as these users likely require access to the Windows Insiders Program.
3.5. Configure Admin Approved Updates
- Scroll down to Administrator Approved Updates and configure which updates can install on end-user devices.
- Select Enable for Require Update Approval to configure approval for update groups.
- Select Allowed for Auto-Approved Updates to display the list of available update groups and configure automatic approval on a group by group basis.
- Review the recommended configurations which auto-populate in the Workspace ONE UEM Console.
- Allowed — Install automatically after the deferment period during approved hours.
- Not Allowed — Requires manual approval in the Workspace ONE UEM Console on a KB by KB basis.
3.6. Configure Delivery Optimization
- Scroll down to the Delivery Optimization section, and configure settings to mitigate potential bandwidth issues.
- Select Allowed for Peer-to-Peer Updates to create an internal device network that enables devices to share updates with each other.
- Select Use Peers on the Same NAT Only as the Allowed Peer-to-Peer Method for downloads of Windows updates, apps and app updates.
- Do Not Limit peer usage to members with the same group ID.
- Select Not Allowed for VPN Peer Caching to prevent devices connected to the domain network via VPN from peer caching.
40as the Minimum Battery Required For Peer Uploads (%). Uploads will automatically pause when the battery level drops below the specified minimum.
Note: Consider limiting peer usage by Group ID when using geographically based distribution groups. This establishes a NYC peer network for the New York City user group, and a Los Angeles peer network for the LA user group.
3.7. Configure Memory
- Scroll down to the Memory settings.
- Allow up to 10 GB as the Maximum Allowed Cache Size for delivery optimization,
- Specify 32 GB as the Minimum disk size for devices to use peer caching.
- Require 4 GB RAM as the Minimum RAM for devices to use peer caching.
- Require 4 MB as the Minimum Content File Size That Can Use Peer Caching.
%SystemDrive%as the Drive location used for peer cache by delivery optimization.
3.8. Configure Network
- Scroll down to Network settings.
0KiloBytes/second as the Maximum download bandwidth that a device will use.
500KiloBytes/sec as the Minimum QoS (Quality of Service or speed) for background downloads.
20GB as the maximum Monthly upload data cap (GB).
3.9. Publish the Profile
Using Workspace ONE UEM to Manage Windows 10 Updates
After configuring the updates profiles, you can manage distribution rings from the Workspace ONE UEM Console.
2. Manage Updates
Leverage this centralized view of all updates to:
- Discover all available updates.
- Link directly to Microsoft reference articles for each KB.
- Select and assign a KB or group of KBs to assignment groups.
- Find the installation or deployment status of an update.
Summary and Additional Resources
This tutorial shows you how to use Workspace ONE UEM to manage Windows 10 updates through a series of exercises.
Terminology Used in This Tutorial
The following terms are used in this tutorial:
|adaptive access||The ability to control access and authentication methods to sensitive apps based on a device’s managed status.|
|additive||Includes only changes developed after the latest version of the application or the last additive patch.|
|app dependencies||Applications required by the environment and devices to run the Win32 application.|
|app patches||Files that apply additive or cumulative fixes, updates, or new features to applications.|
|app transforms||Files that control application installation and can add or prevent components, configurations, and processes during the process.|
|app uninstall process||Scripts that instruct the system to uninstall an application under specific circumstances.|
|application store||A user interface (UI) framework that provides access to a self-service catalog, public examples of which include the Apple App Store, the Google Play Store, and the Microsoft Store.|
|auto-enrollment||Auto-enrollment simplifies the enrollment process by automatically enrolling registered devices following the Out-of-Box-Experience.|
|BitLocker||Full disk encryption available for Windows, focused on addressing data leakage or data theft scenarios from stolen, lost, or incorrectly decommissioned devices.|
|bring your own device (BYOD)||The process of providing secure access to corporate data, apps, and content on an employee-owned device without invading employee privacy to their personal data, apps, or content.|
|business mobility||The concept of being able to provide secure access to your business services, infrastructure, and content to enable your workforce to work remotely.|
|catalog||A user interface (UI) that displays a personalized set of virtual desktops and applications to users and administrators. These resources are available to be launched upon selection.|
|cloud||Asset of securely accessed, network-based services and applications. A cloud can also host data storage. Clouds can be private or public, as well as hybrid, which is both private and public.|
|conditional access||To provision access to a resource or service, based on user entitlements or roles.|
|container||The separation of corporate and personal data on employee-owned devices, allowing IT administrators to manage corporate applications and profiles without invading employee privacy or personal apps and content.|
|cumulative||Includes the entire application, including any changes since the latest version of the application, or the last patches.|
|data leakage protection||Software-controlled policies that determine how and where data can be transferred or shared to.|
|device enrollment||The process of installing the mobile device management agent on an authorized device. This allows access to VMware products with application stores, such as VMware Identity Manager.|
|Device Health Attestation||Module that gathers device health measurements and reports these measurements to the Health Attestation Service for evaluation.|
|enrollment||The process of allowing your device to be managed by the software-defined policies of the chosen enterprise mobility management provider.|
|enterprise mobility management||The concept of using software and policies to both secure and provide access controls for mobile devices.|
|files and actions||The combination of the files delivered to a device and the actions that file performs on the device. Files and actions cannot be assigned directly to a device. Instead, assign files and actions to a product, which then provisions to devices.|
|Health Attestation Services||Cloud service that evaluates health measurements from the device to determine the health state.|
|identity-as-a-service||Identity and access management services through the cloud to provide SSO identity federation and user-access provisioning.|
|identity provider (IdP)||A mechanism used in a single-sign-on (SSO) framework to automatically give a user access to a resource based on their authentication to a different resource.|
|mobile application management||The concept of managing access, deployment, and restrictions of mobile applications using software and services.|
|mobile device management
|The concept of managing mobile devices using software installed on an authorized device to monitor, manage, and secure end-user access to enterprise resources.|
|multi-factor authentication||Access control process that requires users to authenticate using more than one method of authentication by providing something the user knows (a password) and something the user has, such as a hardware token, smartcard, or phone, or something the user is, such as a fingerprint or retina.|
|one-touch login||A mechanism that provides single sign-on (SSO) from an authorized device to enterprise resources.|
|per-app VPN||Policies that allow individual apps to access VPN configurations without granting device-wide access to the VPN connection.|
|public app stores||Portals where users can access and obtain publically published applications, such as the iOS App Store and Google Play Store.|
|service provider (SP)||A host that offers resources, tools, and applications to users and devices.|
|smart groups||Groups that control which devices get which product, based on how the group is created.|
|step-up authentication||Restricting applications or services to require a stronger authentication method, depending on the sensitivity or severity of the resource.|
|unified endpoint management||A single platform that allows organizations to manage and secure every endpoint, any app, and content across deployment use cases.|
|virtual desktop||The user interface of a virtual machine that is made available to an end user.|
|virtual machine||A software-based computer, running an operating system or application environment, that is located in the data center and backed by the resources of a physical computer.|
|Windows Information Protection||Formerly Enterprise Data Protection (EDP), a Windows solution to assist in preventing data leakage without impeding the user experience.|
For more information about Workspace ONE, you can explore the following resources:
- VMware Workspace ONE Action Path
- VMware Workspace ONE product page
- VMware Workspace ONE Documentation
- VMware Identity Manager product page
- VMware Identity Manager Documentation
- VMware Workspace ONE UEM, powered by VMware AirWatch product page
- VMware Workspace ONE (formerly AirWatch) Documentation
- VMware Workspace ONE free trial
- VMware Workspace ONE Enterprise Edition Reference Architecture
- VMware End-User-Computing Blogs
- Workspace ONE UEM Hands-On Lab
About the Authors
This tutorial written by Josué Negrón, Sr. Solutions Architect, End-User-Computing Technical Marketing, VMware, and Hannah Jernigan, Technical Writer, End-User-Computing Technical Marketing, VMware, with appreciation and acknowledgement for considerable contributions from the following subject matter experts:
- Pedro Bravo, Deployments Subject Matter Expert, VMware AirWatch
- Ajay Padmakumar, T3 Support Subject Matter Expert, VMware AirWatch
- Varun Murthy, Product Line Manager, VMware AirWatch
- Nigitha Alugubelli, Sr. Product Manager, VMware AirWatch
- Jason Roszak, Director Product Management, VMware AirWatch
- Darren Weatherly, Sales Engineer, VMware AirWatch
- Robert Terakedis, Sr. Solutions Architect, EUC Technical Marketing, VMware
- Aditya Kunduri, Product Marketing Manager, EUC Mobile Marketing, VMware
The purpose of this tutorial is to assist you. Your feedback is valuable. To comment on this tutorial, contact VMware End-User-Computing Technical Marketing at firstname.lastname@example.org.