When taking an S2D server offline for patching or other reasons, it is not only taking away the compute and memory for that server but also a portion of the storage pool. Care must be taken to keep your data safe and ensure quick resumption of production-level readiness to your cluster.

Visit Microsoft for the full description and latest information: https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/maintain-servers

Key Steps to reboot servers:

1. Open PowerShell as Admin.

2. Check to make sure the virtual disks are healthy by running Get-VirtualDisk.

3. Run Suspend-ClusterNode -Drain to move the VMs to another node.

4. Run to cleanly put the storage into maintenance mode. At this point writes to this node’s storage are still active until step 5 has been completed.

Get-StorageFaultDomain -type StorageScaleUnit | Where-Object {$_.FriendlyName -eq “<Node Name>”} | Enable-StorageMaintenanceMode

5. Run to verify the disks for the node are in maintenance mode. You should see “In Maintenance Mode, OK” under Operational Status.

Foreach($Node in (Get-ClusterNode).Name){$Node;Get-StorageNode -Name $Node*|Get-PhysicalDisk -PhysicallyConnected}

6. Reboot server.

7. Once you’re ready to put the server back into production, open PowerShell as Admin.

8. Run to put the storage back into production.

Get-StorageFaultDomain -type StorageScaleUnit | Where-Object {$_.FriendlyName -eq “<Node Name>”} | Disable-StorageMaintenanceMode

9. A storage job will initiate in the background to repair and resync the data. To check on the status, run (as Admin) Get-StorageJob  If it returns to a command prompt that means there are no jobs running. Do not reboot the next node until all of the jobs have been completed.

10. Run Get-VirtualDisk to verify the virtual disks are healthy after storage jobs complete. Wait until steps 9 and 10 have been completed before live migrating VMs back to this node as storage jobs will consume system resources potentially affecting the response time of your applications.

11. Run Resume-ClusterNode -Failback Immediate to put the cluster node back into production to handle VM workloads.

Alternative:

The steps to reboot each servers can take some time especially with post storage resync and repair. If you have the ability to shutdown the entire cluster this link will walk through the steps to make the entire process faster.

https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/maintain-servers#how-to-update-storage-spaces-direct-nodes-offline

How to Run Cluster Validation

1. Open Failover Cluster Manager

2. Right click on the cluster and select “Validate Cluster”

3. A ‘Validate a Configuration Wizard’ will open and select next to continue

4. Select “Run only tests I select” and select next to continue

5. Make sure “Storage” is unchecked. If you run cluster validation with storage, you will corrupt your data in your production environment

6. Select next to continue and the test will run. Once it finish open the Report to view the result.

How to Disable Cluster Quorum:

1. Open Failover Cluster Manager
2. Select the cluster
3. Right click on the cluster or select ‘More Action’ on the Actions panel on the right
   

   

4. Select ‘Configure Cluster Quorum Setting’
   

   

5. This will open the Quorum Wizard and select ‘Next’ to continue
6. Select the second options. ‘Select the quorum witness’
   

   

7. Next select the last options to disable the quorum witness. ‘Do not configure a quorum witness’
   

   

8. Once the witness is removed. Check the Failover Cluster Manager to make sure it is removed in the 'Cluster Core Resources’
   

   

How to Enable Cluster Quorum:

1. Open Failover Cluster Manager
2. Select the cluster
3. Right click on the cluster or select ‘More Action’ on the Actions panel on the right
   

   

4. Select ‘Configure Cluster Quorum Setting’
   

   

5. This will open the Quorum Wizard and select ‘Next’ to continue.
6. Select the second options. ‘Select the quorum witness’
   

   

7. Here you can select 3 different Quorum Witness:
   1. Disk Witness: will create a witness on a disk. This is not an option for Storage Space Direct (S2D) because it does not work. The option is there for Storage Space. It not recommended by DataON.
   2. File Share Witness: Will create a small file which will act as the witness. Recommend having the witness on another cluster, server, or workstation that is not on the cluster itself.
   3. Cloud Witness: will create a witness on the cloud. This requires a Azure account and subscription. This also require having constant internet connection for the witness to be active.

1. Once you select the Witness, select the path where the witness will lie.
   

   

2. Confirm the witness and select ‘Next
   
   
3. Once it is configure, you will reach the summary page and select ‘Finish’ to exit.
   

   

