none
Error checking Client activity RRS feed

  • Question

  • Hi all,

    We currently have the SCCM v1802 and on some computers passed through the image of PXE 1903 of Windows 10 via the SCCM itself, we have seen that the CCM client is installed and reports that it is active only for a while, after this, it leaves in the SCCM as "No client", which is not true `because both the" SMS agent host "service is running, as well as the client version are correct. We check it with:

    Get-Service -Name 'sms agent host' -ComputerName name1 | Select-Object -Property Status

    Get-WMIObject -ComputerName 'name1' -namespace root\ccm -class sms_client | select clientversion


    After searching for information, I have seen a way to restart the service, generating the config file again, as well as reinstalling the SMS certificates, with the following commands from CMD:

    net stop ccmexec
    ren "C:\Windows\SMSCFG.ini" SMSCFG_old.ini
    certutil -delstore SMS SMS
    net start ccmexec


    But the problem is reproduced from time to time, it comes out again as a non-client, which means that we cannot apply updates, etc., and less when we have the windows update against the Internet covered in workstations.

    In the logs we see:

    UpdateTrustedSites.log

    AddDefaultPortalToTrustedSites (delete) : url = http://name.domain.com:80/CMApplicationCatalog, zone = 2

    AddDefaultPortalToTrustedSites: SetZoneMapping(delete) failed: 80070002

    I don't see any more errors in the logs, any idea where I can see the error?

    Greetings and thanks for the help

    Gerardo,

    Wednesday, September 18, 2019 12:35 PM

All replies

  • CCMeval.exe:

    ==========[ ccmeval started in process 11516 ]==================================== CcmEval 18/09/2019 14:50:47 14148 (0x3744)

    ccmeval version: 5.0.8692.1000 CcmEval 18/09/2019 14:50:47 14148 (0x3744)
    Loading manifest file: c:\Windows\CCM\CcmEval.xml CcmEval 18/09/2019 14:50:47 14148 (0x3744)
    Successfully loaded ccmeval manifest file. CcmEval 18/09/2019 14:50:47 14148 (0x3744)
    Begin evaluating client health rules. CcmEval 18/09/2019 14:50:47 14148 (0x3744)
    Successfully retrieved all client health checks. CcmEval 18/09/2019 14:50:47 14148 (0x3744)

    .........

    Evaluating health check rule {09886543-BE8B-431F-BC00-7D917632E22C} : Verify/Remediate Antimalware service startup type. CcmEval 18/09/2019 14:50:52 14148 (0x3744)
    Result: Not Applicable, ResultCode: 0, ResultType: 0, ResultDetail:  CcmEval 18/09/2019 14:50:52 14148 (0x3744)
    Evaluating health check rule {5B50566C-363E-4F1C-8A7D-6F2D2A51B142} : Verify/Remediate Antimalware service status. CcmEval 18/09/2019 14:50:52 14148 (0x3744)
    Result: Not Applicable, ResultCode: 0, ResultType: 0, ResultDetail:  CcmEval 18/09/2019 14:50:53 14148 (0x3744)
    Evaluating health check rule {B9274BD3-4B32-4B41-8E4D-7B0306D412CE} : Verify/Remediate Antimalware service startup type for Windows 10 or up. CcmEval 18/09/2019 14:50:53 14148 (0x3744)
    Result: Not Applicable, ResultCode: 0, ResultType: 0, ResultDetail:  CcmEval 18/09/2019 14:50:53 14148 (0x3744)

    .......

    Failed to get SOFTWARE\Policies\Microsoft\Microsoft Antimalware\Real-Time Protection\DisableIntrusionPreventionSystem CcmEval 18/09/2019 14:50:53 14148 (0x3744)
    Result: Not Applicable, ResultCode: 0, ResultType: 0, ResultDetail:  CcmEval 18/09/2019 14:50:53 14148 (0x3744)

    .......

    Successfully evaluated all client health rules. CcmEval 18/09/2019 14:50:53 14148 (0x3744)

    Client is set to use HTTPS when available. The current state is 224. CcmEval 18/09/2019 14:50:53 14148 (0x3744)
    MapNLMCostDataToCCMCost() returning Cost 0x1 CcmEval 18/09/2019 14:50:53 14148 (0x3744)
    Client is set to use HTTPS when available. The current state is 224. CcmEval 18/09/2019 14:50:53 14148 (0x3744)
    Raising event:
    instance of CCM_CcmHttp_Status
    {
    ClientID = "GUID:2394c84a-ffe0-4818-bcef-dda5e7a06ebf";
    DateTime = "20190918125054.324000+000";
    HostName = "SVPMI030.ibsesp.loc";
    HRESULT = "0x00000000";
    ProcessID = 11516;
    StatusCode = 0;
    ThreadID = 14148;
    };
    CcmEval 18/09/2019 14:50:54 14148 (0x3744)
    Client's current MP is http://SVPMI030.ibsesp.loc and is accessible CcmEval 18/09/2019 14:50:54 14148 (0x3744)
    MP check succeeded CcmEval 18/09/2019 14:50:54 14148 (0x3744)
    Send previous report if needed. CcmEval 18/09/2019 14:50:54 14148 (0x3744)
    Fail to get time from registry CcmEval 18/09/2019 14:50:54 14148 (0x3744)
    Can't determine whether previous sent succeed, assume sent failed CcmEval 18/09/2019 14:50:54 14148 (0x3744)
    Previous report was sent as state message, check whether it was really sent CcmEval 18/09/2019 14:50:54 14148 (0x3744)
    Previous report was successfully sent as a state message. CcmEval 18/09/2019 14:50:54 14148 (0x3744)
    Report is changed, need to send it this time. CcmEval 18/09/2019 14:50:54 14148 (0x3744)
    Begin to send client health status report CcmEval 18/09/2019 14:50:55 14148 (0x3744)
    Successfully sent client health status as a state message. CcmEval 18/09/2019 14:50:55 14148 (0x3744)
    Evaluating Client Health status for MDM_ConfigSetting... CcmEval 18/09/2019 14:50:55 14148 (0x3744)
    Updating MDM_ConfigSetting.ClientHealthStatus with value 7 CcmEval 18/09/2019 14:50:55 14148 (0x3744)
    ==========[ ccmeval finished normally in process 11516 ]========================== CcmEval 18/09/2019 14:50:55 14148 (0x3744)

    Gerardo,

    Wednesday, September 18, 2019 12:57 PM
  • Hi,

    That could be related to the client getting stuck in Provisioning Mode due to a "Restart PC" task in the OSD. The problem is that the Restart PC task at the end of the task sequence wasn't properly letting the client close itself out of provisioning mode.

    We can try to change the following registry key and reboot the PC:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec
    Provisioning Mode set to FALSE 
    SystemTaskExcludes set to *BLANK* 

    For the reference:
    https://www.windows-noob.com/forums/topic/13363-console-showing-client-no/

    Regards,
    Allen

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, September 19, 2019 2:25 AM