/build/static/layout/Breadcrumb_cap_w.png

K1000 Agent Deployment on OS X 10.9.3

I can't get a single machine provisioning push to complete successfully on any Mac (Air, Mac Book Pro, Mac Mini)
Why won't the installed agent connect to AMP
Log file below...
[07/24/14 11:47:16 AM] Begin provisioning...

  [07/24/14 11:47:16 AM] Executing Unix platform provisioning.

  [07/24/14 11:47:16 AM] Probing tcp ports for accessibility.

  [07/24/14 11:47:16 AM] Port 22 [ssh] open.


  STEP 1: CONNECT TCP/SSH - SUCCESSFUL



  STEP 2: AUTHENTICATION - SUCCESSFUL


  [07/24/14 11:47:17 AM] Target is osx-x86_64.

  [07/24/14 11:47:18 AM] K1000 agent NOT detected via ssh query.

  [07/24/14 11:47:18 AM] Attempting remote agent installation.

  [07/24/14 11:47:18 AM] Copying K1000 agent installer.

  [07/24/14 11:47:18 AM] Running K1000 agent installer.


    mp /Volumes/Dell_KACE dev /dev/disk2s2

    installer: Package name is Dell KACE Agent

    installer: Upgrading at base path /

    installer: The upgrade was successful.

    "disk2" unmounted.

    "disk2" ejected.


  [07/24/14 11:47:37 AM] Verifying installation.


  STEP 3: PUSH SCRIPT\PROVISIONING - FAILED


  [07/24/14 11:47:38 AM] K1000 agent detected via ssh query.

  [07/24/14 11:47:38 AM] Version is 5.4.10622.

  [07/24/14 11:47:38 AM] K1000 agent KUID: 8D4ED259085349C297CD0A6EEE0AC3CF

  [07/24/14 11:47:38 AM] K1000 agent NOT connected via AMP.

  [07/24/14 11:47:38 AM] End provisioning run. 

5 Comments   [ + ] Show comments
  • Are you trying to upgrade current agents or deploy to new systems? This log looks like it is attempting to upgrade a current agent which I find doesn't work well through provisioning, you have to first uninstall the agent and then install. - chucksteel 9 years ago
    • I've tried to push out the agent several times which may explain why it looks like it is trying to upgrade. I've tried to use the single machine provisioning to uninstall with no luck. Where are the agent files kept in the OS X so I can manually remove them from there? - Tderrick 9 years ago
      • The log seems to indicate that the agent is present so it's possible that they just aren't checking in for some reason. The files are stored in /Library/Application Support/Dell/KACE.

        See this KB article for an uninstall command:
        http://www.kace.com/support/resources/kb/solutiondetail?sol=121173 - chucksteel 9 years ago
  • I found no evidence of any KACE agent files on the test Mac Mini. Nothing what so ever. - Tderrick 9 years ago
  • I'm having the same issues/error message - were you able to figure it out? - kvan1414 9 years ago
  • Issue was not resolved, still not a single mac successfully communicating with the KACE. I haven't had time for more testing without new information on the problem. The IT Director doubts the KBOX's stability with Mac Hardware at this point. - Tderrick 9 years ago
    • Have you contacted support? I manage close to 500 Macs with my KBOX. - chucksteel 9 years ago
  • No, I have not yet contacted support as it is not a critical issue, currently we only have 5 macs on the network. what is the best way to contact support on issues like these? - Tderrick 9 years ago
    • I usually click the "Report a Problem" link on the bottom right corner of the administrator interface and fill out the form. - chucksteel 9 years ago

Answers (2)

Posted by: erik.ragan 9 years ago
Senior Yellow Belt
0
The 5.4.x builds of the K1000 agent do not support OS X 10.9. That support was introduced in version 5.5.x of the K1000 server and agent. The most up-to-date (GA) version is 6.0. I definitely recommend upgrading, not only for OS support, but the new features as well.

