Troubleshooting Deployment Issues with the FileWave Upgrade Fileset

If you’re experiencing issues deploying the Upgrade Fileset to devices, the resolution steps depend on the target operating system.

macOS Deployment

Issue: Devices show that the latest FileWave Client is not installed despite deploying the Fileset.
Solutions:
1. Reinstall on Selected Devices:
2. Alternatively, you can Redeploy the Fileset:
Cause:
This issue occurs due to the Privacy Preferences Profile (v3) required for the FileWave Client. The profile must install first, but it cannot complete until the FileWave Client is deployed. Redeploying ensures proper installation order.

Note: This should be a one-time occurrence unless a new profile is required with a major macOS update post-Sequoia.

Windows Deployment

Issue: Errors occur when deploying the Fileset due to improper extraction during setup.
Solution:
1. Remove and Recreate the Fileset:
2. Redownload and Extract the Fileset:
Verification:
After importing the Fileset, ensure its contents are correctly displayed in FileWave.
Examples:
Broken Example:

Windows fileset: The extracted folder contains only a single ~Upgrade_Fileset_for_Windows.fileset folder containing unusable files.

image.png


Working Example:

Windows fileset: The extracted folder includes only the temp folder, containing scripts/MSI required to update the Client, which is imported into FileWave as the Fileset.

image.png


By following these steps and verifying with the examples, you can ensure successful deployment of the FileWave Upgrade Fileset. If further assistance is needed, please contact FileWave Support.

Revision #4
Created 22 November 2024 15:03:29 by Josh Levitsky
Updated 22 November 2024 16:24:44 by Jared Jones