none
Deployment Status Unknown. RRS feed

  • Question

  • Dear All,

    We are having a strange issue where Patched SCCM clients are showing as “Unknown” deployment status.

    However, when same is checked in the reporting tool of SCCM, those server DO NOT appear under “unknown”

    Investigations and tests:

    1. The boundary group corresponding to the servers did not exist.
      1. Same has been created but the deployment status of the servers are still showing as “unknown”.

    1. A new deployment group, software update group and collection was created and applied on 2 Test Servers
      1. But same issue has been observed.

    1. WSUS target, Firewall and telnet were checked 
      1. WSUS points to the correct path
      1. Firewall is off on the machines
      1. Telnet to the wsus/sccm on port 8530 is successful.

    1. On the SQL Db Affected server is reporting the last evaluation to be on 26 October 2019

      1. However, on the server itself, the last evaluation is dated to be 04 Nov. 19

    1. Also, the results of the evaluation shows that all  tests were passed.

    Applied till now:

    http://get-cmd.com/?p=4367

    https://smsagent.blog/tag/client-check-result-no-results/

    https://smsagent.blog/2016/02/12/reading-ccmeval-results-directly-from-a-configmgr-client-with-powershell/

    https://social.technet.microsoft.com/Forums/en-US/6a307f01-2fbf-4ded-b46d-3ab29921713f/sccm-2012-clients-status-unknow?forum=configmanagersecurity

    Any help/ opinion is welcomed.

    Thanks in advanced.

    Devesh

    Monday, November 4, 2019 7:21 AM

Answers

  • Not sure how, but the issue seems to be solved.

    Steps done:

    1. created new deployment with the latest patches

    2. Redeployed on the appropriate collection.

    Only machines appearing under unknown are those with no agent now.

    Thanks all for your input,

    Devesh

    Tuesday, November 19, 2019 5:25 AM

All replies

  • Have you checked the Scan status of specific machine?

    and also enforcement status for specific deployment

    Monday, November 4, 2019 10:32 AM
  • Unknown means the site has not heard from the client about its state from the deployment.

    For software updates, that always means checking wuahandler.log first.

    Boundaries and boundary groups are unrelated to reporting deployment state.

    Have you tried forcing the clients to resend all of their update compliance states?

    See https://blogs.technet.microsoft.com/scotts-it-blog/2015/02/23/refreshing-state-messages-in-system-center-configuration-manager-2012/


    Jason | https://home.configmgrftw.com | @jasonsandys

    Monday, November 4, 2019 1:39 PM
  • Hi Devesh,

    Based on your scenario, have you verified the updates were distributed to the DP successfully? Have your clients received the updates?

    In addition, here is a link to troubleshoot client update issues, hope it helps.
    http://eskonr.com/2015/04/sccm-2012-troubleshoot-client-software-update-issues/


    Best Regards,
    Tina

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, November 5, 2019 3:17 AM
  • Hi,

    How are things going? I just checked in to see if there are any updates. Please feel free to feedback and if the reply is helpful, please kindly click “Mark as answer”. It would make the reply to the top and easier to be found for other people who has the similar question.

    Thank you for your kindly support.

     
    Best Regards,
    Tina

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, November 8, 2019 7:31 AM
  • Hello,

    Thanks for your reply.

    The scan status is showing as successful.

    Monday, November 11, 2019 11:33 AM
  • Hello,

    Thanks for your reply.

    i've already tried forcing the agents to re send status update and even uninstalled and reinstalled agents but issue is still persisting.

    Monday, November 11, 2019 11:35 AM
  • Hello,

    Thanks for your reply.

    Yes, the updates were well received and installed on the clients.

    But the issue is still persisting also, when checking on compliance reports, 1 server which has all required updates installed, is showing as 'non-compliant'.

    Monday, November 11, 2019 11:37 AM
  • Check the client updatesstore.log for any missing updates
    Monday, November 11, 2019 1:23 PM
  • How did you verify that the updates were installed?

    Have the systems rebooted since installing the updates?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, November 13, 2019 2:59 AM
  • Not sure how, but the issue seems to be solved.

    Steps done:

    1. created new deployment with the latest patches

    2. Redeployed on the appropriate collection.

    Only machines appearing under unknown are those with no agent now.

    Thanks all for your input,

    Devesh

    Tuesday, November 19, 2019 5:25 AM