Sorry - this might seem like an obvious one.
From my target PC, I cant get to \\kbox.domain.com\client, but I can hit \\kbox\client just fine. Is there a spot in the konfiguration that I missed?

My real problem is that my agents arent responding back. When deploying an agent, I have had to type kbox as the server name instead of kbox.domain.com, because otherwise I will get an error saying that a file cannot be found (\\kbox.domain.com\client...). The client pushes out with kbox as the server name, but the SMMP.conf file has incorrect values:


pl=pluginDesktopAlerts,pluginPatching,pluginWeb,pluginRunProcess
log=SMMP.log
host=kbox
lasthost=kbox.domain.com
kboxver=5.2.38773
ampport=52230
ampurl=http://kbox:52230
webport=80
weburl=http://kbox
rto=20
wto=20
crto=10



Hopefully this all makes sense! Thanks for the help!
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity

Answers

0

Provisioning Results

IP Address: 172.16.5.22
MAC Address: b8:ac:6f:ac:e7:5c [computer inventory]
Host Name (from DNS): mad1262.domain.com
Suspected OS (from scan): unknown
Action: Agent Install
Provisioning Status: failed
K1000 Agent Installed: Yes
Error Category: NETWORK related failure.
Error: CreateProcessAsUser

Record Last Modified:
Record Created:

Provisioning Log

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


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

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

STEP 1: CONNECT TCP/SSH - SUCCESSFUL

[04/29/11 09:19:00 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
process (//kbox.domain.com/client/agent_provisioning/windows_platform/agent_provision.bat kbox.domain.com client kbox.domain.com 0 0 1) could not be launched: 2 The system cannot find the file specified.
(authenticated, but CreateProcessAsUser failed)process (//kbox.domain.com/client/agent_provisioning/windows_platform/agent_provision.bat kbox.domain.com client kbox.domain.com 0 0 1) could not be launched as LocalSystem: 2 The system cannot find the file specified.
(authenticated, but CreateProcess failed); (no exit code)process could not be launched: 2; (no exit code)exit code: 0Removing service
Connecting to ADMIN$
Deleting service file
Disconnecting ADMIN$

STEP 3: PUSH SCRIPT\PROVISIONING - FAILED

End of remote communications.

[04/29/11 09:19:00 AM] End provisioning run.
Answered 04/29/2011 by: jeradw
Senior Yellow Belt

Please log in to comment
0
What do you have under network settings?

Settings -> network settings

You want to make sure that your domain matches your domain.

Also check the values for the kbox dns name and web server name.
Answered 04/29/2011 by: dchristian
Red Belt

Please log in to comment
0
It looks like there wasnt an entry in DNS for kbox. We added that to DNS along with its IP...

still testing, but I can atleast get to the shares now!

I will post back as soon as I know more
Answered 04/29/2011 by: jeradw
Senior Yellow Belt

Please log in to comment
0
Yup - looks like its working now! Did I miss a step in the instructions to make a DNS entry for KBOX, or was it supposed to do it automatically and didn't?
Answered 04/29/2011 by: jeradw
Senior Yellow Belt

Please log in to comment
0
Hi,

No the KBOX won't add itself to your DNS. You did the correct action by adding it.
Answered 04/29/2011 by: nshah
Red Belt

Please log in to comment