| **Name** | Fileset Title |
| **Size** | Fileset size, as stored on FileWave Server and Boosters or Clients when transferred. |
| **Version** | Each update to a Fileset will increment its version number after the Model Update |
| **Files** | Total number of files stored within the Fileset |
| **ID** | A unique identifier used by FileWave to track each Fileset |
| **Comment** | User customisable text for viewing in FileWave Admin software only |
| **VPP Token** | Apple Volume Purchase Program token name |
| **Default Revision** | Indicates the default revision to be deployed, where a Fileset contains multiple revisions |
| **Revision Count** | Highlights the amount of revisions within each Fileset. |
Files may be selected and exported from the Fileset to the local device.
# Desktop PKG and MSI Filesets ## What Special Filesets may be created for PKG and MSI installers. These will automatically instal the software on deployment activation. ## Why It is usual for Admins to just simply require PKGs or MSIs to instal on activation. To simplify the process, FileWave can automatically create a special Fileset to handle this process. ## How Using the New Fileset option within the FileWave Central Admin App, it is possible to choose PKG or MSI Fileset. From the pop-up view, select the installer and FileWave will create this auto installing Fileset.More easily, if a PKG or MSI installer file is dragged into the FileWave Central Fileset view, the same automated Fileset should be created, without the need to use the New Fileset view.
Dragging the installer file onto a desired Fileset Group will cause this new Fileset to be created within that group.
Consider renaming the installer before upload, such that the version number is not included. Instead, add the name and version number to the revision name. The below section on revisions should make this clear why this would be a good idea.
## Information Opening a PKG or MSI Fileset will show the contents similar to the below: [](https://kb.filewave.com/uploads/images/gallery/2025-02/6ojD9S4X0N5yip78-image.png) From creation, this special Fileset is expecting an installer of the named PKG or MSI from initial upload to the server.If manually altering a PKG or MSI Fileset, to upload a newer version of an installer, it is therefore necessary that the replaced installer file MUST have the same name as the installer being replaced.
### Revisions In some ways, revisions simplify the process of updating the Fileset with newer installers. There are two ways to create a new revision: - Drag and drop a new installer onto the existing Fileset - Open the existing Fileset, choose the option to Manage Revisions and from the button to add a new revision, choose to duplicate #### Drag & Drop When dragging a PKG installer onto a current PKG Fileset or an MSI onto a current MSI Fileset, a prompt similar to the below should be shown: [](https://kb.filewave.com/uploads/images/gallery/2025-02/UULkHQ1A5CEXDqHa-image.png) Choosing the option to 'Add revisions to existing' will automatically generate a new revision with this new installer. Assigning this new revision to devices or setting this new revision as the new default should then trigger this new installer to activate on devices.After the new revision is created, consider opening the Fileset to set the name of the new revision, such that the name includes the version number of the installer.
#### Duplication When choosing to Manage Revisions from within the Fileset, there is the option to duplicate a revision of choice. On doing so, everything from the prior Revision can be copied over to this new revision. [](https://kb.filewave.com/uploads/images/gallery/2025-02/jaEvwtaKpwub0doQ-image.png) This is useful when there are multiple additional items added into a PKG or MSI Fileset. However, there is an important consideration when using this method. As highlighted above, when manually replacing a PKG or MSI installer, **the installer name with the Fileset must match**. Hence, duplicating a revision, with the idea of replacing the current installer with a new version, whilst maintaining additional files, forces this requirement.Before creating the first Fileset for a given installer, rename the installer to exclude the version number before uploading. Instead, add the version number into the name of the revision instead.
The name of the installer to be uploaded does not need to match, but the name of the installer within the Fileset must match. If the name of the installer file does not match before upload, 'copy' the name from within the Fileset, upload the new installer into the same folder as the original installer, delete the original installer and rename the new installer using 'paste'.
If the name of the initial installer uploaded includes the version number, when manually altering the revision, since the name must match, the newly uploaded version would have to be misnamed with a version number that does not make sense.
File Level Filesets (including PKG and MSI Filesets) can be exported for transfer to another FileWave server. They can also be compressed and stored for future use or archived.
Most installers only handle upgrade, not downgrade. If there is a desire to rollback to an older revision, it is likely the currently installed version on the device will need to be deleted beforehand.
After successful installation, the .msi is removed locally from the machine. If you need to remove the application at a later date, please refer [here](https://kb.filewave.com/books/filesets-payloads/page/uninstalling-filesets) for details on the 'Use MSI uninstaller' checkbox. If you require specific switches or other custom parameters for installation and uninstallation, using an empty fileset may provide better flexibility for deployment.
## Related Content - [Fileset Revisions](https://kb.filewave.com/books/filesets-payloads/chapter/fileset-revisions) - [Uninstalling Filesets](https://kb.filewave.com/books/filesets-payloads/page/uninstalling-filesets) # Verification There are three primary verification settings. Each of these settings causes the related file(s) to behave differently once deployed. | **Self Healing** | Files set as self-healing will be replaced on devices with those within the Fileset, if different, or added if missing. The act of Verification re-confirms all included files. | On disassociation, Files included in the Fileset will be removed from the device |
| **Download if Missing** | Similar to self-healing, however, the file will only be added if the file is missing. After initial deployment, the file may be altered, without repair occurring at Verification | On disassociation, Files included in the Fileset will be removed from the device |
| **Ignore At Verify (Left Behind)** | Once delivered, the file may be altered. | On disassociation, delivered files will remain on the device. |
| **Don’t overwrite existing files upon deployment** | If enabled, only deliver the file if it does net exist. |
| **Overwrite only if the existing file is older** | A sub option to the overwrite option, only replace the current file on the device, if that existing file has an older timestamp than the matching file in the Fileset. |
Any files that already exist between one Fileset and another, will not be transferred between server and client since they already exist as required; with the exception of the overwrite option on initial deployment.
# Windows Registry Windows registry files may be included within a Filesets and edited within FileWave.  # Apple VPP Apps Unlike File Level Filesets, Apple VPP Filesets contain the details of the App from the App Store, including the link to the App, with 3 distinct tabs, Details, Kiosk and Configuration.FileWave does not store Apps from the App Store, devices will pull the Apps directly from the App Store on successful activation.
#### Details Amongst these are some key entries:| **Remove App when MDM profile is removed** | If the device has the MDM enrolment profile removed, this option will force Apps managed by MDM to be removed. |
| **Prevent Data Backup** | Disallow the App from backing up user data |
| **Take management of this app if the user has installed it already** | For Apps already installed, the MDM server will take over management of the App from the user. This is required if you want FileWave to manage deployment behavior, updates, and related settings for that App. |
| **Application update (DDM)** | For supported apps installed through DDM in FileWave 16.3.x, this controls how the App is updated on iOS, iPadOS, and macOS. Choose **Follow Store Settings**, **Always On**, **Always Off**, or **Pin specific version**. If you choose **Pin specific version**, use the version field to target the exact App Store version to install and keep. |
| **User** | Only set when a managed user logs in |
| **System** | Payload settings applied regardless of user logged in. |
Apple allows the management of any amount of directory users for a single device. However, only one local user will be managed. This user will be the first user after enrolment of the device.
Profiles are stored directly within the Fileset and delivered to devices after MDM communication has been established. # Android Apps Android Filesets are created from either the public or private Play Store. Additionally, Web Apps may be considered.  Three tabs are available for a Play Store App Fileset: Configuration, Permissions and Managed Properties. The later will only contain management options, where the developer has chosen to include options. Configuration and Permissions should be reviewed, as should any any management properties where they exist, before assignment.
# Fileset Properties Properties exist for most Filesets, but options displayed will vary depending upon Fileset type. File Level Filesets include:| **Properties** | Additional features include Reboot, the Force sub-option, priority, and an option to change verification for the entire Fileset. Priority provides extra control over the order of Fileset activation. |
| **Requirements** | Settings define the OS and hardware requirements for the Fileset. The Fileset downloads and activates only on devices that match these requirements. |
| **Dependencies** | Dependencies are covered in more detail elsewhere. In essence, the Fileset activates only after another defined Fileset installs first. |
| **Delete Files** | A defined list of files to be removed during activation |
| **Kiosk** | Details shown to users via the Kiosk Self-Service menu and system tray item. |
Profiles may only be a dependency in one direction, to prevent unexpected delay of Fileset installations.
FileWave has no control over the MDM protocol and relies on Apple’s process for delivering MDM items. For this reason, dependencies can make an MDM Fileset, such as a profile or VPP app, install after a non-MDM Fileset has activated, but other Filesets cannot depend on an MDM Fileset.
# Dependencies Dependencies offer a way to associate multiple Filesets with reliance upon other Filesets to be installed first. From the below example image, 2 Fileset Dependency Properties are displayed. - **Left image:** the Fileset which will instal first (should not be associated with devices relying upon this dependency). - **Right image:** the Fileset that will be associated and therefore instal afterwards. It can be seen that the Fileset on the left is shown as a dependency of the Fileset on the right.  Multiple Filesets may be used as dependencies or be the dependent. Dependents of a Fileset may also be a dependency of another Fileset, creating a chain of Fileset installations. # Revisions Previously, updating one version of a software, for example, to a newer version, would require: a new Fileset created, new association or deployment generated and then the prior association removed. Revisions simplifies this process. To prevent associations or deployments being altered, a Fileset becomes a container of multiple revisions.  The version associated with devices may be altered within the Fileset. This allows for efficient update of Filesets on devices, simplified process between testing and mass assignment, whilst at the same time providing an easy method to roll back if found to be necessary; depending upon Fileset Type.Behind the scenes, swapping from one revision to another is the same as actually swapping between two different Filesets. All contents will be reconsidered and any scripts ran, e.g. a post-uninstaller script will run if included in the Fileset Revision that is being unassigned.