This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
In SCCM 100% of our Server 2012 R2 servers show an Unknown status when it comes to Windows Updates. I can't find anything online. Any ideas? All other server versions 2012. 2016 and 2019 are reporting correctly.
Hi, @Daniel Kaliel
That is really strange, is the boundary group related to Server 2012 R2 configured correctly and the SUP configured correctly?
And how many updates in this SUG you are deploying?
So they are in the same boundary groups as the other server versions. I believe there are only 4 updates in this group.
I will re-deploy with updates and see, maybe? (your suggestion has me thinking) that someone just went wrong with the deployment.
I can't deploy until near the end of the month, so I will update this case at that time.
Hi, @Daniel Kaliel
Thank you for posting in Microsoft Q&A forum.
We may select a server 2012 R2 client to check the WUAHander.log to see if client can scan the updates corrrectly.
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 "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
There doesn't appear to be any errors in that log.
<![LOG[Existing WUA Managed server was already set (https://MRESCCM.mross.ds:8531), skipping Group Policy registration.]LOG]!><time="06:57:00.341+420" date="02-10-2022" component="WUAHandler" context="" type="1" thread="4056" file="sourcemanager.cpp:1117">
<![LOG[Added Update Source ({CCBA2E64-0A46-47F7-A6D7-C4DEA2F969B5}) of content type: 2]LOG]!><time="06:57:00.341+420" date="02-10-2022" component="WUAHandler" context="" type="1" thread="4056" file="sourcemanager.cpp:1503">
<![LOG[Scan results will include all superseded updates.]LOG]!><time="06:57:00.357+420" date="02-10-2022" component="WUAHandler" context="" type="1" thread="4056" file="cwuahandler.cpp:3674">
<![LOG[Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')]LOG]!><time="06:57:00.357+420" date="02-10-2022" component="WUAHandler" context="" type="1" thread="4056" file="cwuahandler.cpp:3677">
<![LOG[Async searching of updates using WUAgent started.]LOG]!><time="06:57:01.533+420" date="02-10-2022" component="WUAHandler" context="" type="1" thread="4056" file="cwuahandler.cpp:1004">
<![LOG[Async searching completed.]LOG]!><time="06:57:26.372+420" date="02-10-2022" component="WUAHandler" context="" type="1" thread="3840" file="cwuahandler.cpp:2810">
<![LOG[Successfully completed scan.]LOG]!><time="06:57:27.747+420" date="02-10-2022" component="WUAHandler" context="" type="1" thread="4056" file="cwuahandler.cpp:4317">
Anything interesting in CcmMessaging.log on the 2012 R2 client showing as Unknown?
I have exactly the same problem in one of the environments that's not using internal PKI and MP/DP is set to HTTP:
[CCMHTTP] ERROR: URL=http://<mp>/ccm_system_windowsauth/request, Port=80, Options=1216, Code=0, Text=CCM_E_NO_TOKEN_AUTH
I checked the ccmMessaging.log on the server and we don't see anything. In our case we are using PKI and HTTPS
Supplied sender token is null. Using GetUserTokenFromSid to find sender's token.
Raising event: instance of CCM_CcmHttp_Status { ClientID = "GUID:FEDCCD66-F521-4F86-9CA6-FDFF2E53405E"; DateTime = "20220224203240.206000+000"; HostName = "MRESCCM.mross.ds"; HRESULT = "0x00000000"; ProcessID = 8096; StatusCode = 0; ThreadID = 2844;};
Raising event: instance of CCM_CcmHttp_Status { ClientID = "GUID:FEDCCD66-F521-4F86-9CA6-FDFF2E53405E"; DateTime = "20220224203250.712000+000"; HostName = "MRESCCM.mross.ds"; HRESULT = "0x00000000"; ProcessID = 8096; StatusCode = 0; ThreadID = 2844;};
OutgoingMessage(Queue='mp_mp_ddrendpoint', ID={CBEDF515-3AAC-404D-8683-A8FF7DA85943}): Delivered successfully to host 'MRESCCM.mross.ds'. CcmMessaging
@AllenLiu-MSFT you are right. Recreating the DP and redeploying worked but for some reason I can't mark it as an answer.
And when you check the updates for 2012 R2 in All Software Updates, what's the number of Required and NotRequired? Or are they all show unknown?
So again, none of the February patches deployed. We had to do them manually. But when I check on the individual patches I see:
BUT when I look at the deployment in monitoring it still shows 100% unknown.
Should I delete the deployment and downloads and try again?
For the individual update, it shows 18 clients require this update.
I think you may try to re-deploy it to see if it helps.
That worked
Sign in to comment