Here is the results from the job.  Any suggestions on how to resolve this would be appreciated.  We are new to the KACE 1000 so learning as we go.  :-)

 [07/11/16 02:08:21 PM] Begin provisioning...

  [07/11/16 02:08:21 PM] Executing Windows platform provisioning.


  STEP 1: CONNECT TCP/SSH - SUCCESSFUL

[07/11/16 02:08:40 PM] Executing remote communications:


      Initializing RPC

      Connecting to ADMIN$

      Copying service file

      Disconnecting ADMIN$

      Connecting to IPC$
 


  STEP 2: AUTHENTICATION - SUCCESSFUL


      Opening pipe to service

      IN: pipe_open(\KBRemoteService, 7790178)

      Sending commands

      Commands: //KACEserver/client/agent_provisioning/windows_platform/agent_msi_provision.bat KACEserver client ampagent-6.4.522-x86.msi KACEserver

      Sending login credentials

      Login: TNEB\Administrator

      [MSGCODE: 000] Begin agent_msi_provision.bat processing.

      [MSGCODE: 064] Detected 64-bit platform.

      [MSGCODE: 015] Executing MSI installer.

      %s

      C:\WINDOWS\TEMP>start /wait msiexec.exe /qn /l*v C:\WINDOWS\TEMP\ampmsi.log /i \\KACEserver\client\agent_provisioning\windows_platform\ampagent-6.4.522-x86.msi HOST=KACEserver

      %s

      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


  [07/11/16 02:08:40 PM] End of remote communications.

  [07/11/16 02:08:40 PM] End provisioning run.
1 Comment   [ + ] Show Comment

Comments

  • Looks like it doesn't like the credentials you supplied. You can install the agent manually without a problem, yes? If so, check your provisioning job for accurate credentials (agent needs admin rights to install)
Please log in to comment

Answers

1
it looks like the client is not able to reach the appliance samba folder.
Does it work with non W10?
is \\KACEserver\client\agent_provisioning avaible?
Answered 07/12/2016 by: Nico_K
Red Belt

Please log in to comment
1
I can actually browse to the appliance samba folder from the Win10 PC without any issues.  I can even install the KACE agent manually using this method but I want to know what is stopping it from installing via remote push from appliance.
Answered 07/12/2016 by: candice.dean
White Belt

Please log in to comment
0
I was having the same issue. The computer in question was in a different domain, so I think the issue ultimately ended up being a combination of network qualification and authentication. The computer I was trying to push to needed to be able to communicate by to the KACE appliance, which was in a different domain. I had to fully qualify to path to the KACE appliance and specify an account in the target computer's domain and then it worked.
Answered 10/19/2016 by: JLankford
White Belt

Please log in to comment
Answer this question or Comment on this question for clarity