Booster Overview

Introduction

A Booster in the context of FileWave is a component designed to scale the management of devices within a network. It is a server component that can be installed on macOS, Windows, and Linux systems and is used to distribute data from the FileWave server to devices. Boosters can be used with both FileWave-hosted and on-premise servers. They are optional, but often valuable for environments that need local caching, reduced WAN traffic, or better deployment performance.

Booster Planning for Customers

Hosted Customers

For Hosted customers, a Booster is optional, not required. It is often recommended when you manage macOS or Windows devices from a FileWave-hosted server because it can cache Filesets and application installers closer to clients, reduce WAN traffic to the hosted server, and improve deployment performance. For Windows devices, Boosters can also cache Microsoft OS updates and patches. Boosters do not help Android, ChromeOS, iPad, iPhone, or Apple TV device-only workflows. For Apple OS updates and upgrades on macOS, iOS, iPadOS, and tvOS, use Apple Content Caching instead.

If you choose to deploy Boosters, consider the architecture and placement before rollout. For this, refer to the Booster Deployment Planning article, which provides valuable insights and recommendations on Booster planning.

On-Premise Customers

For On-Premise customers, Boosters remain a valid and common architecture choice for caching, reducing server or WAN load, supporting distributed sites, and improving deployment performance. Refer to the Booster Deployment Planning article to plan and architect your Boosters effectively.

Why Consider Boosters?

Key Insights on Boosters

Clients are configured to use Boosters.  Where configured, the first client requesting any Non-MDM Fileset from the server, waits for the Booster to download the Fileset first; the client in-turn receives the Fileset from the Booster.  Any subsequent clients, requesting an already Boosted Fileset, will benefit immediately from the Fileset now stored on the Booster.

Since clients are the driving force, there is no need to store the entire repository of Fileset, but just those requested by downstream clients.  Boosters may also be configured to remove boosted Filesets which are deleted from the server, essentially self managing their storage space.

Boosters may be cascaded with each other, handling even the most complex network environments.

Whether your clients are on a centralized network or scattered across multiple networks (like remote workers or students), Boosters can be immensely beneficial.

What's Next?

If you're unsure about how to set up Boosters, or if you believe you've already implemented them but would like a configuration review, we're here to help! A quick call can clarify and assist. Please connect with Customer Technical Support about any issues that arise, but use Professional Services & Training for guidance on best practices as a paid service or leverage the YouTube video listed below.


Revision #11
Created 2023-07-03 19:27:23 UTC by Josh Levitsky
Updated 2026-06-17 22:24:28 UTC by Josh Levitsky