Provisioning Results IP Address:192.168.1.3 MAC Address:4c:00:10:60:cf:1b Host Name (from DNS):192.168.1.3 Suspected OS (from scan):unknown Action:Agent Install Provisioning Status:failed KBOX Agent Installed:Yes Error Category:No Error Record Last Modified:
Record Created:
Provisioning Log
[hr]
[hr] [10/06/10 06:11:48 AM] Begin provisioning...
[10/06/10 06:11:48 AM] Executing Windows platform provisioning.
[10/06/10 06:11:48 AM] Probing tcp ports for accessibility.
[10/06/10 06:11:48 AM] Port 139 [netbios-ssn] open.
[10/06/10 06:11:48 AM] Port 445 [microsoft-ds] open.

STEP 1: CONNECT TCP/SSH - SUCCESSFUL

[10/06/10 06:12:08 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: 095] KUID file not written by kinstaller.
[MSGCODE: 100] agent_provision.bat exiting.
exit code: 0Removing service
Connecting to ADMIN$
Deleting service file
Disconnecting ADMIN$

STEP 3: PUSH SCRIPT\PROVISIONING - FAILED

End of remote communications.

[10/06/10 06:12:08 AM] End provisioning run.
what is this issue, I cant figure out this.
0 Comments   [ + ] Show Comments

Comments

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
looks like the agent got installed but couldn't talk to the server in a timely manner. At this point the issue becomes a check-in problem and should be troubleshot with this faq
Answered 10/06/2010 by: GillySpy
Seventh Degree Black Belt

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