Failed to connect to admin share using machine account

Failed to connect to admin share using machine account

Failed to connect to admin share using machine account (5). I am not sure how many of you have come across this error. When I was working on my lab setup I installed the configuration manager and when I deployed the client agent it failed to install. When i checked the ccm.log file I saw the error Failed to connect to admin$ using machine account (5). I noticed the warning line which said “no remote client installation account found“. Now there was the mistake, I had not configured the client push installation account.

Failed to connect to admin share using machine account

So why is this account so important?. This account is used to connect to computers and install the Microsoft System Center 2012 Configuration Manager client software if you deploy clients using Client Push Installation. If the Client Push Installation account is not specified, the site server account is used to try to install the Configuration Manager 2012 client software. Note that the Client Push Installation account is not automatically created, the CM administrator needs to create it. The administrator can create multiple Client Push Installation accounts or can use a single account across multiple sites. The Client Push Installation account must be in the local administrators built-in group on the computers where the Configuration Manager 2012 client software is to be installed. The Client Configuration Manager checks for changes to the Client Push Installation account once every hour.

To specify a client push installation account, launch the Configuration Manager console, click on Administration, under Site Configuration click on Sites. At the top banner click Client Installation Settings and then click Client Push Installation. Click on Accounts tab and then click Yellow star icon.

Failed to connect to admin share using machine account

Choose the account from the AD and click on OK.

Failed to connect to admin share using machine account

8 Comments

  1. Avatar photo Abhas Kumar Samal says:

    Hi Prajwal,
    i got same issue and i follow your steps but still not working successfully. same error is coming here.

    —> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account JOHN\Administrator (0000052e) SMS_CLIENT_CONFIG_MANAGER 2/16/2020 10:23:20 PM 4424 (0x1148)

    —> ERROR: Failed to connect to the \\CAS\admin$ share using account ‘Machine Account’ SMS_CLIENT_CONFIG_MANAGER 2/16/2020 10:23:20 PM 4424 (0x1148)
    —> Failed to connect to \\cas.john.com\admin$ using machine account (67) SMS_CLIENT_CONFIG_MANAGER 2/16/2020 10:23:20 PM 4424 (0x1148)
    —> ERROR: Unable to access target machine for request: “2097152001”, machine name: “CAS”, access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 2/16/2020 10:23:20 PM 4424 (0x1148)
    Execute query exec [sp_CP_SetLastErrorCode] 2097152001, 1265 SMS_CLIENT_CONFIG_MANAGER 2/16/2020 10:23:20 PM 4424 (0x1148)

  2. Avatar photo Rajendra yadav says:

    Thanks sir i got multiple resolution from your article..

  3. Avatar photo Nikunj Kumar says:

    Thanks Prajwal !
    Was stuck with the similar issue in my lab setup.
    Got fixed now.

  4. Thanks!

  5. Thank you very much Prajwal. I had not read anything about a Client Push account when I was setting up SCCM. Your article is very informative and straight to the point.

  6. Not sure if you will ever reply to this, but I’m having hard time on this specific issue I’m using the domain admin account.

  7. HI, But what if the Client installation is already defined and still we are getting Message ID 3014,3015 and client fails to install.

    1. Avatar photo Pravin Bharti says:

      Hi, I have 2 domain, my primary domain all system hai client installed and they reporting to site. But secondary domain system showing in devices, but unable to access admin $ . Due to that it’s not reporting to site. I enabled all ports as well. Need help asap.

Comments are closed.