Workspace ONE UEM OS Update Management

January 26, 2021   |   by bgarmon

This page was last updated May 6 2021

VMware’s Operational Tutorial for Managing Updates for Windows 10 was re-written for 2021 (click here to read it) to offer updated guidance around the process of managing OS updates using Workspace ONE UEM, but the update lost a lot of the technical configuration for how to put the ideas into practice. If you’re wanting to Test the ideas proposed in the guide you’re going to need do a bit more configuration. Don’t worry, it’s only 6 steps to success! 

Design Goals: 

With any project it helps to define clear goals at the start to understand what knobs and switches in the products need to be configured. The end goal of following this blog is a Workspace ONE UEM OS Updates configuration that achieves the following:

  • Update Windows 10 using Workspace ONE UEM for Domain joined devices, Workgroup managed devices, and Azure AD joined devices. 
  • Leverage Microsoft’s concept of Distribution Rings to spread out the updates to smaller groups of devices to ensure the updates cause minimal disruption should new bugs be introduced. This will be done using 2-Day, 5-Day, and 10-Day install and reboot deferrals.
  • Include Insider Preview Builds
  • Allow users to defer device reboots

Getting Started:

You’ll need the following before getting started:

  • Ability to create Active Directory Users and Groups
  • Setting up Azure AD is not part of this guide, but it is expected to be in place to test Azure AD joined devices.
  • Workspace ONE UEM Console with ACC and permissions within UEM to the root OG, permissions to add User Groups, Create Assignment Groups, and Create Policies
  • Windows 10 computing devices: physical or virtual is fine just make sure the device can be factory reset
  • A login account and password for my.vmware.com to access VMware’s Policy Builder
  • I highly recommend you download and run the Powershell for Auto-Tagging of Devices using Auto Tags
  • Head over to Brooks Peppin’s Blog and read Windows 10 Feature Upgrades Full Control .
    The section “Configure and Deploy Profile with UEM” is where you will find the link to download the Ring 1, 2 and 3 XML files. I’m borrowing a number of his ideas. Come back once you are done reading his page.

Step 1: Configure Active Directory Users in Active Directory

Pick/Create three to five user accounts in Active Directory, each having an email address. These accounts will be used to assign the Ring Distribution. I’ll use the Avengers for my accounts. In my environment the number of users I’m creating is limited by the amount of Microsoft Azure licenses I’m willing to pay for:

  • TStark
  • SRogers
  • PParker
  • BGarmon (honorary member)

Bonus: In the Workspace ONE UEM Console create a basic user account named Vision which will be used to enroll Workgroup joined computers.

Step 2: Configure Active Directory User Groups in Active Directory

Pick/Create 7 User Groups in AD then add members as follows:

  • HR Members: SRogers
  • Sales Members: TStark
  • Support Members: BGarmon and Pparker
  • All Employees Members: User Group HR + Sales + Support 
  • WU Ring 1 Members: Support
  • WU Ring 2 Members: HR
  • WU Ring 3 Members: Sales

Step 3: Import AD User Groups in Workspace ONE UEM Console

In Workspace ONE UEM Console > Accounts > User Groups > List View > Click Add > Add User Group  and add each of the 7 groups you created in the previous step.

Step 4: Create Smart Groups in Workspace ONE UEM Console:

Smart Groups do not support nesting of SmartGroups making this part a bit more painful then it should be. From the Workspace ONE UEM Console > Groups & Settings > Groups > Assignment Groups > Add Smart Group and follow the format below:

Smart Group NameType:
Criteria or
Devices or Users
Filters Used
WU - Azure AD MachinesCriteriaEnrollment Category > Selected > AAD Enrolled
WU - Insiders Preview BuildDevices or UsersPick a Device.
TestPatch0 is the PC I use
WU - Ring 1CriteriaOrganization Group - All
User Group > Selected > WU Ring 1
Platform and Operating Systems > Windows Desktop Equals Any
WU - Ring 2CriteriaOrganization Group - All
User Group > Selected > WU Ring 2
Platform and Operating Systems > Windows Desktop Equals Any
WU - Ring 3CriteriaOrganization Group - All
User Group > Selected > WU Ring 3
Platform and Operating Systems > Windows Desktop Equals Any
WU - Computers In Workgroup Devices or UsersPick a device that is in a Workgroup
InWorkgroup is the PC I'm using
All Dell Windows 10CriteriaOrganization Group - All
Tags > Dell
All Microsoft Surface DevicesCriteriaOrganization Group - All
Tags > Surface Book 3 and Surface Pro 4
(include any other Surface tags in your environment)
All Windows 10 DevicesCriteriaOrganization Group > All
Platform and Operating System > Windows Desktop > Any > Any

