I can only access the Samba share for my KACE appliance using the IP address, not the DNS name.  Not sure if this is causing the issue with trying to push agents to new machines or machines that were in inventory but don't have the AMP service running on them.  When pushing agents to the IPs of known computers, keep getting this error:

 process (//SOS-Kace.sos.local/client/agent_provisioning/windows_platform/agent_msi_provision.bat SOS-Kace.sos.local client ampagent-6.3.314-x86.msi SOS-Kace.sos.local)
 could not be launched: 2 The system cannot find the file specified.
       (authenticated, but CreateProcessAsUser failed)process (//SOS-Kace.sos.local/client/agent_provisioning/windows_platform/agent_msi_provision.bat SOS-Kace.sos.local
 client ampagent-6.3.314-x86.msi SOS-Kace.sos.local) could not be launched as LocalSystem: 2 The system cannot find the file specified

Not sure if this is because it won't resolve DNS, or some other issue, but it started after the 6.3.314 updates.  

It is a reserved IP in DHCP, has a user with domain admin credentials, but fails with CreateProcessAsUser every time...

2 Comments   [ + ] Show Comments


  • When I try the work-around, it gives an error "Alternate Download Location requires a share name". Where do I specify the share name?
  • In the "Alternate Download Location" in the provisioning setup, you will need to have the IP address of the Samba share, along with the folder name that contains the provisioning installer. Also, I found out through another ITNinja article, which I will add a link to when I find it, that if provisioning is failing at the 2nd authentication, substitute the domain admin account with a local admin account that is on the machine in question. This was easy for us because we have a local admin account set through group policy.
Please log in to comment


  • When will this be fixed? Even your KB article is out of date for an issue that has been affecting K1000's all over.

    FYI, you can no longer just put in the IP address as the alternative download location. A share name is required. Supplying a share name doesn't work either since the provisioning appends the path anyways.
Please log in to comment
Answer this question or Comment on this question for clarity