When we try to provision a Windows 7, 64 bit machine we get the following error: 

K1000 Agent Provisioning : "X.X.X.X"

IP Address: X.X.X.X
Host Name (from DNS): X.Y.Z.com
Suspected OS (from scan): unknown
Action: Agent Install
Provisioning Status: failed
K1000 Agent Installed: No
Error Category: No Error
Record Created: 2012/09/05 16:32:39
Record Last Modified: 2012/09/05 16:32:39
Provisioning Log

  [09/05/12 04:31:44 PM] Begin provisioning...
  [09/05/12 04:31:44 PM] Executing Windows platform provisioning.
  [09/05/12 04:31:44 PM] Probing tcp ports for accessibility.
  [09/05/12 04:31:44 PM] Port 139 [netbios-ssn] open
  [09/05/12 04:31:44 PM] Port 445 [microsoft-ds] open


  [09/05/12 04:31:47 PM] Executing remote communications:

      Initializing RPC
      Connecting to ADMIN$
      Copying service file
      Disconnecting ADMIN$
      Connecting to IPC$


      Creating service
      Opening pipe to service
      IN: pipe_open(\pipe\KBRemoteService, 2)
      Sending commands
      Commands: cmd /c IF EXIST "%ProgramFiles(x86)%\Dell\KACE\AMPTools.exe" ("%ProgramFiles(x86)%\Dell\KACE\AMPTools.exe" -uninstall) ELSE "%ProgramFiles%\Dell\KACE\AMPTools.exe" -uninstall
      Sending login credentials
      Login: X.Y.Z.COM\administrator
      The system cannot find the path specified.
      exit code: 1ERROR: smb_raw_read_recv - NT_STATUS_PIPE_DISCONNECTED
      Removing service
      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$


      End of remote communications.
  [09/05/12 04:31:47 PM] End provisioning run.
We have not tried with an XP machine yet, that's the next step.  If we manually run the agent.msi package it installs and gets picked up by Kace but we want to get it working using Advanced and Auto Provisioning.  Windows Firewall is disabled, Antivirus was turned off, UAC was disabled, no password was set for the samba share.  Any ideas?
Answer Summary:
0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer



This has been resolved.  We changed the default share name to "kace client" however when it created the share it was just creating a share named the default "client".  When the kbox tried to push the installation it was sending the client to a share that didn't exist.

Answered 09/06/2012 by: Bogen
White Belt

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



Is this observed just on 1 Win 7 x64 machine are all?

Answered 09/06/2012 by: AbhayR
Eighth Degree Black Belt

  • So far, in terms of testing prior to our implementation, this has been observed on every machine we tried. 3x Win 7 x64, 3x Win 7x32 and 3x Win XP.
Please log in to comment

As an update this may or may not be related to the issue:

When originally creating the samba share an admin password was specified.  After having some issues we stopped the share, rebooted the kbox, then started the share again (this time without specifying the password).

We believe this is related because even after restarting the share and not specifying the admin password, when you browse manually  to it using \\X.X.X.X and try to access the "clientdrop" folder it prompts you for the username and password which is the original one that was set.  It doesn't prompt us for a password to access the "client" folder.

Strangely enough the contents of each the "client" and "clientdrop" folder look identical.  I don't know why there would be two different shares and why one requires password and the other doesn't.  

If that's the case aside from the original question to resolve this issue, my side questions would be why are there two folders, can we tell it to use one over the other, if the password was originally set why doesn't this information get passed over to the clients to access the folder and how would we go about wiping the password completely?

Answered 09/06/2012 by: Bogen
White Belt

  • The client folder is read only. Clientdrop is how you would add files to the client folder once you have mapped clientdrop.
Please log in to comment