Hi, @Franz Schenk
Try to install the latest CU for 21H2 to see if it helps.
22H2 enablement Package does not work
- Have prepared the required 22H2 enablement package
- And distributed to a 21H2 Testclient The Build Upgrade never arrives on the client. But the deployment status says that the 21H2 system is compliant to 22H2
(See all pictures)
Thank you in advance for any advice where to start troubleshooting.
Franz
Microsoft Security | Intune | Configuration Manager | Other
-
AllenLiu-MSFT 49,316 Reputation points Microsoft External Staff
2023-04-04T06:44:18.2+00:00
2 additional answers
Sort by: Most helpful
-
AllenLiu-MSFT 49,316 Reputation points Microsoft External Staff
2023-03-31T02:38:23.2333333+00:00 Hi, @Franz Schenk
Thank you for posting in Microsoft Q&A forum.
The "Compliant" in deployment status has two meanings:
- The client need this update and has installed it.
- The client does not need this update.
So, we may firstly check if SCCM think the client need this update, we can click the "Required" to see if the test client is in the list.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".
-
Franz Schenk 341 Reputation points
2023-03-31T08:18:03.1466667+00:00 You are right, the client is not in the list above. Among with three other clients of the testing collection, which contains 8 clients.
Have verified again this client. It's for sure 21H2, and it has the latest security- and service stack update installed. So the question is why SCCM considers some clients "compliant" to Win 10 22H2 when they are running Win 10 21H2.