I have a whole bunch of laptops and workstations that are scattered all over the area that I would like to manage with my new Kace 1100 server.  

so far I am able to connect to the webserver of the KACE, and download the client and then install it.  But the KACE never sees it.  

I get this error  " GetServiceStatus: OpenService (ERROR): 1060"

but everything else seems to be fine, It finds the server at port 

I get this "Detect AMP connection: http://kace.domain.com:52230"

what other ports should I have open for this action, I have 52230, 80, 443, is there something else I am missing.   I read something that terrified me, someone said that the workstations have to be VPN'd to the server, so that both sides ports are exposed to each other.  this is not going to happen, I have too many users who are connected at home, and no reason for a VPN since the software they use is just public cloud stuff or local installed software.  no reason for a VPN , not to mention, I could never get them to connect to the VPN for just the heck of it.

Please help me here. 

0 Comments   [ + ] Show Comments


Please log in to comment



  Feel free to post a copy of the deployment log from the agent.

  If the remote machines can't communicate with the K1K, it won't work.  There are two common ways to do this.  The first is to have remote machines connect to the office LAN with a VPN.  The second is to place the K1K on your DMZ so that it is open to the internet.  If you do place the K1K on the DMZ, I highly recommend talking to support to enable SSL and make sure it is otherwise secured.

  Once you have a method for your clients to reach the KACE, you have to make sure the proper ports are open on both sides.  If you have a firewall, you'll have to open the path between the clients and the KACE.  You would be using some combination of 80, 443, and 52230.  Deploying the agent also requires 139 and 445.

  The next thing to check, since you can connect to the website of your K1K, is that you have the right hostname defined.  Make sure that the K1K IP can be resolved via DNS from the client, and that the client can reach the name set in Settings -> Control Panel -> Network for the DNS Hostname and the Web Server Name.

  Next, make sure you can connect to the share on the K1K from the client.  Test that you can reach the \\yourK1K\client share from the client you are installing the agent on.

  Make sure the client has an exception in its firewall for the KACE.  Often things like Windows Firewall can get in the way.  It's easy to test by turning it off for a moment and seeing if that fixes the issue; you can configure it if it turns out to be the cause.

  Check that the KACE Agent is properly installed.  If you are using the latest 5.3 agent, the settings are split between two folders:

    C:\Program Files (x86)\Dell\KACE or C:\Program Files\Dell\KACE


  Check that the following files exist:




  •   If SMMP.conf does not exist, remove and reinstall the agent

  If SMMP_SERVICE_STARTED does not exist, check that the KBOX SMMP Management Service exists in services.msc. If it does not, remove and reinstall the agent, otherwise, start the service.  Continue by checking for the SMMP_CONNECTED file.

  •   If SMMP_CONNECTED is the only thing missing, check that the SMMP.conf file is valid.  The SMMP.conf file should match the same file on a working machine.  If it is not valid, restart the AMP connection with the resetconf flag as below.  You will have to restart the AMP connection to the machine if you replace the SMMP.conf file, or if the SMMP_CONNECTED file is missing.

  Restart the AMP connection.  With a local machine session, open a command prompt, change directories to the KACE Agent location, and run

AMPTools.exe -resetconf host=yourk1khostname
    From a remote machine with psexec.exe

  You can do this from a remote machine with psexec.exe from the PSTools suite.  Change directories to the psexec.exe location.

psexec \\computername <KACE Agent Location>\AMPTools.exe -resetconf host=yourk1khostname  

  Wait for the command to finish. It should stop (if necessary) and start the SMMP service, then exit with code 0.  If it does not successfully start the service, check that the service has not been disabled.  If it does not exit with code 0, you will need to reinstall the agent.

  If this is the second time you have fixed a corrupt SMMP.conf file, run

AMPTools.exe -debug=true -resetconf host=yourk1khostname

  Check that there is a KBOT_LOG.txt

  If this is the third time you have fixed a corrupt SMMP.conf file, copy the KBOT_LOG.txt to send to support

  Once you reset the AMP connection, you should see the file SMMP_CONNECTED get generated.  If you still do not see this, something is blocking access back to the KACE.

  Wait for a while after you have restarted the AMP connection, and check that the computer is now in inventory. If it is now connected via AMP, but has not checked in, force a checkin on the client.

  More help can be found here:


Answered 06/08/2012 by: philologist
Red Belt

  • A configuration for the K1000 in the DMZ:

    SSL documentation:

    Precautions before Implementing SSL

    How do I configure my KBOX to support SSL?

    How do I configure LDAPS (Secure LDAP) for my KBOX?

    Which network ports does the KACE K1000 appliance require to function?
Please log in to comment
Answer this question or Comment on this question for clarity