Managing Macintosh with KBOX 1100
Is anyone here managing Macs using the KBOX? About 25% of my machines are Mac. We are inventorying and patching with great success.
We also push fonts with file synchronization.
I am, however, quite unsuccessful in deploying software applications. I would love to converse with anyone that has had success with this.
I am not terribly familiar with Mac scripting and would much rather have the robustness and simplicity of a Managed Installation, however it doesn't seem to work on Macs.
I am currently trying to deploy a Symantec.mpkg contained in a zip file, however using the "default" command line setting, the zip is delivered as a payload, but never executes.
Looking forward to a good discussion! Thanks!
We also push fonts with file synchronization.
I am, however, quite unsuccessful in deploying software applications. I would love to converse with anyone that has had success with this.
I am not terribly familiar with Mac scripting and would much rather have the robustness and simplicity of a Managed Installation, however it doesn't seem to work on Macs.
I am currently trying to deploy a Symantec.mpkg contained in a zip file, however using the "default" command line setting, the zip is delivered as a payload, but never executes.
Looking forward to a good discussion! Thanks!
1 Comment
[ + ] Show comment
Answers (12)
Please log in to answer
Posted by:
MacDude
10 years ago
I did a presentatoin on Mac Application Packaging at Dell World Software User Forum (what used to be the Kace Konference) where I had exercises for doing non-standard deployments. I'll see if I can get those released.
BTW- The exercises were: Google Chrome (with modified defaults), Adobe Flash (with some tricks), and MS Office customization.
Comments:
-
MacDude, my Mac currently has updates for MS Remote Desktop v. 8.0.15 and Mac Command Line Tools (OS X 10.9)6.2. According to the below patching matrix these aren't supported, and my K1000 does not have them. Do you create a script for installing these? Is there a canned script which will make a Mac simply run all updates it has in its built-in Software Updates queue? Also, any idea if there is a more recent version of this supported software matrix?
https://support.software.dell.com/k1000-systems-management-appliance/kb/112030 - bens401 9 years ago-
Hi Bens, It is often the case that you will need to manage full upgrades with either Managed Installs or Scripting jobs. Patching will typically only update an app within the major version (i.e., 8.01 to 8.54, but not 8.01 to 9.0).
With regard to running the built in updater, it can be done via command line, so it could be done with the K1000. see: https://support.apple.com/en-us/HT200113 - MacDude 9 years ago-
MacDude,
I created a Kace offline script for now but it seems to work great so far. I need to test it on a very outdated Mac. This will be good for programs that aren't supported by Kace Mac patching, although I don't understand why Kace can't patch Command Line Tools. Here's output logs from the script on my Mac which had only one program update available. My plan is to run this script the day after my scheduled Mac patches. I have a feeling this could lead to some problems in future. Any thoughts? Thanks for your help:
-Output Log
Launched Process: softwareupdate
Software Update Tool
Copyright 2002-2012 Apple Inc.
Finding available software
Downloaded Command Line Tools (OS X 10.9)
Installing Command Line Tools (OS X 10.9)
Done with Command Line Tools (OS X 10.9)
Done.
Launched Process: softwareupdate
-Activity Log
Launching path /usr/sbin program: 'softwareupdate' '--list > /tmp/updates.txt' wait='true'
Uploading file: /tmpupdates.txt
Launching path /usr/sbin program: 'softwareupdate' '--install --all' wait='true' - bens401 9 years ago
Posted by:
ScottinOkla
13 years ago
Posted by:
ms01ak
13 years ago
Posted by:
dchristian
13 years ago
The KBox will only take .app and .pkg.
Here's an article that talks about renaming .mpkg
[link]http://www.kace.com/support/kb/index.php?action=artikel&cat=4&id=825&artlang=en[/link]
Mac installs are usually easier, since no command line is required to install the applications.
For the most part they can be left as use default with no run parameters.
Here's an article that talks about renaming .mpkg
[link]http://www.kace.com/support/kb/index.php?action=artikel&cat=4&id=825&artlang=en[/link]
Mac installs are usually easier, since no command line is required to install the applications.
For the most part they can be left as use default with no run parameters.
Posted by:
bbevard
13 years ago
We have about 10 Macs in our enviornment right now and for almost every managed install I have come across it was as simple as dropping the .app or .pkg file (usually contained within a disk image file) onto the Kbox and using the default installation parameters. I have yet to run into an issue where renaming the .mpkg file to .pkg didn't fix it. Did that resolve your issue?
Posted by:
mlathrop
13 years ago
Posted by:
mlathrop
13 years ago
Posted by:
ScottinOkla
13 years ago
I was somewhat successful...
Well lets consider it progress...
If I copy the renamed package to the root of the OSX drive and type the following command in terminal, I get...
command:
sudo installer -pkg package_name.pkg -target /
returned:
installer: Warning - Any open applications being upgraded will close. Please save your work before continuing.
installer: Package name is ...
installer: Installing at base path / (but everything showed up in the Applications folder)
installer: The install was successful.
So I can trigger the package manually, but I cannot get Kace to deploy it. FWIW, I got the installation string from the Kace GUI.
Well lets consider it progress...
If I copy the renamed package to the root of the OSX drive and type the following command in terminal, I get...
command:
sudo installer -pkg package_name.pkg -target /
returned:
installer: Warning - Any open applications being upgraded will close. Please save your work before continuing.
installer: Package name is ...
installer: Installing at base path / (but everything showed up in the Applications folder)
installer: The install was successful.
So I can trigger the package manually, but I cannot get Kace to deploy it. FWIW, I got the installation string from the Kace GUI.
Posted by:
MacDude
13 years ago
Posted by:
mlathrop
13 years ago
Posted by:
NatureST
13 years ago
Posted by:
cblake
13 years ago
FYI Mac fans- in August we'll be having a KKE focused on Mac software distribution (Tuesday 8/2) and open Q&A (8/4) specifically on macs. You're welcome to join any K1000 Thursday session and ask, but we promise to have Mac resources for "Mac week".
You'll find the KKE schedule here: https://kace.webex.com/mw0306ld/mywebex/default.do?siteurl=kace&service=7 in the Training Center. Look forward to seeing you there!
Be sure to reach out to [email=kketeam@kace.com]kketeam@kace.com[/email] if there are other topics we should get on our schedule.
You'll find the KKE schedule here: https://kace.webex.com/mw0306ld/mywebex/default.do?siteurl=kace&service=7 in the Training Center. Look forward to seeing you there!
Be sure to reach out to [email=kketeam@kace.com]kketeam@kace.com[/email] if there are other topics we should get on our schedule.
Comments:
-
The recordings from these KKE events are also available. http://www.kace.com/support/resources/kb/article/KACE-Kontinuing-Education-K1000-and-K2000-Recordings - MacDude 11 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.
I am looking at KACE to manage my MAC computers just like the original question. I see a lot of talk about pushing applications to the MAC and file types, etc. But how are people's experience with pushing OS updates? I am in a KACE trial period and I am seeing some updates in the App Store that aren't being seen by KACE. - bawesome 9 years ago