Using kace to manage off network devices

We have 2 networks, one internal, and then a separate thats for our phone system.

the k1000 sits in the internal network,  I have setup firewall rules to allow any traffic from the phone network to or from the k1000.

I manually installed the agent on the phone system servers, and shortly afterwards they showed up in the k1000 inventory.

Everything seemed great, but now when i attempt to patch these servers they say it cant connect to the phone system servers, and managed installes also fail.

Device inventory, works with no issue.

Any ideas why this is happening?

The phone system consist of 1 hyperV host and 2 vms.

0 Comments   [ + ] Show comments

Answers (5)

Posted by: brianfulcher15 8 years ago
Orange Belt
It looks like because network 2 has no DNS server it is unable to resolve to the k1000, Is there a way to have the k1000 use IP instead of hostname for inventory, patching etc?
Posted by: nshah 8 years ago
Red Belt
You can't have separate names using deployment unless you manually install the agent with an IP or use another toll outside of kace to install the msi package with the IP address.  The amp.conf (C:\ProgramData\Dell\KACE) file would hold the host= xxxx name and that would have to be changed on the network 2 machines using either a batch or script that runs the amptools.exe found under C:\Program Files (x86)\Dell\KACE with the parameter host= IP Address. That would stop the KBOX service and change the amp.conf file and then restart. 
Posted by: brianfulcher15 8 years ago
Orange Belt
the error i get when trying to patch the phone network is handshake failed.

  • check the kagent log in programdata\dell\kace\user and see what additional detail it gives. - SMal.tmcc 8 years ago
Posted by: brianfulcher15 8 years ago
Orange Belt
this is the last bit of info i'm seeing, also can someone tell me how to put the text below in a code box?  Im new here, been trying the [code] [/code] method with no luck

[2016-03-22.16:22:02][KInventory:runInventory         ] KInventory   Inventory Capture completed and stored in C:\ProgramData\Dell\KACE\inventory.xml
[2016-03-22.16:22:02][runkbot:GetIdOfActiveUser       ] GetIdOfActiveUser: SECURITY_LOGON_TYPE: 2(18) There are no more files.

[2016-03-22.16:22:02][KCopy:UploadUsingCurl           ] UploadFile:  Server gzip compression is active
[2016-03-22.16:22:02][KCopy:GZipFile                  ] GZipFile: size of file C:\ProgramData\Dell\KACE\inventory.xml to zip is 288551
[2016-03-22.16:22:02][KCopy:UploadUsingCurl           ] UploadFile:  uploading file C:\ProgramData\Dell\KACE\inventory.xml.gz to
*   Trying
* Connected to ( port 80 (#0)
> PUT /service/inventory.php?KUID=91C4D7ED-01D9-472B-B9C5-20580CB4592A&VERSION=6.4.180 HTTP/1.1

User-Agent: Mozilla/5.0 (Windows Server 2012 R2 Standard/6.3.9600; WOW64) libcurl/7.40.0 OpenSSL/1.0.1l zlib/1.2.8 DellKACE-Agent/6.4.180


Accept: */*

KUID: 91C4D7ED-01D9-472B-B9C5-20580CB4592A

Content-Encoding: gzip

Content-Length: 24136

Expect: 100-continue

< HTTP/1.1 100 Continue

* We are completely uploaded and fine
< HTTP/1.1 200 OK

< Date: Tue, 22 Mar 2016 20:19:22 GMT

< Server: Apache

< Expires: Thu, 19 Nov 1981 08:52:00 GMT

< Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0

< Pragma: no-cache

< Set-Cookie: kboxid=76mhtjnisi4ona29m6mi4meqa3; path=/; HttpOnly

< Access-Control-Allow-Headers: x-dell-auth-timestamp, x-dell-auth-key, x-dell-auth-signature, accept, origin, content-type

< Access-Control-Allow-Origin: *

< Access-Control-Allow-Methods: PUT, DELETE, POST, GET, OPTIONS

< X-DellKACE-Appliance: k1000

< X-DellKACE-Host: kace1100s.datamail.data-management.com

< X-DellKACE-Version: 6.4.120261

< X-KBOX-WebServer: kace1100s.datamail.data-management.com

< X-KBOX-Version: 6.4.120261

< Cache-Control: private, no-cache, no-store, proxy-revalidate, no-transform

< Content-Length: 0

< Content-Type: text/html; charset=utf-8

* Connection #0 to host left intact
[2016-03-22.16:22:02][KCopy:UploadUsingCurl           ] UploadFile:  Server gzip compression cleanup.
[2016-03-22.16:22:05][AMPAgent:ClientReadCB           ] Header: msgid (726398); msgType (0)
[2016-03-22.16:22:05][AMPAgent:ClientReadCB           ] Payload: pluginId: RunProcess (6); payloadLen (37)
[2016-03-22.16:22:06][pluginRunProcess:GetIdOfActiveUs] GetIdOfActiveUser: SECURITY_LOGON_TYPE: 2(18) There are no more files.

[2016-03-22.16:22:06][runkbot:IsLoggedIn              ] IsLoggedIn: WTSGetActiveConsoleSessionId returned an inactive session(Session 1), trying  GetActiveSessionPidList
[2016-03-22.16:22:06][runkbot:GetIdOfActiveUser       ] GetIdOfActiveUser: SECURITY_LOGON_TYPE: 2(18) There are no more files.

[2016-03-22.16:22:06][KDeploy:GetIdOfActiveUser       ] GetIdOfActiveUser: SECURITY_LOGON_TYPE: 2(0) The operation completed successfully.

Posted by: brianfulcher15 8 years ago
Orange Belt
i also see these errors 

DownloadFile: 'C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots\4\ddpe_windows_inventory.ps1' error occurred: 'Could not resolve host: kace1100s.datamail.data-management.com' Error Code (6:Couldn't resolve host name), url: http://kace1100s.datamail.data-management.com/packages/kbots/4/ddpe_windows_inventory.ps1.ad74284a0a4ad1a74af2361dd4c3c5be
[2016-03-22.16:21:44][runkbot:KCopyFile               ] Error (cURL) copying files from 'http://kace1100s.data-management.com/packages/kbots/4/ddpe_windows_inventory.ps1.ad74284a0a4ad1a74af2361dd4c3c5be' to 'C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots\4\ddpe_windows_inventory.ps1': (6) Couldn't resolve host name
[2016-03-22.16:21:44][runkbot:DownloadDependency      ] Dependency download failed!

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