PENDING Issue with SCCM Collection and OS Build Numbers not updating after in-place upgrade to Windows 11 24H2

[chrisj76]

We are currently upgrading the fleet from Windows 10 to Windows 11 24H2 using a in-place upgrade task sequence.
When the rollout stated we didn't have any issue but since more device are new been upgraded we have the following issue.

1. Workstations are been upgrade to Windows 11 24H2 successfully - Active Directory is showing Operation System and Build correctly as Windows 11 10.0 (26100)
but SCCM shows the build number still as Windows 10 10.0.19045 and still in Windows 10 collections.
2. Workstation build number will update to 10.0.26100.x but stills show in the Windows 10 collection and not show in the Windows 11 Collections.

This is cause issue that device that have already been upgrade the Task Sequence will try and run again and keep trying to run daily until the the device is removed out of the wave deployment collection. The way it's meant to work is as soon as the upgrade is completed the device should be in the Windows 11 24H2 collection which is set as an excluded collection but since either the build number or collections are not updating.

The collections are all set to incremental updates.
I've created new client setting policy to run the hardware inventory and software inventory every 3 hours on the upgrade collection.
This has only helped in pulling the correct build number but the collections are still take days to update .
The strange thing is it's not every doing it for every device out of the 250 device so far to upgrade it affected around 50

 

[Garth]

We are currently upgrading the fleet from Windows 10 to Windows 11 24H2 using a in-place upgrade task sequence.
When the rollout stated we didn't have any issue but since more device are new been upgraded we have the following issue.

1. Workstations are been upgrade to Windows 11 24H2 successfully - Active Directory is showing Operation System and Build correctly as Windows 11 10.0 (26100)
but SCCM shows the build number still as Windows 10 10.0.19045 and still in Windows 10 collections.
2. Workstation build number will update to 10.0.26100.x but stills show in the Windows 10 collection and not show in the Windows 11 Collections.

This is cause issue that device that have already been upgrade the Task Sequence will try and run again and keep trying to run daily until the the device is removed out of the wave deployment collection. The way it's meant to work is as soon as the upgrade is completed the device should be in the Windows 11 24H2 collection which is set as an excluded collection but since either the build number or collections are not updating.

The collections are all set to incremental updates.
I've created new client setting policy to run the hardware inventory and software inventory every 3 hours on the upgrade collection.
This has only helped in pulling the correct build number but the collections are still take days to update .
The strange thing is it's not every doing it for every device out of the 250 device so far to upgrade it affected around 50

What exactly does you collection query look like? How often are you preforming heartbeat discovery and hardware Inventory?

 

[chrisj76]

What exactly does you collection query look like? How often are you preforming heartbeat discovery and hardware Inventory?

Windows 11 (24H2) 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" and SMS_G_System_OPERATING_SYSTEM.ProductType = 1

heartbeat discovery is 1 week and per above we change the hardware Inventor to 3 hours to the collection Windows 11 Compatible Devices 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_UPGRADE_EXPERIENCE_INDICATORS on SMS_G_System_UPGRADE_EXPERIENCE_INDICATORS.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_UPGRADE_EXPERIENCE_INDICATORS.UpgExProp = "Green" and SMS_G_System_UPGRADE_EXPERIENCE_INDICATORS.Version = "GE24H2" and SMS_G_System_UPGRADE_EXPERIENCE_INDICATORS.UpgExU = "Green" and SMS_G_System_OPERATING_SYSTEM.Caption like "Microsoft Windows 10%"

this collection also excludes Windows 11 (24H2) Collection

 

[Garth]

Windows 11 (24H2) 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" and SMS_G_System_OPERATING_SYSTEM.ProductType = 1

heartbeat discovery is 1 week and per above we change the hardware Inventor to 3 hours to the collection Windows 11 Compatible Devices 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_UPGRADE_EXPERIENCE_INDICATORS on SMS_G_System_UPGRADE_EXPERIENCE_INDICATORS.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_UPGRADE_EXPERIENCE_INDICATORS.UpgExProp = "Green" and SMS_G_System_UPGRADE_EXPERIENCE_INDICATORS.Version = "GE24H2" and SMS_G_System_UPGRADE_EXPERIENCE_INDICATORS.UpgExU = "Green" and SMS_G_System_OPERATING_SYSTEM.Caption like "Microsoft Windows 10%"

this collection also excludes Windows 11 (24H2) Collection

3 hours is too often, daily is fine for HW inv. Daily is what you should be using for Heartbeat discovery too.