Hi there.

I´m still at the Start of testing the TRIAL K1000 Box.
I´m not able to get any W7 Maschine into the inventory although the agent provisioning has completed without any error.
I tried everything that is mentioned within http://www.kace.com/support/kb/index.php?action=artikel&cat=3&id=713&artlang=en but no W7 is coming up.
Here´s the provisioning protocol of one of the W7 clients:

Provisioning Log
--------------------------------------------------------------------------------

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

[03/04/11 12:48:15 PM] Begin provisioning...
[03/04/11 12:48:15 PM] Executing Windows platform provisioning.
[03/04/11 12:48:15 PM] Probing tcp ports for accessibility.
[03/04/11 12:48:15 PM] Port 139 [netbios-ssn] open.
[03/04/11 12:48:15 PM] Port 445 [microsoft-ds] open.
STEP 1: CONNECT TCP/SSH - SUCCESSFUL
[03/04/11 12:48:31 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: 001] KBOX Agent is installed.
[MSGCODE: 091] AMP is connected.
[MSGCODE: 093] KUID file detected.
[MSGCODE: 094] kuid: 2108C0F2-5670-46CA-87AF-7FB4BB70549E
[MSGCODE: 100] agent_provision.bat exiting.
exit code: 0Removing service
Connecting to ADMIN$
Deleting service file
Disconnecting ADMIN$
STEP 3: PUSH SCRIPT\PROVISIONING - SUCCESSFUL
End of remote communications.
[03/04/11 12:48:31 PM] End provisioning run.
STEP 4: AMP CONNECTION - WAITING...

STEP 5: CLIENT SYNC - WAITING...

Any idea ?

Regards
Sascha
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
The K1000 fully supports Win7.
Is .NET 1.1 installed?

Is that system 64 bit Win7?

Was the Agent deployed using the Advanced Provisioning? If yes, was the option "Install .NET 1.1 on x64 Systems" enabled?

Please try again using Advanced Provisioning and enabling that option.
Answered 03/04/2011 by: tstaub
Second Degree Blue Belt

Please log in to comment
0
Based on the output of the log, it looks like the agent is installed but not communicating back to the server.

Check C-> program files (or x86 if 64 bit) -> kace -> kbox -> smmp.conf

What do you have for server?

Can your machine resolve this address?

If it can is it your KBOX?

If that doesn't work try installing the agent manually at least to see if it checks in that way.
Answered 03/07/2011 by: dchristian
Red Belt

Please log in to comment
0
Hi!

The system is a 32bit Win7 Ultimate.
The agent was deployed using "Single Maschine Provisioning" the first time.
.Net 1.1 was and is installed on the W7 client.
Now i tried "Advanced Provisioning" - first to deinstall the agent and then the second time to install.
Now the provisioning results look like this:





Suspected OS (from scan):
Windows


Action:
Agent Install


Provisioning Status:
succeeded


KBOX Agent Installed:
Yes


Error Category:
No Error




Record Last Modified:



Record Created:





Provisioning Log

[hr]



[hr]


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

STEP 1: CONNECT TCP/SSH - SUCCESSFUL

[03/09/11 09:32:48 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
IN: pipe_open(\pipe\KBRemoteService, 2)
Sending commands
Commands: //BONK1K01/client/agent_provisioning/windows_platform/agent_provision.bat BONK1K01 client BONK1K01 0 0 1
Sending login credentials
Login: GKNSMI\adm_bonacronis
[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: 091] AMP is connected.
[MSGCODE: 093] KUID file detected.
[MSGCODE: 094] kuid: 2108C0F2-5670-46CA-87AF-7FB4BB70549E
[MSGCODE: 100] agent_provision.bat exiting.
exit code: 0ERROR: smb_raw_read_recv - NT_STATUS_PIPE_DISCONNECTED
ERROR: on_pipe_error - NT_STATUS_PIPE_DISCONNECTED
Removing service
OpenService - NT_STATUS_OK
StopService - NT_STATUS_OK
DeleteService - NT_STATUS_OK
CloseServiceHandle - NT_STATUS_OK
CloseSCMHandle - NT_STATUS_OK
Connecting to ADMIN$
Deleting service file
Disconnecting ADMIN$

STEP 3: PUSH SCRIPT\PROVISIONING - SUCCESSFUL

End of remote communications.

[03/09/11 09:32:48 AM] End provisioning run.

STEP 4: AMP CONNECTION - SUCCESSFUL


STEP 5: CLIENT SYNC - WAITING...


Compared to the first provisioning results Step 4: AMP Connection is now Succesful.
But still the Client don´t came up in the inventory.

The smnp.conf looks like this:

rto=20
validationinterval=480
pl=pluginDesktopAlerts,pluginPatching,pluginWeb,pluginRunProcess
log=SMMP.log
host=BONK1K01
ampport=52230
crto=10
wto=20
webport=80
lasthost=BONK1K01
kboxver=5.1.31237
ampurl=http://BONK1K01:52230
weburl=http://BONK1K01
lastvalidation=2011-03-09T07:32:47Z

The KBOX name could be resolved by the client.

Any other ideas ?

Thanks
Sascha
Answered 03/09/2011 by: skruegerGKN
Yellow Belt

Please log in to comment
0
Not sure if I missed the responses to dChristian, but I do see a error in the logs.

smb_raw_read_recv - NT_STATUS_PIPE_DISCONNECTED

After checking some other forum posts alot of people respond back about problems between hostname values.

See the below post from GillySpy.

http://itninja.com/question/faulttree-105483&mpage=1&key=&#55483

"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
"
Answered 03/10/2011 by: Tetravaal
Senior Yellow Belt

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

Share