There are three high-level steps for migration of VMs from an existing cluster to a new cluster.

1. Setup new servers and storage and configure iSCSI access to new storage.
2. Setup Hyper-V and failover clustering.
3. Setup the CSV storage for the new cluster.

There are two methods by which you can migrate VMs from an existing cluster to a new cluster:

Option 1
You could transfer roles to the new cluster, but this does not move any of the actual data for the VMs. If you are using iSCSI with different LUNs and mount points, the process is more involved for migrating the roles and VMs. The easier process is to simply remove each of the Hyper-V VM roles from the failover cluster manager and use the native Hyper-V Manager to “move” the actual VM’s to the new cluster. Both processes can be done while the VMs are running.

Option 2
Use the built-in Microsoft “Shared Nothing Live Migration” to migrate VMs to new cluster. For the live migration to work between servers you must initiate the move from the source server. Otherwise you need to employ Kerberos authentication for the Hyper-V settings > Live Migration > Advanced settings and the Delegation > Trust properties of the computer object. It is highly recommended to start this process on non-production VMs at first to ensure the process works smoothly!!

Here are the simple step-by-step instructions how to perform this migration.

Step 1: Remove Role

Open Failover Cluster Manager and remove the virtual machine role for the VM you want to move. This does not remove the VM, it simply removes it from the cluster manager and thus is no longer highly available.

Step 2: Hyper-V Manager Move

Open Hyper-V Manager on the server where the VM resides. Right-click the VM and select Move.

Step 3: Select Type of Move

Select the type of move you want to perform. The top option allows you to move the entire VM (config, snapshots, VHDs, etc.).

Step 4: Destination Server Name

Specify the name of your destination server. This is not the cluster name but one of the nodes in the cluster.

Step 5: What to Move

Now select what you want to move. Again, the top option moves all the VM files necessary to run the VM on a different server.

Step 6: Choose folder and move

Browse and select the CSV volume (already created as part of the cluster setup process). We recommend creating a folder with the name of the server inside the CSV for easier identification. Click Next to perform the move.

Step 7: Network Check

When the move initially begins, it pre-checks a variety of things to make sure the move will be successful. One of those items is the virtual switch the VM is connected to. If your virtual switches have the same name between your clusters, then you will not receive this prompt. In this example, there was a prompt for the virtual switch for the VM to connect with due to the name change as shown here. If you have snapshots of the VM, these will also move but you will be prompted for the switch to connect with, if the names are different.

Step 8: Finishing up

The tool will move and preserve the snapshots which you cannot do with the export option. This is one of the main reasons the Move feature is recommended.

www.dataonstorage.com | 1-888-725-8588 | sales@dataonstorage.com 

Copyright © 2020 DataON. All Rights Reserved. Specifications may change without notice. DataON is not responsible for photographic or typographical errors. DataON, the DataON logo, MUST, and the MUST logo are trademarks of DataON in the United States and certain other countries. Other company, product, or services names may be trademarks or service marks of others.

Below is a step-by-step guide on how to add a third node to an existing 2-node Storage Spaces Direct (S2D) cluster with the production workload still running.

1.) Ensure that the cluster is configured with a witness.

2.) Pause/Drain a node in the cluster.

3.) Place the paused node's drives into a storage maintenance mode.

Get-StorageFaultDomain -type StorageScaleUnit | Where-Object {$_.FriendlyName -eq “<Node Name>”} | Enable-StorageMaintenanceMode 

4.) Physically add the 3rd node into the 2-node cluster configuration by cabling the three servers like the image below:

DataON 2U Platforms:

DataON 1U Platform:

5.) Make sure the node that is being added to the cluster has the same firmware and drivers installed as the two servers in the existing 2-node cluster. Also install the necessary Windows features and configure the network correctly. Before adding the third node to the cluster, run a cluster validation.

$S1 = "Node1"

$S2 = "Node2"

$S3 = "Node3"

$nodes = ($S1,$S2,$S3)

Test-Cluster -node $nodes -Include "Storage Spaces Direct",Inventory,Network, "System Configuration" -ReportName C:\Windows\cluster\Reports\report

6.) With a clean validation report, proceed to add the third node into the S2D cluster.

<<Add-ClusterNode -Name ‘NewNodeName’ >>

7.) Disable the storage maintenance mode on the drives of the paused node; Resume the node to the cluster.

