none
Alert me SCCM- can't remote control new client RRS feed

  • Question

  • Hello,

    Recently new clients cannot be connected.

    On console: Client Type of client is -None

    On client in Configuration Manager Properties:

       Client Certificate is None

       In Actions: there is only: Machine Policy Retrieval & Evaluation Cycle, User Policy Retrieval & Evaluation Cycle.

       In Components: CCM Notification Agent is disabled

    Thanks 

    Wednesday, November 20, 2019 8:50 AM

Answers

  • Thank you all
    Everything worked after the MP was corrected in the following action:
    % windir% \ system32 \ inetsrv \ appcmd.exe set config -section: system.webServer / httpCompression / - [name = 'xpress']

    One client was still problematic and we reformatted it and now it's correct

    • Marked as answer by mbyforum Wednesday, November 27, 2019 7:33 AM
    Wednesday, November 27, 2019 7:33 AM

All replies

  • check the boundaries.. monitor log files locationservices.log and clientlocation.log

    follow the blog Troubleshooting issues where clients are not reporting http://blogs.technet.com/b/configurationmgr/archive/2009/08/10/troubleshooting-issues-where-clients-are-not-reporting.aspx

    Wednesday, November 20, 2019 9:19 AM
  • Hi,

    Check first if the SCCM client is installed correctly on these machines, if not, try a push installation from the console, don't forget to make sure that all prerequisites are OK (Windows Firewall, Push installation account...).

    If you are using a PKI certificate between SCCM and clients, check if the PKI certificate is enrolled on the computer client.

    Btw, what is your SCCM and Windows client version?

    Regards,

    SAAD Youssef

    ______

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

    Wednesday, November 20, 2019 10:05 AM
  • Thanks for your responses

    SCCM 2012 Version 1802

    Windows 10 Client

    I send 2 attached Files from one of the problematic PC

    In a good Pc: Client Certificate: Self-signed

    • Edited by mbyforum Wednesday, November 20, 2019 10:23 AM
    Wednesday, November 20, 2019 10:22 AM
  • In your first screenshot, there is no assigned management point, is it true or just hidden by you?

    In the Actions tab (second screen), run Machine Policy Retrieval & Evaluation Cycle, do you obtain an error message to do this?

    Check also LocationServices.log & ClientLocation.log files located in "%WINDIR%\CCM\Logs".


    • Edited by SAAD Youssef Wednesday, November 20, 2019 10:50 AM
    Wednesday, November 20, 2019 10:49 AM
  • I don't hide the management point

    Run Machine Policy Retrieval & Evaluation Cycle, done error message "The selected cycle cannot start"

    Wednesday, November 20, 2019 11:19 AM
  • Try to install the client manually with the specifying the MP server in the installation command line:

            ccmsetup.exe SMSMP=SCCM_Server SMSSITECODE=ABC

    Don't forget to change "SCCM_Server" with the FQDN of your SCCM/MP Server and "ABC" with your SCCM Site Code.

    To locate ccmsetup.exe file, go to "C:\Windows\ccmsetup".

    What about LocationServices.log & ClientLocation.log files ?


    • Edited by SAAD Youssef Wednesday, November 20, 2019 1:53 PM
    Wednesday, November 20, 2019 1:52 PM
  • You can't initiate a remote control session to a system without the client agent installed and successfully communicating with the site.

    Have you reviewed the logs on the client system to determine why it is not successfully communicating with or registering with the site including clientidmanagerstartup.log, ccmmesaaging.log, clientlocation.log, and locationservices.log?

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

    Wednesday, November 20, 2019 2:04 PM
  • Hi,

    First, we need to make sure if the boundaries and boundary groups are configured correctly. And also check the logs mentioned above. 

    Then, there is no such thing called SCCM 2012 Version 1802, it is SCCM current branch 1802. And SCCM 1802 is end support on September 22, 2019. it is recommend to upgrade to SCCM current branch 1906 ASAP.

    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, November 21, 2019 7:00 AM
  • No change.

    What should I look at in log files?

    Thursday, November 21, 2019 7:50 AM
  • there are 2 Boundaries: 

    I upgrade to SCCM 2012 from Version 1802 to 1902 (Yesterday)

    The Management point is error

    I do but no change
    dism.exe /online /norestart /enable-feature /ignorecheck /featurename:"IIS-WebServerRole" /featurename:"IIS-WebServer" /featurename:"IIS-CommonHttpFeatures" /featurename:"IIS-StaticContent" /featurename:"IIS-DefaultDocument" /featurename:"IIS-DirectoryBrowsing" /featurename:"IIS-HttpErrors" /featurename:"IIS-HttpRedirect" /featurename:"IIS-WebServerManagementTools" /featurename:"IIS-IIS6ManagementCompatibility"  /featurename:"IIS-Metabase" /featurename:"IIS-WindowsAuthentication"  /featurename:"IIS-WMICompatibility"  /featurename:"IIS-ISAPIExtensions" /featurename:"IIS-ManagementScriptingTools" /featurename:"MSRDC-Infrastructure" /featurename:"IIS-ManagementService"
    



    • Edited by mbyforum Thursday, November 21, 2019 9:38 AM
    Thursday, November 21, 2019 7:53 AM
  • Hi,

    Did you add the boundary to the boundary group and config the site assignment of boundary group?


    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, November 21, 2019 8:01 AM
  • Yes

     it does not only work for recently installed stations

    Thursday, November 21, 2019 8:04 AM

  • The Management point is error



    You have to make first that the Management Point is healthy, try with the suggested solutions and if the problem persists, check mpcontrol.log file for more details ("SCCM Install directory\Microsoft Configuration Manager\Logs").
    Thursday, November 21, 2019 9:48 AM
  • Ok now the MP is right but there are some Clients Is No and it's not possible to connect them


    • Edited by mbyforum Sunday, November 24, 2019 8:51 AM
    Sunday, November 24, 2019 8:50 AM
  • You have to install first the SCCM client and get YES in the console before using Remote Control feature.

    You can check ccmsetup.log file for more details ("%WINDIR%\ccmsetup"), or, if you install the client from the console, check ccm.log file ("SCCM install directory\Microsoft Configuration Manager\Logs").

    Don't forget to enable the Remote Control option in the Client settings, more details: https://docs.microsoft.com/en-us/configmgr/core/clients/manage/remote-control/prerequisites-for-remote-control


    Sunday, November 24, 2019 10:08 AM
  • Hi,

    After repairing the MP, how about the client status on console? And how about the actions on client in Configuration Manager Properties? 

    And as Youssef mentioned, enable Remote Control option in Client setting.

    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.

    Monday, November 25, 2019 3:01 AM
  • The clients who was None stays in None and couldn't connect them.
    The clients who was Yes in Client and couldn't connect to. Now i can connect them.

    Now i see problematic client it doesn't have "ConfigMgr Remote Control Users" Group

    Monday, November 25, 2019 8:10 AM
  • The clients who was None stays in None and couldn't connect them.
    The clients who was Yes in Client and couldn't connect to. Now i can connect them.

    Now i see problematic client it doesn't have "ConfigMgr Remote Control Users" Group

    I'm still waiting the result about SCCM client installation logs, as said in my last post.

    We need more details to help you (logs, screenshots...).

    Monday, November 25, 2019 8:54 AM
  • in ccm/log on the problematic client

    ---> Unable to connect to WMI (root\ccm) on remote machine "", error = 0x8004100e.

    Monday, November 25, 2019 9:33 AM
  • in ccm/log on the problematic client

    ---> Unable to connect to WMI (root\ccm) on remote machine "", error = 0x8004100e.

    Refer to the following similar post: https://forums.prajwaldesai.com/threads/unable-to-connect-to-wmi-root-ccm-on-remote-machine-error-0x8004100e.416/
    Monday, November 25, 2019 1:03 PM
  • This is not a fatal issue and is expected on systems without the agent installed already. When reading logs, don't just fixate on red highlighted lines as not all red highlighted lines are even errors and those that are aren't always actionable or even indicative of any fatal issues.

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

    Monday, November 25, 2019 3:45 PM
  • Thank you all
    Everything worked after the MP was corrected in the following action:
    % windir% \ system32 \ inetsrv \ appcmd.exe set config -section: system.webServer / httpCompression / - [name = 'xpress']

    One client was still problematic and we reformatted it and now it's correct

    • Marked as answer by mbyforum Wednesday, November 27, 2019 7:33 AM
    Wednesday, November 27, 2019 7:33 AM
  • Hi,

    Thank you very much for the update. I'm glad the problem is solved now. Here's a short summary for the problem.

    Problem/Symptom:
    ===================
    New client cannot be connected with the symptoms:
    On console: Client Type of client is -None
    On client in Configuration Manager Properties: Client Certificate is None
    In Actions: there is only: Machine Policy Retrieval & Evaluation Cycle, User Policy Retrieval & Evaluation Cycle.
    In Components: CCM Notification Agent is disabled

    Possible Cause:
    ===================
    SCCM client did not install correctly.
    MP issue.

    Solution:
    ===================
    MP was corrected in the following action:
    % windir% \ system32 \ inetsrv \ appcmd.exe set config -section: system.webServer / httpCompression / - [name = 'xpress']

    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.

    Monday, December 2, 2019 3:19 AM