Comments:
  • Forgot to include this link.... Supported OS matrix.
    http://www.kace.com/support/resources/kb/solutiondetail?sol=111298 - erik.ragan 9 years ago
  • So I upgraded the version and... same problem
    The agent won't connect via AMP!

    [08/05/14 09:48:22 AM] Begin provisioning...

    [08/05/14 09:48:22 AM] Executing Unix platform provisioning.

    [08/05/14 09:48:22 AM] Probing tcp ports for accessibility.

    [08/05/14 09:48:22 AM] Port 22 [ssh] open.


    STEP 1: CONNECT TCP/SSH - SUCCESSFUL



    STEP 2: AUTHENTICATION - SUCCESSFUL


    [08/05/14 09:48:23 AM] Target is osx-x86_64.

    [08/05/14 09:48:24 AM] K1000 agent NOT detected via ssh query.

    [08/05/14 09:48:24 AM] Attempting remote agent installation.

    [08/05/14 09:48:24 AM] Copying K1000 agent installer.

    [08/05/14 09:48:24 AM] Running K1000 agent installer.



    mp /Volumes/Dell_KACE dev /dev/disk1s1

    installer: Package name is AMPAgent

    installer: Upgrading at base path /

    installer: The upgrade was successful.

    "disk1" unmounted.

    "disk1" ejected.



    [08/05/14 09:48:52 AM] Verifying installation.


    STEP 3: PUSH SCRIPT\PROVISIONING - FAILED


    [08/05/14 09:48:52 AM] K1000 agent detected via ssh query.

    [08/05/14 09:48:52 AM] Version is 6.0.1079.

    [08/05/14 09:48:53 AM] K1000 agent KUID: 8D4ED259085349C297CD0A6EEE0AC3CF

    [08/05/14 09:48:53 AM] K1000 agent NOT connected via AMP.

    [08/05/14 09:48:53 AM] End provisioning run. - Tderrick 9 years ago
  • I tested on another mac with the 10.0 OS, guess what SAME ERROR!

    [08/05/14 10:04:49 AM] Begin provisioning...

    [08/05/14 10:04:49 AM] Executing Unix platform provisioning.

    [08/05/14 10:04:49 AM] Probing tcp ports for accessibility.

    [08/05/14 10:04:49 AM] Port 22 [ssh] open.


    STEP 1: CONNECT TCP/SSH - SUCCESSFUL



    STEP 2: AUTHENTICATION - SUCCESSFUL


    [08/05/14 10:04:49 AM] Target is osx-x86_64.

    [08/05/14 10:04:50 AM] K1000 agent NOT detected via ssh query.

    [08/05/14 10:04:50 AM] Attempting remote agent installation.

    [08/05/14 10:04:50 AM] Copying K1000 agent installer.

    [08/05/14 10:04:52 AM] Running K1000 agent installer.



    mp /Volumes/Dell_KACE dev /dev/disk1s1

    installer: Package name is AMPAgent

    installer: Installing at base path /

    installer: The install was successful.

    "disk1" unmounted.

    "disk1" ejected.



    [08/05/14 10:05:02 AM] Verifying installation.


    STEP 3: PUSH SCRIPT\PROVISIONING - FAILED


    [08/05/14 10:05:02 AM] K1000 agent detected via ssh query.

    [08/05/14 10:05:03 AM] Version is 6.0.1079.

    [08/05/14 10:05:03 AM] K1000 agent KUID: F9B8EB6199C6416595126F914D117B06

    [08/05/14 10:05:03 AM] K1000 agent NOT connected via AMP.

    [08/05/14 10:05:03 AM] End provisioning run. - Tderrick 9 years ago
Posted by: jknox 9 years ago
Red Belt
0
Which agent version are you trying to deploy?

Comments:
  • 5.4.10622 - Tderrick 9 years ago
    • Are you seeing this on more than one system? - jknox 9 years ago
      • I have had similar problems on all my test systems, but I usually only have access to one test system at a time. - Tderrick 9 years ago
      • Now using a second test Mac (MacBook Pro OSX 10.6.8) I got a whole new message...
        [07/29/14 01:03:39 PM] Begin provisioning...

        [07/29/14 01:03:39 PM] Executing Unix platform provisioning.

        [07/29/14 01:03:39 PM] Probing tcp ports for accessibility.

        [07/29/14 01:03:39 PM] Port 22 [ssh] open.


        STEP 1: CONNECT TCP/SSH - FAILED


        [07/29/14 01:03:39 PM] Failed to detect a valid platform/architecture.



        Troubleshooting...

        Attempting "which uname"

        "which uname" did not return anything.

        Attempting "uname -a"

        "uname -a" did not return anything.

        Attempting "which bash"

        "which bash" did not return anything.

        Attempting "echo $SHELL"

        "echo $SHELL" did not return anything.



        [07/29/14 01:03:39 PM] End provisioning run. - Tderrick 9 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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