/build/static/layout/Breadcrumb_cap_w.png

Provisioning of 1st Test System Fails

1st attempt of provisioning of a XP SP3 box has failed due to AMP. What can I do to resolve this? Any help appreciated. How do Provisioning log follows:

[08/05/10 08:32:24 PM] Begin provisioning...
[08/05/10 08:32:24 PM] Executing Windows platform provisioning.
[08/05/10 08:32:24 PM] Probing tcp ports for accessibility.
[08/05/10 08:32:24 PM] Port 139 [netbios-ssn] open.
[08/05/10 08:32:24 PM] Port 445 [microsoft-ds] open.

STEP 1: CONNECT TCP/SSH - SUCCESSFUL

[08/05/10 08:32:53 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: 011] .NET 1.1 is installed
[MSGCODE: 015] Executing KInstallerSetupSilent.msi
...Return code (MSI_ERROR_LEVEL) from MSI execution: [0]
MSI Info: [ERROR_SUCCESS] The action completed successfully.
[MSGCODE: 001] KBOX Agent is installed.
.[MSGCODE: 092] AMP is not connected.
[MSGCODE: 093] KUID file detected.
[MSGCODE: 094] kuid: F0B4D9C3-D37A-4F12-BAD0-BCFE9EB879C7
[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.

[08/05/10 08:32:53 PM] End provisioning run.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: chrisgrim 14 years ago
Senior Purple Belt
0
rfabian,

Amp is the protocol from client to server that works as queuing mechnism. It is outbound from the client to the K1 over port 52230. So, first thing to check is that when you set up your network settings, that you made changed the Web Server Host Name to something that is resolvable from the clients. The default is kbox and if you don't add kbox to DNS or change this value to either the IP address or a resolvable hostname, the agent will be provisioned to a non-resolvable address and you will see this behavior. If the hostname is valid, check c:\program files\kace\kbox\smmp.conf to make sure the hostname in the client config file is the same address as the network settings on the K1. If not, you can uninstall and reinstall the agent, or edit the SMMP.conf file and stop / start the KBOX agent config and you should be good.
Posted by: rfabian 14 years ago
Senior Yellow Belt
0
Thanks 'chrisgrim.' Your answer pointed me 100% to the right configuration issue. Providing the correct 'KBOX Web Server Name' now allows AMP communications.
I have to say that the configuration instructions for setting up the K1000 trial vm seemed to indicate that the default name of 'KBOX' should not be changed. Since I did not understand the underlying function and requirements, I left the defaults.
Posted by: srhctech 14 years ago
Yellow Belt
0
I am experiencing the same issues with getting a test machine to provision. I have tried using device name, fqdn, and ipaddress and each gives the same results. Here is the results text:
[blockquote]
Provisioning Results
IP Address: 192.168.64.129 MAC Address: 00:0c:29:98:29:dd [computer inventory] Host Name (from DNS): 192.168.64.129 Suspected OS (from scan): unknown Action: Agent Install Provisioning Status: failed KBOX Agent Installed: No Error Category: No Error Record Last Modified: Record Created: Provisioning Log

[hr]



[hr]


[10/20/10 02:29:45 PM] Begin provisioning...
[10/20/10 02:29:45 PM] Executing Windows platform provisioning.
[10/20/10 02:29:45 PM] Probing tcp ports for accessibility.
[10/20/10 02:29:45 PM] Port 139 [netbios-ssn] open.
[10/20/10 02:29:45 PM] Port 445 [microsoft-ds] open.

STEP 1: CONNECT TCP/SSH - SUCCESSFUL

[10/20/10 02:30:47 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
Removing service
Connecting to ADMIN$
Deleting service file
Disconnecting ADMIN$

STEP 3: PUSH SCRIPT\PROVISIONING - FAILED

End of remote communications.

[10/20/10 02:30:47 PM] End provisioning run.[/blockquote]
SMMP.conf file contents:
[blockquote]
kboxver=5.1.31237
rto=20
ampurl=http://192.168.64.100:52230
splashtext=KBOX is verifying your PC Configuration and managing software updates. Please Wait...
validationinterval=480
companyname=Salina Regional Health Center
weburl=http://192.168.64.100
pl=pluginDesktopAlerts,pluginPatching,pluginWeb,pluginRunProcess
log=SMMP.log
lastvalidation=2010-10-20T18:47:23Z
host=192.168.64.100
ampport=52230
lasthost=kbox
crto=10
wto=20
webport=80[/blockquote]
and finally the SMMP.log contents:
[blockquote]
[Wed Oct 20 13:47:21 2010] Config: debug: false
[Wed Oct 20 13:47:21 2010] Config: config: SMMP.conf
[Wed Oct 20 13:47:21 2010] Config: log: SMMP.log
[Wed Oct 20 13:47:21 2010] Config: host: 192.168.64.100
[Wed Oct 20 13:47:21 2010] Config: lasthost:
[Wed Oct 20 13:47:21 2010] Config: kboxver:
[Wed Oct 20 13:47:21 2010] Config: ampport: 52230
[Wed Oct 20 13:47:21 2010] Config: ampurl:
[Wed Oct 20 13:47:21 2010] Config: webport: 443
[Wed Oct 20 13:47:21 2010] Config: weburl:
[Wed Oct 20 13:47:21 2010] Config: rto: 20
[Wed Oct 20 13:47:21 2010] Config: wto: 20
[Wed Oct 20 13:47:21 2010] Config: crto: 10
[Wed Oct 20 13:47:21 2010] Config: krash: false
[Wed Oct 20 13:47:21 2010] Config: lastvalidation:
[Wed Oct 20 13:47:21 2010] Config: validationinterval: 480
[Wed Oct 20 13:47:21 2010] Config: pl: pluginDesktopAlerts,pluginPatching,pluginWeb,pluginRunProcess
[Wed Oct 20 13:47:21 2010] Machine ID: B3F2FA43-8B97-455C-903A-6C25420419F7
[Wed Oct 20 13:47:23 2010] Creating Pipe Server...
[Wed Oct 20 13:47:23 2010] Creating Agent Listener...
[Wed Oct 20 13:47:23 2010] Creating scheduler...
[Wed Oct 20 13:47:23 2010] Creating connection...
[Wed Oct 20 13:47:25 2010] Connection established...
[Wed Oct 20 13:47:30 2010] Header: msgid (1); msgType (0)
[Wed Oct 20 13:47:30 2010] Payload: plugid (6); payloadLen (15)
[Wed Oct 20 13:47:59 2010] Header: msgid (2); msgType (0)
[Wed Oct 20 13:47:59 2010] Payload: plugid (0); payloadLen (14)
[Wed Oct 20 13:47:59 2010] pluginZero: payload 'CACHESTATUS
'
[Wed Oct 20 13:48:27 2010] Header: msgid (3); msgType (0)
[Wed Oct 20 13:48:27 2010] Payload: plugid (6); payloadLen (24)
[Wed Oct 20 13:48:54 2010] Header: msgid (4); msgType (0)
[Wed Oct 20 13:48:54 2010] Payload: plugid (5); payloadLen (110)
[Wed Oct 20 13:49:20 2010] Header: msgid (5); msgType (0)
[Wed Oct 20 13:49:20 2010] Payload: plugid (5); payloadLen (128)
[Wed Oct 20 13:49:47 2010] Header: msgid (6); msgType (0)
[Wed Oct 20 13:49:47 2010] Payload: plugid (5); payloadLen (124)[/blockquote]
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