Step 5: Create Windows Update for Business Profiles in Workspace ONE UEM:

As of UEM 2101, the Windows 10 Device Profile includes a payload named “Windows Updates.” Do not use this payload. Instead create a new Profile and use Custom Settings to configure how Windows Update for Business will behave. Use the XML downloaded from Brooks Peppin’s blog to create the device Profiles below. That link again is https://brookspeppin.com/2020/08/26/windows-10-feature-upgrades-full-control/ and you’re scrolling down to the section titled “Configure and Deploy Profile with UEM.”

After following his blog you should end up with:

Profile Name: WU – Ring 1 using Smart Group WU Ring 1

Profile Name: WU – Ring 2 using Smart Group WU Ring 2

Profile Name: WU – Ring 3 using Smart Groups – WU Ring 3 and Computers in Workgroup and Azure AD Enrolled

In addition to the 3 Rings add the next two to cover Workgroup and Insider Preview Builds: 

Profile Name: WU – Workgroup Joined Machines* using Smart Group – WU – Computers In Workgroup and Excluded Groups – WU – Insiders Preview Builds & WU – Ring 1 & WU – Ring 2 & WU – Ring 3

WU – Insiders Preview Build using Smart Group – “WU – Insiders Preview Builds”

For the visual learners like me reading this, here’s what this should look like in the end:

The end result of building the profiles

For the Insiders Build the idea is to get the updates as fast as possible and install them as brute force as possible. Try these Custom settings to start but be prepared to tweak this one: 

Install Settings:

<Replace>
  <CmdID>6ada0015-7698-4ad4-b89e-48fa407abab9</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/AllowAutoUpdate</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data>1</Data>
  </Item>
</Replace>
<Replace>
  <CmdID>8de6da7a-4208-433f-96ae-c933abe01126</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/AllowMUUpdateService</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data>1</Data>
  </Item>
</Replace>
<Replace>
  <CmdID>f9d71ce3-1c64-4913-9c2c-fbf676e61da5</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/BranchReadinessLevel</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data>2</Data>
  </Item>
</Replace>
<Replace>
  <CmdID>e490a4e1-a85e-475b-86bc-8a2cf4bf5ff1</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/ConfigureDeadlineForFeatureUpdates</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data>1</Data>
  </Item>
</Replace>
<Replace>
  <CmdID>25f60c06-a461-4d39-ab38-496f95127b22</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/ConfigureDeadlineGracePeriod</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data>1</Data>
  </Item>
</Replace>
<Replace>
  <CmdID>3aeafea3-7f61-4570-ba5a-54c3876061e6</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/ConfigureFeatureUpdateUninstallPeriod</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data>14</Data>
  </Item>
</Replace>
<Replace>
  <CmdID>7852e415-5728-4fde-9cf9-c0268347a5ab</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/DeferFeatureUpdatesPeriodInDays</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data>0</Data>
  </Item>
</Replace>
<Replace>
  <CmdID>2e15a1f9-b042-4161-b296-5ee8fcc3d9f6</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/DeferQualityUpdatesPeriodInDays</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data>2</Data>
  </Item>
</Replace>
<Replace>
  <CmdID>4f7cf4e4-eeb3-4f08-b912-50c8e159859f</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/DeferUpdatePeriod</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data>0</Data>
  </Item>
</Replace>
<Replace>
  <CmdID>e9f01951-d5e4-4327-9980-1eb578ebe3d4</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/DeferUpgradePeriod</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data>0</Data>
  </Item>
</Replace>
<Replace>
  <CmdID>e7302c5e-78c0-407f-8c84-7e854085c472</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/ManagePreviewBuilds</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data>2</Data>
  </Item>
</Replace>
<Replace>
  <CmdID>f04ca483-85e6-45e8-8058-61c727bdf3d1</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/RequireUpdateApproval</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data>0</Data>
  </Item>
</Replace>
<Replace>
  <CmdID>7893c2e9-6a59-496d-9f61-af8aed99ae5f</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/ScheduleImminentRestartWarning</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data>15</Data>
  </Item>
</Replace>
<Replace>
  <CmdID>32208bc2-47c5-4ad5-bd6c-c092de994fc6</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/ScheduleRestartWarning</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data>2</Data>
  </Item>
</Replace>

Here’s the Remove Settings:

