Good day all!

I'm experiencing an issue when attempting to deploy the agent to my test group:


IP Address: 192.168.1.227
MAC Address: 00:50:56:ac:00:06
Host Name (from DNS): 192.168.1.227
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

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


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

[03/29/11 04:42:37 PM] Begin provisioning...
[03/29/11 04:42:37 PM] Executing Windows platform provisioning.
[03/29/11 04:42:37 PM] Probing tcp ports for accessibility.
[03/29/11 04:42:37 PM] Port 139 [netbios-ssn] open.
[03/29/11 04:42:37 PM] Port 445 [microsoft-ds] open.

STEP 1: CONNECT TCP/SSH - SUCCESSFUL

[03/29/11 04:42:56 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
[MSGCODE: 000] Begin agent_provision.bat processing.
[MSGCODE: 064] Detected 64-bit platform
[MSGCODE: 001] KBOX Agent is installed.
.[MSGCODE: 092] AMP is not connected.
[MSGCODE: 093] KUID file detected.
[MSGCODE: 094] kuid: 7A493585-7A1B-4014-8BC7-FBAC9F4299D9
[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.

[03/29/11 04:42:56 PM] End provisioning run.

I was able to manually install the agent however it is not reporting back. Any help is appreciated.

Thank you!
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
From App Deploy...
Answered 03/29/2011 by: aaron1
Senior Yellow Belt

Please log in to comment
0
NVM... The issue was due to installing the agent manually before correcting the DNS name issues... Meaning I named the appliance kbox-test however I added a DNS entry call KACE.... Removing the agent manually then letting it push out was the correct way....
Answered 03/29/2011 by: aaron1
Senior Yellow Belt

Please log in to comment
0
Also, provisioning will declare it a failure if the agent does not connect back to server in a certain period of time(don't know the exact condition). In both cases the agent is installed. For those reading you might want to check inventory to see if it checked in. All else being equal, if you are provisioning multiple machines then it is very likely that the symptoms of one will be symtpoms of the rest.
Answered 03/29/2011 by: GillySpy
Seventh Degree Black Belt

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

Share