Kbox agent provisioning, cannot sync(windows 7)

When I try to provision kbox agent to a pc with winows 7 professional(x64) it keeps hanging on client sync. The message waiting does not go away.
The firewall of windows is disabled to exclude all problems related to the firewall.

I hope someone can help me with this.

Here's the log:

[11/27/09 09:21:53 AM] Begin provisioning...
[11/27/09 09:21:53 AM] Executing Windows platform provisioning.
[11/27/09 09:21:53 AM] Probing tcp ports for accessibility.
[11/27/09 09:21:53 AM] Port 139 [netbios-ssn] open.
[11/27/09 09:21:53 AM] Port 445 [microsoft-ds] open.


[11/27/09 09:22:15 AM] Executing remote communications:

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


Creating service
Opening pipe to service
IN: pipe_open(\pipe\KBRemoteService, 2)
Sending commands
Commands: //*servername*/client/agent_provisioning/windows_platform/agent_provision.bat *servername* client *servername* 0 0 1
Sending login credentials
Login: WORKGROUP\Administrator
[MSGCODE: 000] Begin agent_provision.bat processing.
[MSGCODE: 064] Detected 64-bit platform
[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: 091] AMP is connected.
[MSGCODE: 093] KUID file detected.
[MSGCODE: 094] kuid: 75B15E6A-1E15-479D-A0A9-470AB208F62D
[MSGCODE: 100] agent_provision.bat exiting.
exit code: 0ERROR: smb_raw_read_recv - NT_STATUS_PIPE_DISCONNECTED
Removing service
OpenService - NT_STATUS_OK
StopService - NT_STATUS_OK
DeleteService - NT_STATUS_OK
CloseServiceHandle - NT_STATUS_OK
Connecting to ADMIN$
Deleting service file
Disconnecting ADMIN$


End of remote communications.

[11/27/09 09:22:15 AM] End provisioning run.



1 Comment   [ + ] Show comment
  • Has this ever been resolved??? Any new updates on this? - rhamilton1973 8 years ago

Answers (11)

Posted by: jkatkace 13 years ago
Purple Belt
This is usually due to a dns problem. Make sure that the KBOX's name, shown as *servername* above, can be resolved from that windows 7 machine.
Posted by: RichB 13 years ago
Second Degree Brown Belt
I think its more of a permission error and this is a known issue with Windows 7. Manual install works from agent_provisioning.

Posted by: joost 13 years ago
Senior Yellow Belt
I doubt about the permission error, because I use the hidden administrator account and should be able to get acces to anything.
I will check for the dns. Could it be related to this error? smb_raw_read_recv - NT_STATUS_PIPE_DISCONNECTED
Posted by: GillySpy 13 years ago
7th Degree Black Belt
I think what jkatkace means is that the agent cannot connect back to the server because of a bad servername. AMP is connected and the agent is installed. Compare the host values in smmp.conf and config.xml -- are they the same?

If you are trying to re-provision this machine then do a prov'n that removes the agent and removes the config.xml (it's a checkbox) file and then do a standard prov'n
Posted by: joost 13 years ago
Senior Yellow Belt

DNS is not the problem as far as I know. Also the hosts in the config files are the same.
I think windows 7 is still blocking some connections or something. I do know the required ports are open because I have tested that with the IP-scan option.
However it doesn't get a mac adress or host name. So something must be wrong. I did test now on 2 different pc's, 1 with snmp settings and 1 without. Both don't work although I get a lot more info from an IP-scan with snmp on, but still no mac or DNS name(must check dns more I guess), but when I check more info, at the connection types I do see the mac adress.

[EDIT]Problem solved. I updated the client agent with a newer version.
We had a version that should be compatible with Windows 7, but probably not good enough.

Thanks for the help
Posted by: cblake 13 years ago
Red Belt
Have you checked the remote registry service? We had to make sure that was running for our Anti-Virus solution, which uses a similar provisioning process.
Posted by: skiddle 13 years ago
Yellow Belt
Check smmp.conf to ensure ssl=false, if Agent Messaging Protocol Settings has Enable SSL for AMP disabled. If smmp.conf has ssl=true, change it to false then restart the AMP service.
Posted by: bf_rob 13 years ago
Senior Yellow Belt

A little thread hijack here: Ive noticed this behavior with the latest agent. Whenever we provision or even simply install the agent on a new machine the ssl=true flag is set in SMMP.conf even though we are NOT using SSL for amp. Any ideas why this is happening? Should i just cave in and enable SSL on amp?

Posted by: skiddle 13 years ago
Yellow Belt
Well, I opted not to enable SSL on AMP. The Kace support bloke advised me this was a bug and would submit it for fixing. He also suggested I tweak agent_provision.bat to copy a properly configured SMMP.conf file to the target machine.
Posted by: airwolf 13 years ago
Red Belt
I'll have to check this in my environment. We don't have SSL enabled for AMP, and I'm fairly certain we've successfully provisioned a few agents of the latest version without any issues with the clients connecting. Glad to hear KACE is aware of the bug.
Posted by: bf_rob 13 years ago
Senior Yellow Belt
Good to know, thanks Skiddle.
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


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