Windows Server 2025 Device Collection

Create Device Collection for Windows Server 2025 in SCCM

Last Updated

November 24, 2025

Posted In

In this guide, I will cover the steps to create a Windows Server 2025 device collection in SCCM. A WQL query can be used to group all devices running Windows Server 2025 into a dedicated device collection.

The latest server operating system from Microsoft is Windows Server 2025. It is also referred to as the Windows Server version 24H2 update. Server 2025 focuses on enhancing security, improving performance, and introducing innovative features. I recommend reading this useful guide on how to download and Windows server 2025.

Before publishing this guide, I performed a client push on Windows Server 2025 and the client agent installation was successful. I used SCCM 2403 to push the client agent on to Server 2025.

Install and Update Third Party Applications with Patch My PC
Install and Update Third Party Applications with Patch My PC

Build number of Windows Server 2025

The WQL query that we will use to create the collection for Server 2025 primarily uses the OS build number. You may also use the OS caption for grouping Server 2025 devices, but it may not be as accurate as using the build number.

One can manually find the build number on Windows Server 2025 by going to Start > Settings > About > Windows Specifications.

Operating System and Full OS build numbers are easily retrieved from the device discovery data in the SCCM console. Right-click a Windows Server 2025 device in the SCCM console and select Properties. In the General tab, scroll down and locate the Operating System Build and Full Operating System Build.

From the below screenshot, here are the build details for Server 2025:

  • Windows Server 2025 Operating system build number: 10.0.26100
  • Windows Server 2025 Full Operating system build number: 10.0.26100.560
Find Build number of Windows Server 2025 using SCCM
Find Build number of Windows Server 2025 using SCCM

Create Windows Server 2025 device collection in SCCM

Follow the below steps to create a Windows Server 2025 device collection in SCCM:

1. Launch the Configuration Manager console and navigate to the Assets and Compliance workspace. Right-click the Device Collections node and select Create Device Collection.

Create Windows Server 2025 device collection in SCCM
Create Windows Server 2025 device collection in SCCM

2. Enter the device collection name as Windows Server 2025 Collection. Choose the limiting collection and click Next.

Create Windows Server 2025 device collection in SCCM
Create Windows Server 2025 device collection in SCCM

3. On the Membership Rules window, click Add Rule and from the drop-down, select Query Rule.

Create Windows Server 2025 device collection in SCCM
Create Windows Server 2025 device collection in SCCM

4. In the Query Rule Properties box, enter the query name and click Edit Query Statement. In the Query statement properties window, select the Criteria tab. Click Show query language and enter the below WQL query to create a Windows Server 2025 device collection.

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.BuildNumber = "26100"
WQL Query for Windows Server 2025 Collection
WQL Query for Windows Server 2025 Collection

5. Click OK three times and continue with the device collection wizard. Review the changes on the Summary page. Complete the remaining steps and close the wizard.

Create Windows Server 2025 device collection in SCCM
Create Windows Server 2025 device collection in SCCM

After a few minutes, in the SCCM console, check the member count of the Windows Server 2025 device collection. The collection should group all the Windows 2025 servers in your hierarchy. Expand the collection to view the members.

If the Server 2025 device collection is not updating, review the colleval.log that records details about when collections are created, changed, and deleted by the Collection Evaluator.

Leave a Reply

Your email address will not be published. Required fields are marked *

5 Comments

  1. Ok found a fix. I added this in after the build number 1 is Windows 11 and 3 is for server.

    and SMS_G_System_OPERATING_SYSTEM.ProductType = “3”
    —-
    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.BuildNumber = “26100” and SMS_G_System_OPERATING_SYSTEM.ProductType = “3”

  2. it’s not a good collection, it includes all windows 11 machines, the same build number “26100”. All Windows 11 machines are included in the collection

  3. there is an error in the code:
    SMS_G_System_OPERATING_SYSTEM.Version = “26100”
    should be
    SMS_G_System_OPERATING_SYSTEM.BuildNumber = “26100”

      1. Still shows all windows 11 devices and when I try to add the 10.0.26100.32522 it wont load the Servers with that build. I hate MS sometimes.

Prajwal Desai

Prajwal Desai is a highly accomplished technology expert and an 11-time Dual Microsoft MVP (Most Valuable Professional), specializing in Microsoft Intune, SCCM, Windows 365, Enterprise Mobility, and Windows. As a renowned author, speaker, and community leader, he is widely recognized for sharing his in-depth expertise and insights through his blog, YouTube channel, conferences, webinars, and other platforms.