Get-StorageFaultDomain -type StorageScaleUnit | Where-Object {$_.FriendlyName -eq “<Node Name>”} | Disable-StorageMaintenanceMode 

8.) By adding a third node to the S2D cluster, 3-way-mirror resiliency is unlocked; Run the following command to configure this setting on the existing storage pool.

<< Get-StoragePool S2D* | Get-ResiliencySetting -Name Mirror | Set-ResiliencySetting -PhysicalDiskRedundancyDefault 2>>

9.) Allow S2D optimization job to complete as well as any other storage jobs to finish before creating a new 3-way-mirror virtual disk/CSV.

10.) With the increased capacity from joining the third node to the cluster, you may now create a new volume (3-way-mirror).

NOTE: The virtual disks that were previously created will remain as 2-way-mirror resiliency.

Introduction

The value of business data grows to the extent that companies simply cannot ignore the importance of a safe data storage. Modern technologies offer a variety of methods how to warrant a highly-available and fault-tolerant storage. One of the techniques includes synchronous mirroring – an approach when a source storage has an exact replica (one or more). At the same time, the data is considered written only when the primary storage receives a signal that all secondary copies have been created. This document suggests taking a look at two-way and three-way synchronous mirroring to better understand the benefits each of them has behind.

Cost-efficiency

2-way synchronous mirroring

This configuration requires storage redundancy on the nodes. The use of RAID10* is recommended. 2-node HA ensures the synchronous mirroring of data between two storage nodes. Taking into account that each storage node has only 50% of usable capacity with RAID10, synchronous mirroring makes the further dividing of those 50% by half resulting in the underutilization of storage capacity – only 25% is used.

* RAID10 use is recommended for a HDD setup. In case of RAID5 use in a HDD setup, there arises the risk of disk failure while rebuilding RAID5. RAID6 in a HDD setup gives low write performance. At the same time, RAID5 and RAID6 configurations can be used for SSD setups due to a high tolerance to physical failures and faster performance of the latter.

With 2-way synchronous mirroring, usable capacity is 25% – ¼ of storage space

3-way synchronous mirroring

Non-redundant RAID0 configuration provides the highest level of performance, therefore, RAID0 can be used for performance. Synchronous mirroring between 3 storage nodes with RAID0 configured on each, results in 33% usable capacity and thus provides a higher level of storage utilization compared to 2-way synchronous mirroring.
While it looks like this configuration does not require storage redundancy on nodes (since 3-way synchronous mirroring already ensures the required level of data protection), you should evaluate the potential risks of disks failing and potential data loss probability (if disks failed on all 3 nodes). Assuming the above, please make sure that the data is protected by backup applications according to the 3-2-1 backup rule.

With 3-way synchronous mirroring, usable capacity is 33% – 1/3 of storage space

As a result, 3-way synchronous mirroring increases the storage utilization rate. The cost-efficiency of this configuration differs depending on the medium type – spindle or flash. The difference is shown on the charts below.

Increased reliability

2-way synchronous mirroring

2-way synchronous mirroring provides 99.99% uptime. The outage of one storage node results in a single point of failure and immediately brings the system to a degraded performance mode. Cache is flushed and turned from write-back to write-through mode on the running node. A number of MPIO paths is reduced twofold because one node is down. Consequently, the storage performance falls.

With 2-way synchronous mirroring, there is a risk of downtime

3-way synchronous mirroring

3-way synchronous mirroring provides 99.9999% uptime. No single point of failure occurs when one node of a 3-node storage cluster goes down. In such a situation, storage performance falls by up to 33% because the system loses 1/3 of the MPIO paths. Performance-critical applications usually can continue running in an ordinary way. The 3-node HA configuration tolerates a double fault and retains the availability of service.

With 3-way synchronous mirroring, constant system uptime is ensured

Higher performance

Higher storage performance is influenced by a number of factors, which include I/O policy, RAID level and cache policy. The effect of these factors is given below:

MPIO paths

2-way synchronous mirroring

With Round Robin/List Queue Depth policy used, I/Os are processed up to two times faster comparing to a single-node configuration.

3-way synchronous mirroring

Owing to the Round Robin/List Queue Depth policy, the I/Os throughput rises by a factor of 3 compared to single-node storage.

As a result, performance is increased by up to 50% compared to a 2-node configuration.

RAID10 vs RAID0

