Updated to 6.0 yesterday and used two of our department groups in KACE as a test.  One group has 35 Dell PCs, the other has 15 Macs and 1 Dell PC.

I found that all of the PCs updated with no issues, not surprising.  The Macs on the other hand had an issue. Any of the Macs running 10.8.5 or below updated the agent fine.  Any of them running 10.9.2 refused to upgrade and in addition stopped checking in once added to the list of upgrades.

Basically the issue is:

-Mac "xyz" running 10.9.2 running the 5.x version of the agent is checking in fine

-Add machine "xyz" to list of devices to update agent version to 6.0.1079

-Go to inventory to see details on "xyz" and click to Force Inventory to force client to check in and update agent

-Machine "xyz" never checks in again despite stopping/starting ampagent or rebooting

The only way around this is to do a manual install of the 6.0.1079 agent which is not a viable solution as we have ~200 Macs in our environment running 10.9.x.

 

 

Anyone else running into this issue?

Answer Summary:
Cancel
2 Comments   [ + ] Show Comments

Comments

  • This is a known issue with 5.5 and older agents, that affects Mac 10.9.x only. This has been fixed with 5.5 AP1 agent and is in the 5.5 AP1 release notes.
    Unfortunately, because the problem resides in an agent component (runkbot), there is no automatic way to fix this.
    The two options are:
    1) Run the script which replaces runkbot with the one from 5.5 AP1 agent before attempting to upgrade on the affected Mac machines. (Script to be uploaded later)
    2) Manually upgrade or unprovision then reprovision the agent.
  • Are you running rep shares by any chance? I had an issue in 5.5 that sounds similar. It turned out to be a bug. I disabled the rep share for my macs and it worked immediately. I haven't tested in 6.0 yet.
Please log in to comment

Answers

0

Actually, I think that using an Online Shell Script is the way to go. Also, if you already have the Macs set for the Agent Upgrade, turn off the agent update (at least for the Macs) while the script is running, then trun it on after the script has replaced the runkbot file.

 

Here is a bash script that should work. Make the 6.0 version of the runkbot executable the dependancy.

 

#!/bin/bash
/bin/cp ./runkbot /Library/Application\ Support/Dell/KACE/bin/runkbot
/bin/sleep 15
/Library/Application\ Support/Dell/KACE/bin/runkbot 2 0

 

 

 

Answered 05/15/2014 by: MacDude
Fourth Degree Brown Belt

Please log in to comment
This content is currently hidden from public view.
Reason: Removed by member request
For more information, visit our FAQ's.

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

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

0
This is a known issue with 5.5 and older agents that affects Mac 10.9.x only. This has been fixed in 5.5 AP1 agent and is documented in the 5.5 AP1 release notes.
Unfortunately, because the problem resides with the agent component (runkbot), there is not automatic way to fix this.
The options are:
  1. Run the script which replaces runkbot on the agent with the one from 5.5 AP1 before attempting to upgrade on the affected Mac. The script will be uploaded separately.
  2. Manually upgrade the agent, or unprovision then reprovision the agent.

Script:
 
To create this script you will need to manually install the 6.0 agent on at least one OS X system so that you can grab the updated version of runkbot from that new version of the Agent. 
 
 1. Create an Online Kscript ( I called mine Agent fix for OS X)
 2. Limit Selected OS to OS X
 3. Add an attachment of the 'runkbot' binary from a working 6.0 machine. The file path is:
 /Library/Application Support/Dell/KACE/bin/runkbot
 4. Under On Success, use the following:
 Launch a Program...
 Directory: /bin
 File: cp
 X Wait for completion
 Parameters:  $(KACE_DEPENDENCY_DIR)/runkbot  $(KACE_APP_DIR)/runkbot
 
 
Run that on any systems that are running 10.9 and are not updating. 
 
Answered 05/14/2014 by: MacDude
Fourth Degree Brown Belt

Please log in to comment
Answer this question or Comment on this question for clarity