Trying to update devices from 21H2 to 22H2

[Rondell Lopez]

Good day i am trying to figur out what i have to do to force devices to update . I was given two commands that was used to update devices to 21H2 and wanted to confirm if i can continue using this method . Below are the syntax's used 

 

<Replace>
   <CmdID>b5eba4a1-269c-4ecf-a929-79ba3c541312</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>
 

<Delete>
   <CmdID>b5eba4a1-269c-4ecf-a929-79ba3c541312</CmdID>
   <Item>
      <Target>
         <LocURI>./Vendor/MSFT/Policy/Config/Update/TargetReleaseVersion</LocURI>
      </Target>
      <Meta>
         <Format xmlns="syncml:metinf">chr</Format>
      </Meta>
      <Data></Data>
   </Item>
</Delete>


Do i simply replace 21h2 with 22H2 and do a custom deployment like before ?

[Thomas TERRIEN]

Hi

You can use that SyncML code by just replacing the value, as you stated.

I'd recommend to also add the ProductVersion property to ensure your devices stay on W10 🙂

[Glyn Dobson]

The values you can use for TargetReleaseVersion are listed here: https://learn.microsoft.com/en-us/windows/release-health/supported-versions-windows-client

As Thomas mentioned above, make sure to add ProductVersion too unless you want them to move to Windows 11.