none
Monitoring Deployment gray for % of computers but discovery works locally RRS feed

  • Question

  • We are distributing Anti Virus software as Application for all workstations, and less than 10% is still gray, after 9 months of deployment being active. I have spent many many many many many working days for cleaning the reasons, so far;

    - Boundaries are okay
    - Client push has been made several times
    - Client re-install with Group policies has been made
    - Unknown Computers are online
    - Same deployment has been done to unknown Computers with Task Sequence
    - SCCM is updated to 1906, latest client version is promoted to production

    Today I got my hands on a Computer, which DOES DISCOVER the Application in Appdiscovery.log but Still stays Unknown in Deployment Monitor view. Hardware scan works, and in inventory F-Secure is seeing. But not in Deployment monitoring. This scenario with appdiscovery.log is very weird to me, what a heck is going on :D


    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Tuesday, September 17, 2019 9:38 AM

All replies

  • Hi,

    What is the Windows version on these clients?

    Do you have the same issue with Software Updates deployment?

    Check the following client log files for more details:

    • Execmgr.log, LocationServices.log and DataTransferService.log

    Regards,

    SAAD Youssef

    _____

    Please remember to mark the replies as answer if they help, thank you!


    • Edited by SAAD Youssef Tuesday, September 17, 2019 10:11 AM
    Tuesday, September 17, 2019 10:10 AM
  • I discoverd some WMI issues in ccmexec.log and other logs and considering now, which is the "Best WMI Fix script" or methot TODAY :)

    Maybe this? https://gallery.technet.microsoft.com/ConfigMgr-Client-Health-ccd00bd7


    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Tuesday, September 17, 2019 10:16 AM
  • Yes, you can use the above script for the check and remediation actions about SCCM client.

    Here is also a script to repair SCCM or rebuild WMI: https://github.com/stevenbartcom/SCCMRepair

    Tuesday, September 17, 2019 10:31 AM
  • Yes, you can use the above script for the check and remediation actions about SCCM client.

    Here is also a script to repair SCCM or rebuild WMI: https://github.com/stevenbartcom/SCCMRepair

    Yep, I just found the same and it seems to be simple enough, and is able to run remote / mass.

    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.


    • Edited by yannara Tuesday, September 17, 2019 10:53 AM
    Tuesday, September 17, 2019 10:53 AM
  • Yes, you can use the above script for the check and remediation actions about SCCM client.

    Here is also a script to repair SCCM or rebuild WMI: https://github.com/stevenbartcom/SCCMRepair

    This script doesn't work. SCCM gets uninstalled, wmi gets rebuilt but client re-install failes. 

    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Tuesday, September 17, 2019 2:08 PM
  • What is the error message in the ccmsetup.log ?
    Tuesday, September 17, 2019 2:24 PM
  • Ugh, that's a terrible and destructive script and I would strongly recommend that no one ever use it. Renaming the repository folder deletes the WMI repository forcing it to be rebuilt which may lose information.

    The proper way to repair WMI is to use the built repair processes and the WMIDiag script.


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

    Tuesday, September 17, 2019 2:57 PM
  • What is the error message in the ccmsetup.log ?
    The WMI doesn't build enough quickly and ccmsetup fails because there is no accessable WMI database yet. 

    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Wednesday, September 18, 2019 6:49 AM
  • Ugh, that's a terrible and destructive script and I would strongly recommend that no one ever use it. Renaming the repository folder deletes the WMI repository forcing it to be rebuilt which may lose information.

    The proper way to repair WMI is to use the built repair processes and the WMIDiag script.


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

    Jason, could you please point me to the right method in details? A link somewhere how to build an automated solution to get this done. I went through Microsoft's WMIDiag tool and if I am not mistaken there is no silent automated method to fix wmi.

    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Wednesday, September 18, 2019 6:51 AM
  • Well, there is no magic, fully automated way to repair WMI except the built-in command-lines. If there was, WMI probably wouldn't have issues in the first place or would be able to auto-repair itself.

    Also, with Win 10, most issues that people think are WMI related, aren't because WMI is very robust and nearly self-repairing in Win 10.

    Here's official guidance though:

    https://techcommunity.microsoft.com/t5/Ask-The-Performance-Team/bg-p/AskPerf/label-name/wmi

    https://blogs.technet.microsoft.com/yongrhee/2016/06/23/wmi-stop-hurting-yourself-by-using-for-f-s-in-dir-s-b-mof-mfl-do-mofcomp-s/


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

    Wednesday, September 18, 2019 12:20 PM

  • Also, with Win 10, most issues that people think are WMI related, aren't because WMI is very robust and nearly self-repairing in Win 10.


    I totally agree. This came to me as total suprise, and an example Computer I saw was Win10. I was hoping to populate a script solution via Group Policy Preferences Scheduled Task.

    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Thursday, September 19, 2019 7:31 AM
  • As noted though, if it were that easy, the problem probably wouldn't happen in the first place or would already auto-correct. That's one of the reasons that WMIDiag is a non-trivial script as there are so many different things that could go wrong.

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

    Thursday, September 19, 2019 5:00 PM