2-way synchronous mirroring

This configuration strongly requires extra redundancy for data protection on the storage nodes themselves. This redundancy can be provided through the use of RAID. RAID10* is recommended for a HDD setup as it ensures mirroring between the disk stripes and makes fast reads and writes. However, storage utilization is considerably low because the same data is mirrored and stored on two stripes of RAID.

* Use of RAID5, RAID6 for a HDD setup is possible but not recommended because of the high probability of a disk failure while rebuilding RAID5, and the low write performance of RAID6. At the same time, RAID5 and RAID6 configurations can be used for SSD setups due to a high tolerance to physical failures and faster performance of the latter.

3-way synchronous mirroring

RAID0 can be used for performance. Both reads and writes are faster here as the system reads the data from all disks simultaneously. With RAID0 you should evaluate the potential risks of disks failing and potential data loss probability (if disks failed on all 3 nodes).

Cache policy

2-way synchronous mirroring

If one node fails, the cache is flushed and turned from write-back to write-through mode and the system immediately switches to a degraded performance mode on reads.

With 2-way synchronous mirroring, cache is flushed and turned to write-through mode causing critical performance degradation

3-way synchronous mirroring

If one node goes down, the system downgrades from a 3 to 2-node cluster and continuous operation with minimal performance degradation (about 33%) due to the absence of one node and because a number of MPIO paths is reduced.

With 3-way synchronous mirroring, cache policy remains write-back that results in minor performance degradation

Important note: Even the highest possible level of redundancy and reliability does not ensure 100% protection against data loss, e.g. due to malicious actions or disaster. So, nothing compares to a good old backup that substantially increases the chances your data is in place.

Conclusion

With synchronous mirroring admins can decide on either two-way mirroring – to ensure basic data protection and high availability, or three-way mirroring – to increase overall system reliability and to also “play games with” cost-efficiency and performance.

In this article, I’ll show you how to use the SCCM feature update option to perform a Windows 10 22H2 upgrade. We will use Windows Servicing in SCCM to upgrade Windows 10 devices to version 22H2 via the enablement package.

Windows 10, version 22H2, also known as the Windows 10 2022 Update, is available for eligible devices running Windows 10, versions 20H2 and newer. Microsoft released Windows 10, version 22H2 (KB5015684) on 18th October 2022, and it is an enablement package.

For home users running Windows 10 version 20H2 and later, the recommended way to get the Windows 10 22H2 is via Windows Update. Go to Start > Settings > Windows Update and run Check for Updates. Select the Feature update to Windows 10, version 22H2 and install it.

When you want to upgrade multiple Windows 10 devices to version 22H2, Configuration Manager is the best tool. It simplifies the way you deploy and manage updates and saves a lot of time. With Configuration Manager, you can select the “Feature Update to Windows 10 Version 22H2 via Enablement Package” and deploy it to a set of devices.

Ways to upgrade to Windows 10 22H2

There are multiple ways that you can use to upgrade to Windows 10 version 22H2.

• Get the Windows 10 22H2 update via Windows Update.
• Use Servicing Plans to upgrade eligible Windows 10 devices to version 22H2.
• Upgrade Windows 10 21H2 to Windows 10 22H2 using ConfigMgr Windows Servicing feature.
• Deploy the Windows 10 22H2 update using the SCCM task sequence.
• Using the Intune to upgrade to Windows 10 22H2 upgrade for WUfB managed devices.

We will use the Configuration Manager feature update option to deploy the Windows 10 22H2 enablement package out of all the above methods. This is the easiest and quickest way I can think of to update Windows 10 to version 22H2.

Recommended: Upgrade to Windows 10 21H2 using SCCM | ConfigMgr

Can I use SCCM Servicing Plans to Upgrade to Windows 10 version 22H2?

Yes, you can use the Servicing Plans in SCCM to upgrade the computers running Windows 10 to version 22H2. With Configuration manager servicing plans you can ensure that all the Windows 10 systems are kept up-to-date when new builds are released. Servicing plans are ADR that can help you to upgrade Windows 10 to version 22H2. Take a look at detailed guide on Windows 10 Servicing Plans in SCCM.

If you are unsure whether to upgrade to Windows 10 22H2 using a Servicing Plan or a feature update deployment, I would advise choosing the latter. There are only a few steps involved in deploying a Windows 10 22H2 feature update, making it much simpler than a servicing plan. You get to make the final decision.

