locked
Client Push Installation Fails RRS feed

  • Question

  • Hi Everyone,

    There is something I just can't figure out.  We've configured a client push account and added it to the local admins group on the clients.  I checked the account and it was locked but we unlocked it and it is still unlocked.  Yet I get errors in the ccm.log file telling me that it can't connect.  I have a lot of errors like the following in the log: 

    ---> Attempting to connect to administrative share '\\client123\admin$' using account 'AM\sccmadmin'

    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account domainabc\sccmpush (00000035)

    Then it tries the machine account which is not in the local administrators group so I'm not suprised that it fails.

    ---> ERROR: Failed to connect to the \\1.2.3.4\admin$ share using account 'Machine Account'

    ---> ERROR: Unable to access target machine for request: "2097153834", machine name: "client123",  access denied or invalid network path.

    Execute query exec [sp_CP_SetLastErrorCode] 2097153834, 5

     

    If I add the SCCM machine name to the local administrators group it works fine but that's not what we want to do.  We want to use just the client push account.  Does anyone know what I'm missing?

    Thanks

    Thursday, February 14, 2013 6:07 PM

Answers

All replies

  • have you tried manually mapping to the remote machine using the am\sccmadmin account?

    AM, multiple domains? computer is in the AM domain?


    Rob Marshall | UK | My Blog | WMUG | File CM12 Feedback | CM12 Docs | CM12 Release Notes

    • Marked as answer by TNFamilyMan Tuesday, March 26, 2013 6:49 PM
    Thursday, February 14, 2013 7:17 PM
  • Error code 35 (hex) = 53 (decimal) = "The network path was not found."

    That's typically a DNS resolution issue.


    Jason | http://blog.configmgrftw.com

    Thursday, February 14, 2013 7:28 PM
  • I saw 00000035 not [sp_CP_SetLastErrorCode] 2097153834, 5 <--- well spotted Jason.

    ping ...


    Rob Marshall | UK | My Blog | WMUG | File CM12 Feedback | CM12 Docs | CM12 Release Notes

    Friday, February 15, 2013 10:43 AM
  • Sorry for the slow response.  I haven't had a chance to work on this issue very much lately.  I did notice yesterday that the client push account is locked out again.  This has happened multiple times so I have to wonder if someone is using the account with a service and hasn't updated the credentials (we changed the password recently).

    I'll check up on the DNS resolution.  Thanks!

    Wednesday, February 20, 2013 4:11 PM
  • It turned out on this one that the machine was having problems installing the client no matter how we did it, through client push or installing locally on the machine.  Your response got me thinking however about manually trying it out.  Thanks for the input from all parties!
    Tuesday, March 26, 2013 6:49 PM