|
|
Almost there
I have been onto this process for several months now. We have gone through many iterations to get to where I am now. I wrote mine to accomodate both Jaguar and Panther. We use ssh to harvest the approved updates from the server and only allow one update at a time. I am ultra conservative on this situation. We run permission repair before and after the update and never put OS revisions on the approve list (too risky). The connectivity checking is a good idea and I even check the subnet so it does not run unless they are at work. In addition I won't allow the updates to run unless the user is logged out. I also prevent login while the update is running and force the reboot after. On the server side we are using SQLite with a combination of perl, shell and Cocoa to manage the approval process. I hope to have a "kit" to release at some point after we go live. I have purposely avoided anything but software update for security reasons and kept things a simple as possible. The ability to have an alternate source for updates is unsupported by Apple so far though it has been made clear to them it's on the wish list.
Almost there
I've been looking for a way to stop users from logging in during the update. How do you achieve this? |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.05 seconds |
|