Related Article: Windows 11 22H2 upgrade using SCCM | ConfigMgr

About Windows 10 version 22H2

Windows 10 22H2 is an enablement package and this is good news for admins. The enablement package is a great option for installing a scoped feature update like Windows 10, version 22H2. You can upgrade from version 2004, 20H2, 21H1, or 21H2 to version 22H2 with a single restart, reducing update downtime. Since Windows 10 22H2 is an enablement package, the devices currently on Windows 10, version 20H2 or newer will have a fast installation experience because the update will install like a monthly update.

Prerequisites

With Configuration Manager, you need few things to be configured before you deploy the feature updates to computers. If you have deployed the feature updates before, it means most of the prerequisites are already taken care of. If your SCCM setup is new, you may have to configure them once before deploying the upgrades.

Listed below are all the prerequisites required for Windows 10 22H2 upgrade using SCCM.

• Configure Software Update Point by enabling the upgrades for Windows 10 and Windows 11.
• Ensure the service connection point is online.
• Enable dynamic update for feature updates in Configuration Manager Client Settings.
• Windows 10 1903, and later product must be enabled under Software Update Point > Products.

Download Windows 10 22H2 Enablement Package

Let’s look at steps for downloading Windows 10 22H2 enablement package using SCCM. First of all ensure you have synchronized the updates in Configuration Manager. You can either download the feature first and deploy or directly deploy the feature update. I prefer to download it first, let the content get distributed to distribution points and then deploy it.

Go to Software Library > Overview > Windows 10 Servicing > All Windows 10 Updates. Look for the update “Feature Update to Windows 10 Version 22H2 x64-based systems 2022-10 via Enablement Package“. You can also search the updates with article ID 5015684.

Download Windows 10 22H2 Enablement Package

If you have got both x64-based systems and x86-based systems, you must download Feature Update to Windows 10 Version 22H2 x64-based and x86-based. In my lab, all my Windows 10 VMs are running Windows 10 64-bit OS, and therefore I am going to download only Feature Update to Windows 10 Version 22H2 x64-based systems 2022-10 via Enablement Package.

Create Deployment Package

On the Deployment package window, specify the deployment package for Windows 10 22H2 upgrade files. This deployment package that you create will contain the software update files that will be deployed to the clients.

Select Create a new deployment package and specify the package name as “Windows 10 22H2 Deployment Package.” Add a brief description and specify the package source – a shared folder where you want to download the updates. Enabling the binary differential replication is optional. Click Next.

Download Windows 10 22H2 Enablement Package

Click on Add button and select the distribution point servers to which you would like to distribute the Windows 10 22H2 upgrade files. Click Next.

Download Windows 10 22H2 Enablement Package

On the Distribution Settings page, you can specify the general distribution settings for the deployment package. Click Next.

Specify the Deployment Package Distribution Settings

The download location lets you select an option to download the updates from. For example, you can download the software updates directly from internet or choose to download the software updates from the location on network. Select the option “Download software updates from the internet“. Click Next.

Choose the Download Location for Updates

Specify the update language for the products. The default language is English US. Click Next.

Select Update Languages for Products

Review the Windows 10 22H2 deployment package settings and close the Download software updates wizard.

Close Download Software Updates Wizard

Note: In case you encounter issues while downloading the Windows 10 22H2 enablement package update, review the PatchDownloader.log located in the %temp% folder. This log file will log all the errors that occur during the download of Windows 10 feature updates.

In the above step, the files required to upgrade Windows 10 to version 22H2 are downloaded to the specified location. If you browse to the downloaded location, you will notice that Windows 10 22H2 enablement package contains only one update which is Windows10.0-KB5015684-x64. The size of the Windows 10 22H2 enablement package is 32 KB. This one file is sufficient to upgrade Windows 10 computers to version 22H2.

Windows 10 22H2 Enablement Package

Deploy Windows 10 22H2 Feature Update using SCCM

In this step, using the Windows Servicing, we will perform the Windows 10 22H2 feature update deployment using Configuration Manager. You can deploy the feature update to a single client or to multiple devices using device collection.

If you are deploying the Windows 10 22H2 update for the first time, I suggest testing the upgrade on a Pilot device collection. A few devices that are intended to test the upgrade to 22H2 should be included in this device collection. Use the following guide to create a device collection for Windows 10 computers in SCCM.

