none
Client Push Installation will not complete on newly imaged Windows 1909 Workstations RRS feed

  • Question

  • We've had SCCM CB installed and operating normally for well over a year with automatic client push installations occurring without any problem.  We have several new laptops that are being imaged with Windows 10 1909 and have noticed that client push is not succeeding on them since the most recent Windows updates were applied to the site server (Windows Server 2016).  All firewall rules are applied via GP and nothing has changed with that configuration or the OUs where the workstation objects are located. The ccm.log file on the server shows that the site system is connecting to the admin$ share, but the installation fails just after "Searching for SMSClientInstall.*".  The Admin$ share is accessible and the account used for the client push is a domain administrator.  Here are the ccm.log entries for one of the workstations the client will not push to.  Strange thing is that the CCMSetup folder did exist in the C:\Windows\CCMSetup folder when I first began troubleshooting this issue, but after deleting it in an attempt to manually push the agent, the client files will not copy down anymore.

    ======>Begin Processing request: "2097153255", machine name: "FNS-5300-20" SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:54:59 AM 5476 (0x1564)
    ---> Attempting to connect to administrative share '\\FNS-5300-20.FNS.ccsd.cobbk12.org\admin$' using account 'FNS\SCCMUser' SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:54:59 AM 5476 (0x1564)
    ---> Connected to administrative share on machine FNS-5300-20.FNS.ccsd.cobbk12.org using account 'FNS\SCCMUser' SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:55:00 AM 5476 (0x1564)
    ---> Attempting to make IPC connection to share <\\FNS-5300-20.FNS.ccsd.cobbk12.org\IPC$> with Kerberos authentication SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:55:00 AM 5476 (0x1564)
    ---> Searching for SMSClientInstall.* under '\\FNS-5300-20.FNS.ccsd.cobbk12.org\admin$\' SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:55:00 AM 5476 (0x1564)
    --->     ERROR: Site <998> is trying to install SMS Client on machine FNS-5300-20.FNS.ccsd.cobbk12.org. Can not push client to this machine for 24 hours. SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:55:00 AM 5476 (0x1564)
    ---> Attempting to connect to administrative share '\\FNS-5300-20\admin$' using account 'FNS\SCCMUser' SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:55:00 AM 5476 (0x1564)
    ---> Connected to administrative share on machine FNS-5300-20 using account 'FNS\SCCMUser' SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:55:00 AM 5476 (0x1564)
    ---> Attempting to make IPC connection to share <\\FNS-5300-20\IPC$> with Kerberos authentication SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:55:00 AM 5476 (0x1564)
    ---> Searching for SMSClientInstall.* under '\\FNS-5300-20\admin$\' SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:55:00 AM 5476 (0x1564)
    --->     ERROR: Site <998> is trying to install SMS Client on machine FNS-5300-20. Can not push client to this machine for 24 hours. SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:55:00 AM 5476 (0x1564)
    ---> ERROR: Unable to access target machine for request: "2097153255", machine name: "FNS-5300-20",  access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:55:00 AM 5476 (0x1564)
    Stored request "2097153255", machine name "FNS-5300-20", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:55:00 AM 5476 (0x1564)
    <======End request: "2097153255", machine name: "FNS-5300-20". SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:55:00 AM 5476 (0x1564)

    I'm at a loss.  Could someone offer some additional ideas on what might be causing this?

    Friday, January 10, 2020 4:21 PM

All replies

  • BTW, the site server was upgraded to version 1910 on 1/5/2020.
    Friday, January 10, 2020 4:32 PM
  • Are you sure that's the complete portion of the ccm.log for the targeted system?

    If you are filtering on just the system's name, you will be missing relevant and important log lines.

    Also, side question, why aren't you using ConfigMgr to "image" these systems?


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

    Friday, January 10, 2020 6:37 PM
  • Hi,

    "ERROR: Unable to access target machine for request: "2097153255", machine name: "FNS-5300-20",  access denied or invalid network path"

    Check if you have any antivirus or Windows Firewall, disable them on the same client and test again the push installation.

    What about the ccmsetup.log log file in the client? ("%WINDIR%\ccmsetup\Logs")

    Regards,

    Youssef Saad

    ______

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

    Saturday, January 11, 2020 10:35 AM
  • ccmsetup.log won't exist if client push can't connect to the remote system successfully.

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

    Saturday, January 11, 2020 8:24 PM
  • Hi,

    > Site <998> is trying to install SMS Client on machine FNS-5300-20. Can not push client to this machine for 24 hours.
    It could because of the client install lockfile, please remove:
    1.\\PCName\admin$\SMSClientInstall.XXX where XXX stands for your site code.
    2.The folder \\PCName\admin$\ccmsetup has to be deleted.

    Here is a thirt party link, just for your reference:
    https://teacheritblog.wordpress.com/2013/05/28/sccm-2012-client-push-installation-not-possible-for-24-hours/

    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, January 13, 2020 7:22 AM
  • Thank you all for your feedback.  As it turns out, the problem appears to be with the NIC dongle; we have several other laptops that were experiencing the same issue.  When the dongle was removed from the mix and the machines connected to wireless, the client pushed as expected.  Seems strange, but we have had some strange behavior from these specific Dell AIO hubs.
    Tuesday, January 14, 2020 6:06 PM
  • If you have any issue with the NIC dongle, you must have a multiple network issues not only the push installation problem, but you can try to update the driver of this dongle.

    Make sure that the IP subnet for NIC dongle is mentioned in your boundaries and boundary groups with the related MP/DP.

    From your SCCM server, try also to ping to a client with her IP address & FQDN, just to check if there is any DNS issue.
    Tuesday, January 14, 2020 7:29 PM
  • 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:
    ===================
    Several new laptops that are being imaged with Windows 10 1909 and have noticed that client push is not succeeding on them since the most recent Windows updates were applied to the site server.
    The error in ccm.log:
    ---> ERROR: Site <998> is trying to install SMS Client on machine FNS-5300-20. Can not push client to this machine for 24 hours.
    SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:55:00 AM
    5476 (0x1564)
    ---> ERROR: Unable to access target machine for request: "2097153255", machine name: "FNS-5300-20",  access denied or invalid network path.
    SMS_CLIENT_CONFIG_MANAGER 1/10/2020 10:55:00 AM
    5476 (0x1564)

    Possible Cause:
    ===================
    The problem appears to be with the NIC dongle

    Solution:
    ===================
    When the dongle was removed from the mix and the machines connected to wireless, the client pushed as expected.  

    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, January 16, 2020 8:55 AM