none
SCCM 2012 client push installation error 53 in sccm console RRS feed

  • Question

  • I tried to client push installation through sccm 2012 console but fail, the installation error is 53. The client firewall is disabled and it can successfully connect to client machine "admin$". What is problem ?   
    Sunday, September 2, 2012 4:16 AM

All replies

  • Can your push account connect to the share?

    Some other things that could cause this problem:

    - There are network connectivity problems.
    - There are name resolution issues with
    - The Remote Registry service is disabled on the client computer.
    - The Server service on the client is not started.
    - File and Printer Sharing for Microsoft Networks is not installed on the client computer

    Sunday, September 2, 2012 5:53 AM
  • What does the ccm.log on the server say? Is this the only machine with the problem or all machines?

    Also, can you remote WMI into that machine using WBEMTEST?


    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

    • Proposed as answer by ChrisDWood634 Thursday, January 14, 2016 1:29 PM
    Sunday, September 2, 2012 6:47 AM
  • use pstools (sysinternals) and see if you can connect to the admin$ using the defined client push account. Also expect to see lots of similar errors in the future. Client push is a method that requires some troubleshooting and attention. Personally I prefer to use a startup script or a GPO to install the clients.

    Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund | Mastering ConfigMgr 2012 The Fundamentals

    Sunday, September 2, 2012 7:40 AM
  • Error code 53 = "The network path was not found."

    This is often due to an offline system or the firewall blocking connectivity.

    When you say "it" can connect to admin$. what is "it"?

    Anti-malware software has also been known to prevent connections.


    Jason | http://blog.configmgrftw.com

    Sunday, September 2, 2012 7:09 PM
    Moderator
  • make sure the WMI is able to access from server to client vice versa using WBEMTEST 

    regards, Han Seen.

    Wednesday, September 5, 2012 3:10 AM
  • I tried to client push installation through sccm 2012 console but fail, the installation error is 53. The client firewall is disabled and it can successfully connect to client machine "admin$". What is problem ?   

    Any luck with this?  I have the same issue as you.

    Wednesday, December 26, 2012 8:18 PM
  • I am also having this problem (error 53) with about 250 of my roughly 1500 windows 7 workstations.  There seems to be no common denominator with these machines (other than lack of sccm client)

    I have confirmed the following characteristics on my two test cases.  Both running Windows 7 Enterprise 64bit.

    1.  I can access the admin$ share on the workstation from the sccm server using the account configured in "push" settings.

    2.  The server and browser service are both running. (have tried restarting both then re-trying the push)

    3.  The remote registry service is running. 

    4.  Windows Firewall is turned off on all connection profiles.

    I would appreciate any ideas.  I don't mind deploying with a gpo, but I'd like to try and get this figured out. (in other words, it's supposed to work right?)

    Thursday, February 7, 2013 5:11 PM
  • You need to review ccm.log for each and every client. Error code is 53 is unambiguous. Don't assume that's the error across the board though which is why you need to examine ccm.log for each.

    Jason | http://blog.configmgrftw.com

    Friday, February 8, 2013 3:33 AM
    Moderator
  • I have quite a few clients where it is half-installed and shows as 'not installed' in the console.  If I initiate a Client Push to one of those machines I get the following in CCM.log:

    ======>Begin Processing request: "2097160845", machine name: "MSJROHDE" SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:04 AM 6668 (0x1A0C)
    Execute query exec [sp_IsMPAvailable] N'PSD' SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:04 AM 6668 (0x1A0C)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:04 AM 6668 (0x1A0C)
    ---> Attempting to connect to administrative share '\\MSJROHDE\admin$' using account 'PSD\SCCMclientAdmin' SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:04 AM 6668 (0x1A0C)
    ---> The 'best-shot' account has now succeeded 21 times and failed 0 times. SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:04 AM 6668 (0x1A0C)
    ---> Connected to administrative share on machine MSJROHDE using account 'PSD\SCCMclientAdmin' SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:04 AM 6668 (0x1A0C)
    ---> Attempting to make IPC connection to share <\\MSJROHDE\IPC$> SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:04 AM 6668 (0x1A0C)
    ---> Searching for SMSClientInstall.* under '\\MSJROHDE\admin$\' SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:04 AM 6668 (0x1A0C)
    ---> System OS version string "6.1.7601" converted to 6.10 SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:05 AM 6668 (0x1A0C)
    ---> Mobile client on the target machine has the same version, and 'forced' flag is turned on. SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:05 AM 6668 (0x1A0C)
    ---> Creating \ VerifyingCopying exsistance of destination directory \\MSJROHDE\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:05 AM 6668 (0x1A0C)
    ---> Copying client files to \\MSJROHDE\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:05 AM 6668 (0x1A0C)
    ---> Copying file "D:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "MobileClient.tcf" SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:05 AM 6668 (0x1A0C)
    Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:06 AM 7312 (0x1C90)
    Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:06 AM 7312 (0x1C90)
    Waiting for change in directory "D:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:06 AM 7312 (0x1C90)
    ---> Copying file "D:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "ccmsetup.exe" SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:16 AM 6668 (0x1A0C)
    ---> Created service "ccmsetup" on machine "MSJROHDE". SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:18 AM 6668 (0x1A0C)
    ---> Started service "ccmsetup" on machine "MSJROHDE". SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:18 AM 6668 (0x1A0C)
    ---> Deleting SMS Client Install Lock File '\\MSJROHDE\admin$\SMSClientInstall.PSD' SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:18 AM 6668 (0x1A0C)
    Execute query exec [sp_CP_SetLastErrorCode] 2097160845, 0 SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:18 AM 6668 (0x1A0C)
    ---> Completed request "2097160845", machine name "MSJROHDE". SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:18 AM 6668 (0x1A0C)
    Deleted request "2097160845", machine name "MSJROHDE" SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:18 AM 6668 (0x1A0C)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097160845, 4 SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:18 AM 6668 (0x1A0C)
    Execute query exec [sp_CP_SetLatest] 2097160845, N'03/12/2013 14:36:18', 13 SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:18 AM 6668 (0x1A0C)
    <======End request: "2097160845", machine name: "MSJROHDE". SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:18 AM 6668 (0x1A0C)

    Tuesday, March 12, 2013 2:44 PM
  • ---> Started service "ccmsetup" on machine "MSJROHDE". SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:18 AM 6668 (0x1A0C)
    [...]
    Execute query exec [sp_CP_SetLastErrorCode] 2097160845, 0 SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:18 AM 6668 (0x1A0C)
    <======End request: "2097160845", machine name: "MSJROHDE". SMS_CLIENT_CONFIG_MANAGER 3/12/2013 9:36:18 AM 6668 (0x1A0C)

    Nothing to worry about here. The first line indicates success. The liine in bold just tells that there was NO error: SetLastErrorCode 0

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, March 12, 2013 6:48 PM
  • Hmmm.  Machine still shows no client installed in the console, though.
    Tuesday, March 12, 2013 7:35 PM
  • Examine ccmsetup.log (%windir%\ccmsetup\Log) then.

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, March 12, 2013 7:44 PM
  • I ran 'ccmsetup.exe /uninstall' through PSEXEC.  After I watched the CCMSETUP.LOG for it to finish successfully, I did a Client Push through the console and it installed just fine.  The questions are:

    1. Why won't the Client Push repair/reinstall broken clients?
    2. Why are the clients broken to begin with - Half installed after OSD TS?

    Tuesday, March 12, 2013 9:45 PM