none
Primary Site Server very slow after turning to https only mode RRS feed

  • Question

  • I have PS installed in my lap in 2016, since then it has been upgraded with every build so far. Because of new MBAM, I updated to 1910 early ring and turn the site to https only.

    I have HyperV host with 32gb of ram, now the PS which is virtual VM has;

    - 18gb of ram
    - SQL memory min. 4096 - max. 10240
    - enough disk space of any disk partition
    - No significant disk I/O load using Resource Monitor, but as new object, I see lot of .msg and .que files running around from \ServiceData\Messaging folder.
    - CPU usage normal
    - Memory 16gb used, 1,5gb standby, 50mb free
    - SQL 2016 uses 130 as compatibility level

    I already done

    - Windows Server 2016 patched up with latest CU
    - SQL 2016 patched up with latest CU
    - sfc /scannow run
    - CM DB optimixed with Ola's script

    Problem - everything is slow from a server site, not only CM console. Opening any new object of OS takes long time. Also I see, that the HDD LED of my physical Hyper-V host is loading 100%. All these problems started after I updated to 1910 and turned the site to https only


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

    Monday, December 16, 2019 9:37 AM

Answers

  • I uninstalled ccm client from the primary server. The thing was, that these logs behind CCM and installation folder were killing my I/O and based on Resource Monitoring, I got hands on, what's going on and what specificly the SCCM engine is really doing. 

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

    Monday, December 16, 2019 9:52 PM
  • Also the solution to fix the ccm client on Primary Site to delete the Device Record and delete smscfg.ini from C:\Windows. Deleting .ini file is important, it did generate new GUID. 

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

    Thursday, December 19, 2019 3:32 PM

All replies

  • I see this log on PS running like crazy all the time.


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

    Monday, December 16, 2019 6:14 PM
  • Found more interesting stuff, this log keep jerking around all night long ;)


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

    Monday, December 16, 2019 7:40 PM
  • Your screenshots are not sticking. Why post screenshots of text log files though?

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

    Monday, December 16, 2019 7:45 PM
  • ClientAuth.log on PS is running every seconds all the time:

    Client '17a6d211-66fa-48fd-b8e2-8bdda9d5a30d' is unknown or has an invalid key registered in the database. ClientAuth 16.12.2019 21:20:00 2732 (0x0AAC)

    Error verifying message from client '17a6d211-66fa-48fd-b8e2-8bdda9d5a30d' (0x87d0025e). ClientAuth 16.12.2019 21:20:00 2732 (0x0AAC)


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

    Monday, December 16, 2019 8:00 PM
  • I uninstalled ccm client from the primary server. The thing was, that these logs behind CCM and installation folder were killing my I/O and based on Resource Monitoring, I got hands on, what's going on and what specificly the SCCM engine is really doing. 

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

    Monday, December 16, 2019 9:52 PM
  • Hi,

    Thank you very much for the update and sharing the solution here. I'm believe this should be useful for someone who has similar issue in the future. Here's a short summary for the problem.

    Problem/Symptom:
    ===================
    After upgrade to 1910 and turned the site to https only, everything is slow from primary site, not only CM console. Opening any new object of OS takes long time. 
    ClientAuth.log on PS is running every seconds all the time:
    Client '17a6d211-66fa-48fd-b8e2-8bdda9d5a30d' is unknown or has an invalid key registered in the database. ClientAuth 16.12.2019 21:20:00 2732 (0x0AAC)
    Error verifying message from client '17a6d211-66fa-48fd-b8e2-8bdda9d5a30d' (0x87d0025e). ClientAuth 16.12.2019 21:20:00 2732 (0x0AAC)

    Possible Cause:
    ===================
    The logs behind CCM and installation folder were killing I/O and based on Resource Monitoring,

    Solution:
    ===================
    Uninstall the ccm client from primary server.

    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.

    Tuesday, December 17, 2019 3:02 AM
  • See the entire story here: https://twitter.com/_yannara_/status/1206817428631703552/photo/1

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

    Tuesday, December 17, 2019 6:17 AM
  • Hi,

    Thanks for sharing the link.
    Have a nice day!

    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.

    Tuesday, December 17, 2019 6:35 AM
  • Have you tried reinstalling the client agent to see if the issue happens again?

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

    Tuesday, December 17, 2019 3:48 PM
  • Have you tried reinstalling the client agent to see if the issue happens again?

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

    Not yet but yea, thought of that. I remember in SCCM 2007, the ccm agent was must to be present to everything work, but I am not sure what is the "best practise" to this matter in CB?

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

    Tuesday, December 17, 2019 6:29 PM
  • The agent has never been required on the primary site server and there is no best practice (there's no such thing as best practices) for agent installation on the site server. Agent installation criteria on the site server is the same as any other system: do you want to mange it or not?

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

    Tuesday, December 17, 2019 6:36 PM
  • Have you tried reinstalling the client agent to see if the issue happens again?

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

    Yes, clientauth.log will give the same error, but there is no 1sec repeat anymore. 

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

    Thursday, December 19, 2019 9:16 AM
  • Also the solution to fix the ccm client on Primary Site to delete the Device Record and delete smscfg.ini from C:\Windows. Deleting .ini file is important, it did generate new GUID. 

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

    Thursday, December 19, 2019 3:32 PM
  • Hi,

    Thanks for the supplement, have a update for the summary:

    Problem/Symptom:
    ===================
    After upgrade to 1910 and turned the site to https only, everything is slow from primary site, not only CM console. Opening any new object of OS takes long time. 
    ClientAuth.log on PS is running every seconds all the time:
    Client '17a6d211-66fa-48fd-b8e2-8bdda9d5a30d' is unknown or has an invalid key registered in the database. ClientAuth 16.12.2019 21:20:00 2732 (0x0AAC)
    Error verifying message from client '17a6d211-66fa-48fd-b8e2-8bdda9d5a30d' (0x87d0025e). ClientAuth 16.12.2019 21:20:00 2732 (0x0AAC)

    Possible Cause:
    ===================
    The logs behind CCM and installation folder were killing I/O and based on Resource Monitoring,

    Solution:
    ===================
    Uninstall the ccm client from primary server. Delete the Device Record and delete smscfg.ini from C:\Windows. Deleting .ini file is important, it did generate new GUID

    Reference Links:
    ===================
    https://twitter.com/_yannara_/status/1206817428631703552/photo/1

    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.

    Friday, December 20, 2019 8:51 AM
  • This entire scenario happends again, if I take away the CA root cert and DP cert. 

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

    Friday, December 27, 2019 4:41 PM