/build/static/layout/Breadcrumb_cap_w.png

Mac OSX provisioning failed

I am trying to push out the latest client package to a macbook pro running osx 10.6.4 and I keep getting the following. Also in the log it states Error category: No Error. Any suggestions?

Provisioning Log

[09/15/10 03:11:44 PM] Begin provisioning...
[09/15/10 03:11:44 PM] Executing Unix platform provisioning.
[09/15/10 03:11:44 PM] Probing tcp ports for accessibility.
[09/15/10 03:11:44 PM] Port 22 [ssh] open.

STEP 1: CONNECT TCP/SSH - SUCCESSFUL


STEP 2: AUTHENTICATION - SUCCESSFUL

[09/15/10 03:11:44 PM] Target is Darwin.
[09/15/10 03:11:46 PM] KBOX Agent detected via ssh query.
[09/15/10 03:11:46 PM] Version is 5.0.24256.

STEP 3: PUSH SCRIPT\PROVISIONING - FAILED

[09/15/10 03:11:46 PM] End provisioning run.

0 Comments   [ + ] Show comments

Answers (5)

Posted by: airwolf 14 years ago
Red Belt
0
Perhaps on a Mac you must first remove the old agent before installing the new one? That's what I would infer from that log.
Posted by: warriorforGod 14 years ago
Senior Yellow Belt
0
Removing the old agent and then installing the new one worked. So is there any way to automate the removal and install in one fell swoop?
Posted by: airwolf 14 years ago
Red Belt
0
Not that I know of. The agent provisioning can be set to remove or install, but not both. A "reinstall" feature would be nice to remove and reinstall the agent, but nothing like this exists presently. You may want to submit a feature request for it.
Posted by: mikergray 14 years ago
Orange Senior Belt
0
Any particular reason you are using the provisioning mechanism to upgrade the agent? The K1000 has a settings tab, KBOX agent, then Agent updates from KACE. This allows you to push agent upgrades to machines that already have an existing agent installed.
Posted by: airwolf 14 years ago
Red Belt
0
I assumed the OP was trying to remove and reinstall a problematic agent. You are correct, mikergray, the best option for upgrading is the built-in agent upgrade mechanism.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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