/build/static/layout/Breadcrumb_cap_w.png

Systems Management Question


Devices stop checking in

03/14/2018 1009 views
Is anyone else having issues with their devices not checking in and/or showing offline?  We have several devices that have stopped checking in and show offline even though they are online.  Support is no help and we are working on deploying the patch management portion of the K1.  We are currently running SMA Version: 8.0.318 and agent version: 8.0.152.

Thanks!
2 Comments   [ + ] Show comments

Comments

  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.
  • Yes, I am.

    I just installed (or updated; I'm not sure, as I didn't check the client Mac before [re]installing the amp agent, and I [re]installed the amp agent because the client machine was not showing up in the K1).

    So the Mac (OS X 10.9.5) has a new 8.1.52 amp agent. For a few minutes today, all looked fine; it showed up in the K1 and I thought all was good. Later I tried to push a test script to the machine, and the K1 complained that it was off-line, but I was remoted into it at the very moment; it was definitely not off-line.

    So I went to an identical client Mac, and found that it already had the amp agent (8.0.152), even though it also is not showing up in the K1 inventory. While remoted to it, I ran "runkbot 2 0", "4 0", and "6 0" (I never can remember which one does what), and the client Mac seemed to report that all went well. I ran "AMPTools host=myhost", and at some point the Mac client started showing up in the K1, but as offline, like the first Mac.

    I found that "HostName" was not set on the Mac client (although LocalHostName and ComputerName were) so I "scutil --set HostName the-computername", and rebooted for good measure. It still shows up as offline in the K1.

    Very frustrating.
  • Oh, wait. Running "runkbot 6 0" again, I see some errors:

    kbot[6:0] @ 2018-05-29T16:48:39 (output) [2018-05-29.16:48:39][KDeploy:main ] KDeploy ----- Starting KDeploy.exe -----
    kbot[6:0] @ 2018-05-29T16:48:39 (output) [2018-05-29.16:48:39][KDeploy:main ] KDeploy called with params: -fs -mi -fade=1 -notifyevent=
    kbot[6:0] @ 2018-05-29T16:48:39 (output) [2018-05-29.16:48:39][KDeploy:Run ] KDeploy Have user acutech
    kbot[6:0] @ 2018-05-29T16:48:39 (output) [2018-05-29.16:48:39][KDeploy:Run ] Not bootup, checking User Context
    kbot[6:0] @ 2018-05-29T16:48:39 (output) [2018-05-29.16:48:39][KDeploy:GetDeploymentInfo ] KDeploy GetDeployInfo: State=ADHOC LoggedIn=YES KUID=8B312C6C02A046C99AF91D8F262FA826
    kbot[6:0] @ 2018-05-29T16:48:39 (output) [2018-05-29.16:48:39][KDeploy:SendServerMsg ] KDeploy INTERNAL ERROR - error returned from curl (3)
    kbot[6:0] @ 2018-05-29T16:48:39 (output) libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "OOB_ClientServerMessageFSMI" because it is missing required fields: m_type, m_KUID
    kbot[6:0] @ 2018-05-29T16:48:39 (output) [2018-05-29.16:48:39][KDeploy:SendServerMsg ] KDeploy FAILED to parse returned PB string. rx: ]
    kbot[6:0] @ 2018-05-29T16:48:39 (output) [2018-05-29.16:48:39][KDeploy:Run ] Server's response was invalid ...
    kbot[6:0] @ 2018-05-29T16:48:39 (output) [2018-05-29.16:48:39][KDeploy:main ] KDeploy ----- Ending KDeploy.exe -----
    kbot[6:0] @ 2018-05-29T16:48:39 (output)
    k

    Maybe relevant?
    • so I ran "sudo /Library/Application\ Support/Quest/KACE/bin/AMPTools uninstall all-kuid", and then made sure the entire Quest directory was gone. I deleted the record of that machine from the K1. Then I reinstalled the 8.1.52 amp agent, then ran "sudo /Library/Application\ Support/Quest/KACE/bin/runkbot 2 0" and 4 0" and "6 0".

      Same errors with the "6 0", and the Mac is not showing up at all in the K1's inventory.

All Answers

0
Probably they have the amp.conf file corrupted.

Try replacing the file with a working one or, as workaround, create in your DNS a CNAME or A "kbox" record that points to your K1000 appliance
Answered 03/15/2018 by: c.castellari
Orange Senior Belt

0
Is it everything? If so, contact kace support. I had to do that myself recently. Though the most recent patch was supposed to include the patch that worked to correct mine.
Answered 03/15/2018 by: five.
Second Degree Green Belt

 
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