<Delete>
  <CmdID>6ada0015-7698-4ad4-b89e-48fa407abab9</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/AllowAutoUpdate</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data></Data>
  </Item>
</Delete>
<Delete>
  <CmdID>8de6da7a-4208-433f-96ae-c933abe01126</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/AllowMUUpdateService</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data></Data>
  </Item>
</Delete>
<Delete>
  <CmdID>f9d71ce3-1c64-4913-9c2c-fbf676e61da5</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/BranchReadinessLevel</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data></Data>
  </Item>
</Delete>
<Delete>
  <CmdID>e490a4e1-a85e-475b-86bc-8a2cf4bf5ff1</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/ConfigureDeadlineForFeatureUpdates</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data></Data>
  </Item>
</Delete>
<Delete>
  <CmdID>25f60c06-a461-4d39-ab38-496f95127b22</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/ConfigureDeadlineGracePeriod</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data></Data>
  </Item>
</Delete>
<Delete>
  <CmdID>3aeafea3-7f61-4570-ba5a-54c3876061e6</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/ConfigureFeatureUpdateUninstallPeriod</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data></Data>
  </Item>
</Delete>
<Delete>
  <CmdID>7852e415-5728-4fde-9cf9-c0268347a5ab</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/DeferFeatureUpdatesPeriodInDays</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data></Data>
  </Item>
</Delete>
<Delete>
  <CmdID>2e15a1f9-b042-4161-b296-5ee8fcc3d9f6</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/DeferQualityUpdatesPeriodInDays</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data></Data>
  </Item>
</Delete>
<Delete>
  <CmdID>4f7cf4e4-eeb3-4f08-b912-50c8e159859f</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/DeferUpdatePeriod</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data></Data>
  </Item>
</Delete>
<Delete>
  <CmdID>e9f01951-d5e4-4327-9980-1eb578ebe3d4</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/DeferUpgradePeriod</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data></Data>
  </Item>
</Delete>
<Delete>
  <CmdID>e7302c5e-78c0-407f-8c84-7e854085c472</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/ManagePreviewBuilds</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data></Data>
  </Item>
</Delete>
<Delete>
  <CmdID>f04ca483-85e6-45e8-8058-61c727bdf3d1</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/RequireUpdateApproval</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data></Data>
  </Item>
</Delete>
<Delete>
  <CmdID>7893c2e9-6a59-496d-9f61-af8aed99ae5f</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/ScheduleImminentRestartWarning</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data></Data>
  </Item>
</Delete>
<Delete>
  <CmdID>32208bc2-47c5-4ad5-bd6c-c092de994fc6</CmdID>
  <Item>
    <Target>
        <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/ScheduleRestartWarning</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data></Data>
  </Item>
</Delete>

Step 6 – Supply Windows 10 Devices to test

Congratulations!  The configuration is complete and you are ready to enroll devices and begin testing. 

At the time of this writing Windows 10 20H2 is the latest feature update available. It’s going to be a poor testing experience if all of your devices are already running 20H2 so head over to MSDN and download a few previous builds of Windows 10. I recommend starting with UEM 1909 or above. This will allow you to experience Patch Tuesday, Feature Updates, Driver updates and all the other wonders of Windows Update for Business as part of your testing experience. 


At a minimum, I recommend 5 devices to start. Getting started testing is as simple as installing Windows 10, enrolling into Workspace ONE UEM and waiting for the OS updates to apply.

I find it helpful to record the computer names assigned to each end user as a quick reference:

TStark is using computer name TestPatch4

SRogers is using computer name TestPatch2 and TestPatch5

PParker is using computer name TestPatch1 and TestPatch7

Congratulations on configuring Windows Update management using Workspace ONE UEM’s modern management approach.

Need more control over updates?

What is implemented above is VMWare’s Modern Management approach to OS Patch management where IT Administrators do not filter or control specific Windows Updates but instead simply manage spacing out the rollouts based on Distribution Rings. The Set and Forget it approach. 

Many organizations require more control over this process. By no means is what follows the only method that works, but after a few months of trial and error what is described below seems to work pretty well. Remember that this approach will require DAILY visits to the UEM Console Device Updates section because new updates will be showing up all the time and each new update requires approval. It’s a lot of work to go this approach for what I will argue is a small benefit but it can be done.

If you would like to test having more control over which updates are able to be installed create or edit the Profiles for the “WU – Device Ring X” to add RequireUpdateApproval with a value of 1 to the Custom Settings. 

