A few problems I am encountering while working on the trial.
First working through the guided tour, under install agent guided tour, under the Exercises, pre-requisites, for all agents the bullet:We need to add some labels and settings to your K1000 for this Guided Tour. If you've not already done this then click here to apply the changes.
You are suppose to click the "click here" (http://djjkbox11/adminui/klips/klip_setup.php) I get page not found.

Then as i'm walking through the provision for a single computer I get this one I have turned on the file/print shareing on the Kbox it self (if this is needed for the provisioning to work why is it not default) anyway. while I'm trying to push it to either a windows 2008 r2 server or a windows 7 workstation I get the same error:

[07/14/11 01:16:13 PM] Begin provisioning...
[07/14/11 01:16:13 PM] Executing Windows platform provisioning.
[07/14/11 01:16:13 PM] Probing tcp ports for accessibility.
[07/14/11 01:16:13 PM] Port 139 [netbios-ssn] open.
[07/14/11 01:16:13 PM] Port 445 [microsoft-ds] open.

STEP 1: CONNECT TCP/SSH - SUCCESSFUL

[07/14/11 01:16:19 PM] Executing remote communications:

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

STEP 2: AUTHENTICATION - SUCCESSFUL

Creating service
Opening pipe to service
Sending commands
Sending login credentials
process (//djjkbox11.kydjj.org/client/agent_provisioning/windows_platform/agent_provision.bat djjkbox11.kydjj.org client djjkbox11.kydjj.org 0 0 0) could not be launched: 2 The system cannot find the file specified.
(authenticated, but CreateProcessAsUser failed)process (//djjkbox11.kydjj.org/client/agent_provisioning/windows_platform/agent_provision.bat djjkbox11.kydjj.org client djjkbox11.kydjj.org 0 0 0) could not be launched as LocalSystem: 2 The system cannot find the file specified.
(authenticated, but CreateProcess failed); (no exit code)process could not be launched: 2; (no exit code)exit code: 0Removing service
Connecting to ADMIN$
Deleting service file
Disconnecting ADMIN$

STEP 3: PUSH SCRIPT\PROVISIONING - FAILED

End of remote communications.

[07/14/11 01:16:19 PM] End provisioning run.
1 Comment   [ + ] Show Comment

Comments

  • Hey there Kaceuser, the idea of making a manual DNS entry shouldnt have any bearing as you can just put in the IP address instead of the kace appliance name in the provisioning job. Im in the same boat with the error STEP 3: PUSH SCRIPT\PROVISIONING - FAILED even AFTER the logs show approved credentials for installation!?!?!
Please log in to comment

Community Chosen Answer

1
FYI:
Just wanted to post a quick update on this. I was able to run a manual install \\kbox\client\agent_provisioning\ (OS) then found that I was having issues with my DNS server it was not resolving the name of my KBOX server back to IP. Once I got this corrected it started working like a charm.
Answered 07/14/2011 by: Gh0stwraith
Senior Yellow Belt

Please log in to comment
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I am having the same or a similar issue. When I run the single machine provisioning there is a line in the log that says " .NET Installation failed.". I checked DNS and there were 2 computers with the same IP in the reverse lookup so I deleted the wrong one. I can ping my KACE server.

On the client, I manually ran agent_provision.bat and the result was "\\\\agent_provisioning\windows_platform\dotnetfx.exe The network path was not found.

I don't know what to try next. I have successfully provisioned other computers.

Thanks.

Jane
Answered 07/21/2011 by: jfrasier
Seventh Degree Black Belt

Please log in to comment
0
\\\\agent_provisioning\windows_platform\dotnetfx.exe

It looks like the hostname for your KBOX is not setup in DNS.
Answered 07/26/2011 by: dchristian
Red Belt

Please log in to comment
0
I too have faced this issue, at this point with no resolution. I'm simply trying to push this to my current pc and it fails over and over. This testing is not going as I had hoped.
Answered 08/02/2011 by: Papa Georgio
Yellow Belt

Please log in to comment
0
This is what I get when I try to run the script. What am I missing?

Suspected OS (from scan): unknown
Action: Agent Install
Provisioning Status: failed
K1000 Agent Installed: No
Error Category: NETWORK related failure.
Error: ERROR: Failed to copy file

Record Last Modified:
Record Created:

Provisioning Log

--------------------------------------------------------------------------------


--------------------------------------------------------------------------------

[08/03/11 11:08:57 AM] Begin provisioning...
[08/03/11 11:08:57 AM] Executing Windows platform provisioning.
[08/03/11 11:08:57 AM] Probing tcp ports for accessibility.
[08/03/11 11:08:57 AM] Port 139 [netbios-ssn] open.
[08/03/11 11:08:57 AM] Port 445 [microsoft-ds] open.

STEP 1: CONNECT TCP/SSH - SUCCESSFUL

[08/03/11 11:08:58 AM] Executing remote communications:

Initializing RPC
Connecting to ADMIN$
Copying service file
ERROR: Failed to copy file - /kbox/bin/KBRemoteService.exe - NT_STATUS_SHARING_VIOLATION

STEP 3: PUSH SCRIPT\PROVISIONING - FAILED

End of remote communications.
Answered 08/03/2011 by: Papa Georgio
Yellow Belt

Please log in to comment
0
Resolved.
Answered 08/04/2011 by: Papa Georgio
Yellow Belt

Please log in to comment
0
Hi Papa Georgio, can you tell me how you resolved this issue as I am experiencing the same problem? Thanks
Answered 08/21/2011 by: repsorp2011
Senior Yellow Belt

Please log in to comment
0
Hi Everyone,

I am also experiencing a similar issue.

The K1000 agent was installed as post installation task on a scripted install of Windows 7 Enterprise 32 bit and I am now attempting to update it by pushing it from the k1000 box. The error is C:\Program Files\kace\kbox\kinstaller_kuid Access is denied and also STEP 3: PUSH SCRIPT\PROVISIONING - FAILED.

I am able to resolve the K1000 and K2000 boxes when performing an nslookup on the Windows machine. Are there other checks which need to be performed?

IP Address: 10.8.8.2
MAC Address: (unknown)
Host Name (from DNS): 10.8.8.2
Suspected OS (from scan): unknown
Action: Agent Install
Provisioning Status: failed
K1000 Agent Installed: Yes
Error Category: No Error

Record Last Modified:
Record Created:

Provisioning Log
________________________________________
________________________________________
[08/22/11 10:39:44 AM] Begin provisioning...
[08/22/11 10:39:44 AM] Executing Windows platform provisioning.
[08/22/11 10:39:44 AM] Probing tcp ports for accessibility.
[08/22/11 10:39:44 AM] Port 139 [netbios-ssn] open.
[08/22/11 10:39:44 AM] Port 445 [microsoft-ds] open.

STEP 1: CONNECT TCP/SSH - SUCCESSFUL

[08/22/11 10:40:02 AM] Executing remote communications:

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

STEP 2: AUTHENTICATION - SUCCESSFUL

Creating service
Opening pipe to service
Sending commands
Sending login credentials
[MSGCODE: 000] Begin agent_provision.bat processing.
[MSGCODE: 001] KBOX Agent is installed.
[MSGCODE: 092] AMP is not connected.
[MSGCODE: 093] KUID file detected.
[MSGCODE: 094] kuid: D97D231A-5E11-4860-BD7E-2F56A27DC360
C:\Program Files\kace\kbox\kinstaller_kuid
Access is denied.
[MSGCODE: 100] agent_provision.bat exiting.
exit code: 0Removing service
Connecting to ADMIN$
Deleting service file
Disconnecting ADMIN$

STEP 3: PUSH SCRIPT\PROVISIONING - FAILED
Answered 08/21/2011 by: repsorp2011
Senior Yellow Belt

Please log in to comment
0
I had the same issue makeing a manualDNS entry for box K1000 & K2000 fixed the issue
Answered 11/24/2011 by: KaseUser
Orange Senior Belt

Please log in to comment
0
If the above fixes did not work for you....
1. Go on the box where you are installing the agent.
2. Manually uninstall the agent using the agent_msi_remove.bat file from the ftp share.
    Make sure you run the batch file as admin.
3.Once all old traces are removed try installing again.

I was having issues pushing the client out in a multi-domain, mpls cloud environment. Once I resolved the DNS issues as stated above I still had to manually uninstall the agent on the remote servers I tried to push to originally before provisioning again.
Answered 08/05/2014 by: h2opolo25
Red Belt

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

Share