question

ABarkath-1705 avatar image
0 Votes"
ABarkath-1705 asked saldana-msft edited

Issues in 20H2 reporting

  1. We have deployed feature update of 20h2 via servicing plan,the issue is when i see the web report there are 70 systems are compliant. when i go and check in physically, the update not even received.

another isuue is , able to see one of system as compliant but same time when i check in SCCM console it show as 1909 build,also physically login into the system and checked where system already been upgraded.

Can some one help here please.

windows-server-update-servicesmem-cm-updates
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

RitaHu-MSFT avatar image
0 Votes"
RitaHu-MSFT answered RitaHu-MSFT edited

@ABarkath-1705
Thanks for your posting on Q&A.

For the first question, please try to review the PolicyAgent.log on one of the computers and confirm the computer has already received the policy.

Here are several screenshots for your reference. Please ignore it if you have already known how to confirm the PolicyAgent.log.

129093-2.png

129075-3.png

For the second question, please review the CcmMessaging.log on the client. The log could record activities related to communication between the client and management points.

Please keep us in touch if there are any updates of the case. Have a great weekend.

Regards,
Rita


If the response is helpful, please click "Accept Answer" and upvote it.
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.


2.png (85.4 KiB)
3.png (43.6 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ABarkath-1705 avatar image
0 Votes"
ABarkath-1705 answered

@RitaHu-MSFT ,

Thank for your post.

Issue1:I have go though the policyagent.log and try to find the policy on 1-2 systems where could not found.

Also this issue was reported in Win 10 2004 build version.

The second one is, Now the system is reflected with correct build version in SCCM console also this system has 1909 build version. Many i know why this system took many days to update in SCCM DB?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ABarkath-1705 avatar image
0 Votes"
ABarkath-1705 answered RitaHu-MSFT commented

129163-policy-on-win-10-2004-build.png



· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@ABarkath-1705
Thanks for your feedback.

Please help to confirm whether the computers are active on the MECM console.
129554-8.png

It seems that the computers could not receive the policy. We could review the CcmMessaging.log to check the communication between the client and management points. In addition, how many computers encounter this issue? All the computers encounter this issue or just a few computers.

Note that if the content not distributed to DP, the deployment wont appear in the software center.

Regards,
Rita

0 Votes 0 ·
8.png (52.0 KiB)

@RitaHu-MSFT

Thank you for reply.

I could see the systems are in MECM console also i have verified that CcmMessaging.log as per this logs the communication between from client and server is successful.

Please find the attached screen shot.

We have deployed FU of 20H2 build to 100 pilot systems which contains (1909/2004), The 1909 systems got upgraded sucessfully which means there is no issues with content distribution. Only issues are in where 2004 build got installed.14 systems were part of the pilot collection, all these systems has win 10 2004 build version.129579-ccm.png


0 Votes 0 ·
ccm.png (46.8 KiB)

@ABarkath-1705
It is weird. How come the windows 10 2004 systems did not receive the policy though the communication between the clients with MP is correct. Would you mind helping to check policyagent.log one more time? Perhaps we missed some tips.

In addition, I noticed that you have mentioned in the first post that there are 70 systems are compliant. Perhaps the windows 10 2004 clients are not compliant to upgrade so the clients did not detect the 20H2 FUs. We could check the UpdatesStore.log on windows 10 2004 clients to check the compliance.

Regards,
Rita

0 Votes 0 ·
Show more comments