/build/static/layout/Breadcrumb_cap_w.png

STEP 2: AUTHENTICATION - FAILED -[SOLVED]

My appologies from the get go, as this has probably been answered. Yet my search results come back with nothing.

Trying to deploy the agent via "Single Machine Provisioning" to Windows XP clients. This fails at:

Initializing RPC
Connecting to ADMIN$
ERROR: Failed to open connection - NT_STATUS_ACCESS_DENIED

STEP 3: PUSH SCRIPT\PROVISIONING - FAILED

End of remote communications.

[04/29/10 09:55:44 AM] End provisioning run.



Can somone point me in the right direction? Thanks in advance for your time and help.
Asked 14 years ago 23940 views
0 Comments   [ + ] Show comments

Answers (5)

Posted by: airwolf 14 years ago
Red Belt
0
Ensure your login credentials have proper access on the system to access the ADMIN$ share. Also, disable any firewall that may be running.
Comments:
  • If this machine is not on a domain, then a registry edit is needed to permit remote access by local admins to the ADMIN$ share. Here are some details.

    http://support.adminarsenal.com/entries/20828513-can-t-access-the-admin-using-a-local-user-account - flickerfly 12 years ago
Posted by: KevinG 14 years ago
Red Belt
0
Make sure that the Simple File Sharing is turn off

Troubleshooting Agent Provisioning

http://www.kace.com/support/customer/faq/index.php?action=artikel&cat=2&id=1013&artlang=en
Posted by: r00tux 14 years ago
Senior Yellow Belt
0
Thanks guys, while demoing the KACE 1100, the agent was deployed to a few systems. It was these computers failing on step 3. We ended up just removing the old instance and then provisioning the agent out again.
Posted by: flickerfly 12 years ago
Purple Belt
0

A little something extra that may be helpful to someone trying to install the client on non-domain machines:

I had to run this registry edit to enable remote local admin access to ADMIN$ found here: http://support.adminarsenal.com/entries/20828513-can-t-access-the-admin-using-a-local-user-account

 

 cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
Posted by: brucegoose03 12 years ago
5th Degree Black Belt
0

Also be sure to check NTLM settings on your clients. 

Provisioning only works through NTLM level 0-4, it will not work if set to "Send NTLM v2 only, refuse LM & NTLM" which is level 5. 

 

 

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