kkbic
Contributor
Contributor

How to upgrade to Windows 11

Hi,

I am new to WS1 and looking for suggestions on how to upgrade our Windows 10 devices to Windows 11 with Workspace One. Currently, we set the windows update branch to Windows 10 "Semi-Annual Channel" from Microsoft Update Service and install updates automatically using a Profile. 

To upgrade a set of the device group to Windows 11, what settings should I change or configure in the Windows Update payload so they could upgrade to Win 11 and start receiving updates as they are currently?

Thanks!

0 Kudos
3 Replies
hard199
Contributor
Contributor

You can set product version parameter using custom profile as below, 

<Replace>
<CmdID>1</CmdID>
<Item>
<Target>
<LocURI>./Vendor/MSFT/Policy/Config/Update/ProductVersion</LocURI>
</Target>
<Meta>
<Format xmlns="syncml:metinf">chr</Format>
</Meta>
<Data>Windows 11</Data>
</Item>
</Replace>

kkbic
Contributor
Contributor

Thank you @hard199, for the response. Now I know where to enable the version. 

Questions:

This is what we currently have it set to for Windows 10:

<Replace>
<CmdID>1</CmdID>
<Item>
<Target>
<LocURI>./Device/Vendor/MSFT/Policy/Config/Update/TargetReleaseVersion</LocURI>
</Target>
<Meta>
<Format xmlns="syncml:metinf">chr</Format>
<Type>text/plain</Type>
</Meta>
<Data>21H1</Data>
</Item>
</Replace>

*I do not see anything related to Win 10 was mentioned in the above xml, except the 21H1? 

*Can I go with the TargetReleaseVersion for Windows 11 or do I have to use the ProductVersion

You mentioned, <Data>Windows 11</Data> but where do I specify the Windows 11 version number? like 21H2 etc?

Thank you!

0 Kudos
MatthiasJoestl
Contributor
Contributor

you need 2 entries.

One is TargetReleaseVersion:

Target: OMA DM Client

Content:

<Replace>
<CmdID>455467546</CmdID>
<Item>
<Target>
<LocURI>./Vendor/MSFT/Policy/Config/Update/TargetReleaseVersion</LocURI>
</Target>
<Meta>
<Format xmlns="syncml:metinf">chr</Format>
</Meta>
<Data>21H2</Data>
</Item>
</Replace>

the other entry is the Windows ProductVersion. But unfortunately it did not work the same way as the other profile.
So we created a direct registry replacement custom profile with

Target:  Workspace One intelligent Hub (NOT OMA DM Client)

Content:

<wap-provisioningdoc id="4ee19c79-6a7a-4727-91db-c1c55025deca" name="customprofile">
<characteristic type="com.airwatch.winrt.registryoperation" uuid="cd83e639-24cd-4108-954e-f2ab3263fe5e">
<parm RegistryPath="HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" Action="Replace">
<Value Name="ProductVersion" Data="Windows 11" Type="String" />
</parm>
</characteristic>
</wap-provisioningdoc>

 

0 Kudos