FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: macOS Updates via Mac AppStore vs. Update Fileset

macOS Updates via Mac AppStore vs. Update Fileset 12 May 2017 07:31 #2551

  • Tan Ng
  • Tan Ng's Avatar Topic Author
  • Offline
  • 1st level - White Belt
  • 1st level - White Belt
  • Posts: 3
  • Thank you received: 0
Is there any documentation explaining the the difference and dependency/impact between macOS Updates via Mac AppStore and FileWave Update Fileset?

What if the user updated the associated client via the Mac AppStore after when not connected to FileWave server?

Where would find the log of the FileWave Update fileset activation to troubleshoot the failed install status?

Thanks.

macOS Updates via Mac AppStore vs. Update Fileset 15 May 2017 17:59 #2554

  • Bao Tran
  • Bao Tran's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 102
  • Karma: 4
  • Thank you received: 13
If you use the "Automatically deploy to requesting clients" option in the Find Software Updates Assistant shouldn't that avoid any conflicts? So if you install a patch via the Mac AppStore I would think that FileWave would no longer assign it automatically. But I don't know how this feature works under the hood so I couldn't tell you for sure.

Not sure what client you're talking about updating. Can you elaborate?

If there's an error it should show up in the Fileset Status tab of the Client Info window for that device. You might be able to get more info by viewing the Client Log via the Client Monitor.

macOS Updates via Mac AppStore vs. Update Fileset 19 May 2017 06:58 #2556

  • Tan Ng
  • Tan Ng's Avatar Topic Author
  • Offline
  • 1st level - White Belt
  • 1st level - White Belt
  • Posts: 3
  • Thank you received: 0
We are trying to update Mac client. We are trying to find a best practice procedure to deploy OS Update fileset.

Here are the steps for 1 scenario:
1. The Mac client is already associated to the OS Updates fileset (e.g. macOS Sierra 10.12.5).
2. The user of the Mac client ignores the FileWave pop-up window to install the update (i.e. FileWave client already downloaded the OS Update files and ready to active/install).
3. Instead, the user goes to the the Mac AppStore and click Updates and then install the pending OS Updates (10.12.5)
4. The Mac client is rebooted after the OS Updates is installed via Mac AppStore
5. After the reboot, there is an inconsistent behavior from FileWave client. On one Mac client, it is no longer showing the FileWave pop-up window prompting to install the OS Updates fileset. On another Mac client, it still shows the FileWave pop-up window. After we click "Install Application" on the FileWave pop-up window, we see the FileWave client is trying to install the OS Update fileset and eventually restart the Mac. After the restart, we see the status to be "Install Failed" from the Fileset Status report (FW Admin or sudo fwcontrol client status).

Does anyone know "Reboot deadline at" really automatically force a reboot at the specified date/time? What happen if the user ignore the FileWave pop-window and manually shutdown/restart the Mac from the Apple menu before the FileWave pop-up window counts down to restart? Will the OS Update fileset still install when restarting the Mac?
Last Edit: by Tan Ng.

macOS Updates via Mac AppStore vs. Update Fileset 25 May 2017 05:57 #2561

  • Bao Tran
  • Bao Tran's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 102
  • Karma: 4
  • Thank you received: 13
I tried all your steps twice and the behavior I see at step 5 is that it is no longer showing the FileWave pop-up window prompting to install the OS Updates fileset after the reboot. After the restart, I see the status as "Installation Failed" from the Fileset Status report. If I check the OS version it's still at the old version so the OS patch installation for the new OS version did indeed fail. It seems there's some weird conflict with the open FileWave OS update window that cause the Mac AppStore to fail to install the update correctly. To resolve these failed installations and get the clients to update here's what you can do. I tried this for a single client and it worked.

1. Go to the Filesets section, highlight the OS patch, and click Report in the menu bar.
2. Sort by the Status column, highlight all the Installation Failed entries and click the Reinstall on Selected Clients button.

The FileWave prompt to install the OS update should appear on the client machines agains. After this installation via FileWave completed the status changed to Installed Successfully. To avoid this issue in the future I'd recommend training your users or sending out an email letting them know that that they do not need to update the OS but that you will handle it for them.

I don't think the reboot deadline kicks in unless the OS update actually installs successfully but you probably want to test that out.

What happen if the user ignore the FileWave pop-window and manually shutdown/restart the Mac from the Apple menu before the FileWave pop-up window counts down to restart? Will the OS Update fileset still install when restarting the Mac?


The behavior I saw was identical to what happens as if you ignore the FileWave dialog and installed the OS patch from the Mac AppStore.

1. System reboots.
2. System looks like it's installing OS patch.
3. Reboots when it's done.
4. Log in and check OS version and it hasn't changed.
5. Check installation status in FileWave Admin and it says installation failed.
6. Pop up window doesn't appear again to install the patch.

I forced the failed patch to reinstall via FileWave using Reinstall on Selected Clients as described at the top of this response.
  • Page:
  • 1