Recommended Article: Upgrade Windows 10 21H1 using SCCM | ConfigMgr

Use the following steps to deploy the Windows 10 22H2 feature update using SCCM:

• In the ConfigMgr console, navigate to Software Library\Overview\Windows Servicing\All Windows Feature Updates.
• Right-click Feature Update to Windows 10 Version 22H2 x64-based systems 2022-10 via Enablement Package update, and select Deploy.

Deploy Windows 10 22H2 Feature Update using SCCM

On the General page, enter the details for Windows 10 22H2 feature update deployment.

• Deployment Name: Enter a suitable name such as Deploy Windows 10 22H2 Enablement Package.
• Description: Although it’s optional, you may add a brief description.
• Software Update Group: This is created automatically and is visible under Software Update Groups in Configuration Manager console.
• Collection: Click Browse and select a device collection consisting of few pilot devices selected for testing Windows 10 2022 upgrade.

Click the Next button to continue.

Deploy Windows 10 22H2 Feature Update using SCCM

On the Deployment Settings page, specify the type of deployment. Choose whether you want to make the Windows 10 22H2 upgrade available for users in the Software Center or deploy it as required. Read more about SCCM Available vs. Required to know the differences. Click Next.

Deploy Windows 10 22H2 Feature Update using SCCM

The Scheduling page lets you configure schedule details for the deployment. Configure the following settings:

• Schedule Evaluation | Time Based on: Select Client Local Time.
• Software Available Time: As soon as possible.

If you want to make the Windows 10 22H2 upgrade available at a specific date and time, select Specific time and define them. Define the deadline installation to ensure the upgrade happens in the defined period.

Click Next to continue.

Deploy Windows 10 22H2 Feature Update using SCCM

Specify the following user experience settings for the deployment.

• User Notifications: Display in Software Center and show all notifications
• Commit changes at the deadline or during a maintenance window (requires restarts): Yes
• If any update in this deployment requires a system restart, run updates deployment evaluation cycle after restart: No.

Click Next.

Deploy Windows 10 22H2 Feature Update using SCCM

On the Download settings page, specify the download settings for the current deployment:

• Client Computers can use distribution points from neighbor boundary: No
• Download and install software updates from the fallback content source location: Yes

Click Next to continue.

Deploy Windows 10 22H2 Feature Update using SCCM

Review the deployment settings of Windows 10 22H2 on Summary page and click Next. On the Completion window, click Close.

Deploy Windows 10 22H2 Feature Update using SCCM

Windows 10 22H2 Servicing: End-User Experience for Upgrade

After you have deployed Windows 10 22H2 enablement package update using Windows Servicing, it’s time to test the upgrade installation on end computers. The end-user experience is similar to other feature upgrades.

On the client computer, first launch the Software Center. Once the Software Center has been opened, select Feature Update to Windows 10 Version 22H2 x64-based systems 2022-10 via Enablement Package update by clicking the Updates tab. Click on the Install button.

Windows 10 22H2 Upgrade Servicing: End-User Experience

Confirm you want to upgrade the operating system on this computer. It will take only few minutes to upgrade the operating system as this is an enablement package. Note that this is an in-place upgrade to version 22H2, and the setup automatically migrates your apps, data, and settings. Click on the Install button to begin the Windows 10 22H2 upgrade.

Windows 10 22H2 Upgrade Servicing: End-User Experience

The Feature Update to Windows 10 Version 22H2 x64-based systems 2022-10 via Enablement Package is installed in less than 2 minutes. Click on Restart.

Restart the Computer to Complete Windows 10 22H2 Upgrade

On the confirmation box, click Restart.

Restart the Computer to Complete Windows 10 22H2 Upgrade

The Windows 10 22H2 upgrade is complete. Log in to the Windows 10 computers and click Start > About My PC. Under Windows Specifications, you will find the build number and version of Windows 10. In the below screenshot, we see the Windows version is “22H2” and the OS build number is 19045.2006.

Verify the Windows 10 22H2 Version and Build Number

After you have upgraded multiple Windows 10 computers to version 22H2, you can create a device collection in SCCM. Refer to this article to learn how to create Windows 10 22H2 device collection using WQL Query. If you want to get to Windows 11, you can upgrade to Windows 11 using different methods.