FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: Software Updates Caveats

Software Updates Caveats 27 May 2016 18:06 #2314

  • Tim Curtin
  • Tim Curtin's Avatar Topic Author
  • Offline
  • 1st level - White Belt
  • 1st level - White Belt
  • Posts: 1
  • Thank you received: 0
On the topic of Software Updates.

I currently manage 250 Mac OS X systems in a retail environment and I would like to decommission my current update servers, in favor of Filewave Boosters. I am struggling with this transition due to a few caveats in the way Filewave handles software updates.

The number one deterrent is the lack of a time-frame to download and update. I cannot afford to have downtime during business hours. I need updates to only download, run, and restart outside of store hours. The Start Download and Become Active are a great start, but they still fall short.

In order to set Start Download and Become Active times for software updates:

- The update must be associated through the Software Update Assistant
- Find and open the specific update within Associations (harder than it seems due to how similar all the update names are)
- Select all of the systems associated to the software update
- Select the Edit Associations buttons in the upper left
- Edit the Association Timing

In response to the aforementioned workflow, I would prefer to assign the Association Timing with the Software Update Assistant as I create the initial association. A streamline and seamless workflow would lend more time to handling important tasks.

Software Updates Caveats 01 Jun 2017 13:49 #2568

  • Nick Hetherington
  • Nick Hetherington's Avatar
  • Offline
  • 1st level - White Belt
  • 1st level - White Belt
  • Posts: 1
  • Thank you received: 0
Ya, I have requested the same feature. I used to manage our Mac environment with JSS, and it had so many better ways for a business to run updates, such as install time frames, repeating installs, etc. We also didn't have to mess with trying to schedule the different specific updates for each iteration of OS X, which was so nice compared to FileWaves system. I manage about 500 OS X based systems in a university environment, so we cannot have any downtime, at all. Which is why we actually can only barely use FileWave for updates to out Mac environment. When I tried to use it for updates 3 months ago, it ended up Soft Bricking 4 executive's iMac's, and required us to clone the HDD, format, then migrate their information back to get out of the constant kernel panics. Which meant I got to work the entire weekend to have them fixed before start of work Monday. What I ended up doing was writing out a very basic script that utilizes the built in SoftwareUpdate command of OS X to request and install updates from Apple. It is set to begin after hours, but since I can't manage this very well because FileWave does not give good activation windows, I added a automatic restart with a 15 minute timer, that way the user is informed with enough time to save his work and restart, without to many issues or major downtime, should the FileSet decide to activate during business hours.
  • Page:
  • 1