/build/static/layout/Breadcrumb_cap_w.png
01/06/2017 2027 views
I set up the provisioning to target one machine that does not have the agent loaded currently.
It fails on step 3 of the process.
  C:\windows\TEMP>echo off
      MSI Info: [ERROR_INSTALL_FAILURE] A fatal error occurred during installation.
      Access is denied.
      [MSGCODE: 002] K1000 Agent is not installed.
      [MSGCODE: 092] AMP is not connected.
      ERROR: The system was unable to find the specified registry key or value.
      [MSGCODE: 095] KUID value not written by MSI installer.
      [MSGCODE: 100] End agent_msi_provision.bat processing.
      OpenService - NT_STATUS_OK
      StopService - NT_STATUS_OK
      DeleteService - NT_STATUS_OK
      CloseServiceHandle - NT_STATUS_OK
      CloseSCMHandle - NT_STATUS_OK
      Connecting to ADMIN$
      Deleting service file
      Disconnecting ADMIN$
  STEP 3: PUSH SCRIPT\PROVISIONING - FAILED
  [01/06/17 11:45:42 AM] End of remote communications.
  [01/06/17 11:45:42 AM] End provisioning run.

This is the first windows 10 Surface Pro 3 I have attempted to install the agent on.
I currently am running the K1000 version 6.4.120822 and agent 6.4.522.
Thanks in advance!
3 Comments   [ + ] Show comments

Comments

  • See if this article helps at all.
    http://www.itninja.com/question/how-do-i-get-the-k1000-agent-to-install
  • Thanks for the response. The sharing options did not seem to help. I had to manually install the agent from the device.
    • the user you used to push is running in admin approval mode? (via script it cannot approve the installation request)
      • Yes the user is the network admin. I have tried it with a local admin user as well with the same results.
  • I am having the same issue. UAC is off, Network Sharing is on, the credentials of the user pushing the provision is correct (my computer), targeted user is even an administrator. I am able to reach \\KACEserver\client\agent_provisioning from the file explorer and install manually, however that is not ideal.

All Answers

0
I have had a similar experience.  I found that unlocking on using the built in Windows 10 Administrator Account resolved my issue.  The account I had created with Admin rights always gave an access denied error, but worked once I used the built in Administrator.  My guess is that it is tied into the trusted installer and the fact that the built in local administrator has the "create global object" privilege. 
Answered 01/26/2017 by: turnerjr
White Belt

  • I found I didn't have to enable the built in Administrator but did target it as the username and used the password of my one installed local admin account and it worked perfect. Seems to be a tie to the built in Administrator I guess?