<Item>
    <Target>    <LocURI>./Device/Vendor/MSFT/Policy/Config/Update/RequireUpdateApproval</LocURI>
      </Target>
    <Meta>
      <Format xmlns="syncml:metinf">int</Format>
      <Type>text/plain</Type>
    </Meta>
    <Data>1</Data>
  </Item>

This setting will prevent the updates from installing on the device until a Workspace ONE UEM Administrator logs into the Workspace ONE UEM Console and approves the update using the Devices > Devices Updates section of the console. 

Think about Assignment aka Approval like this: The Windows 10 device asks Windows Update for Business for a list of updates, gets a reply with a list, then has to ask Workspace ONE UEM if it’s ok to install the list that was just provided. If there is a Smart Group Assigned to the update, the answer back to the device is YES and the update is installed. 

Just because the update is Assigned to a Smart Group, aka Approved, it does not mean it will install. For example if you assign the OS Update “2020-11 Cumulative update Preview for Windows 10 Version 20H2 for x64-based Systems (KB4586853)” to the Smart Group “All Windows 10” and the Windows 10 device happens to be running Windows 10 UEM Version 2004, Windows will ignore the update and not install it because the actual update is specific to Windows 10 version 20H2. 

A final note about Assignments: This feature does not function like Windows Software Update Services (WSUS) and Windows 7 where you can individually approve 12 out of 12 updates on Patch Tuesday. Instead Assignments are based on Categories that Microsoft has defined as part of Windows Update for Business (WuFB). Behind the GUI, each category is assigned a GUID and when troubleshooting it’s helpful to know the GUIDS. Here is a breakdown of the Classification Categories to their GUIDs:

Now on to the assignments:

The following Smart Group Assignment, aka Approval, has worked well for me with this approach: 

Filter the Windows Devices Updates in UEM by Classification:

Classification Application 

I’ve never seen anything show up here. If you do let me know what you see but if something were to show up I would assign it to the Smart Group “All Windows 10”

Classification Connectors

I’ve never seen anything show up here. If you do let me know what you see but if something were to show up I would assign it to the Smart Group “All Windows 10”

Classification Critical Updates

Assign to Smart Group “WU – Ring 1” for the first week, come back in a week and add “WU – Ring 2”, come back the next week and add “WU – Ring 3” If all is well, on Week 3 change the assignment to “All Windows 10”

Classification Definition Updates

Assign to Smart Group “All Windows 10”

Classification Developer Kits

I’ve never seen anything show up here. If you do let me know what you see but if something were to show up I would assign it to the Smart Group “All Windows 10”

Classification Drivers

If you’re using Microsoft Surface devices, or OEM’s like Dell or Lenovo this Driver section will likely be filled with a number of OEM specific drivers. This is where that optional SmartGroup above comes into play. Using Device Tags use SmartGroups to assign drivers to the correct devices. For generic drivers assign them to “All Windows 10”

Classification Feature Packs

I’ve never seen anything show up here. If you do let me know what you see but if something were to show up I would assign it to the Smart Group “All Windows 10”

Classification Feature Updates

A populated Feature Updates

If you’re following the Ring Deployment method above the idea is to approve the latest Insider Preview Builds to your test device, then Approve the next Feature Pack to Ring 1. Ring 2 and 3 should be whatever matches your production Win10 Build. All others Feature Updates listed should remain set to Not Assigned aka Not Approved.

Classification Guidance

I’ve never seen anything show up here. If you do let me know what you see but if something were to show up I would assign it to the Smart Group “All Windows 10”

Classification OS Updates

Assign to Smart Group “WU – Ring 1” for the first week, come back in a week and add “WU – Ring 2”, come back the next week and add “WU – Ring 3” If all is well, on Week 3 change the assignment to “All Windows 10”

Classification Security Updates

Assign to Smart Group “WU – Ring 1” for the first week, come back in a week and add “WU – Ring 2”, come back the next week and add “WU – Ring 3” If all is well, on Week 3 change the assignment to “All Windows 10”

Classification Service Packs

I’ve never seen anything show up here. If you do let me know what you see but if something were to show up I would assign it to the Smart Group “All Windows 10”

Classification Tools

I’ve never seen anything show up here. If you do let me know what you see but if something were to show up I would assign it to the Smart Group “All Windows 10”

Classification Unknown

So this one we don’t like to talk about. It’s created by Workspace ONE UEM as a result of a design flaw. There are two approaches – ignore them completely or approve them all using the Smart Group “All Windows 10”.

Classification Update Rollups

I recommend you assign to Smart Group “All Windows 10”

Tags:

Leave Your Comment