Filesets

Move a Fileset to Another Group
What
The Move To... command moves a Fileset into another Fileset group without dragging it through the Filesets list.
When to use it
Use Move To... when a long Filesets list makes drag and drop slow or when you want to choose the destination group explicitly.
Move a Fileset
In FileWave Central, open Filesets and select the Fileset you want to move.
Right-click the Fileset and choose Move To....
Select the destination Fileset group and confirm the move.
Verify that the Fileset now appears in the intended group.
The following video shows the workflow:

OS Software Updates - Automation Rules
What
OS update management often means tracking frequent Apple and Microsoft updates, creating Filesets, and assigning them to the right groups. FileWave 16.2.0 introduced Automation Rules to generate update Filesets from updates reported by managed devices. FileWave 16.4 adds platform and category suggestions, richer policy previews, and a Windows preview option that can focus on updates currently requested by devices.
When/Why
Apple and Windows devices report relevant OS updates back to FileWave Server. Client Info for an individual device lists the updates that device has reported:
The Software Updates view in FileWave Central shows updates reported across Apple and Microsoft devices, with additional filter options. As devices report into FileWave, this view continues to update.
The 'Is New' value drives Automation Rules.
Freshly reported entries automatically have 'Is New' set to 'Yes'.
Automation Rules target updates marked as new and generate Filesets for the updates you include. Exclusion rules keep unwanted updates out of the automation flow, such as Windows driver packs you do not want to deploy automatically.
Automation Rules can also apply to updates that do not exist yet. When devices report matching updates later, the rules can pick them up.
When Automation Rules run, FileWave creates one Fileset per included update and ignores excluded updates. The 'Is New' flag changes to 'No' when a Fileset is generated, so excluded updates remain marked as new.
You can manually change the 'Is New' flag for one or more updates from the right-click contextual menu:
Resetting the 'Is New' flag to 'Yes' makes the update eligible the next time Automation Rules run. Setting it to 'No' keeps that update out of rule processing, regardless of matching rules.
Once rules are configured, run them with the Run Automation button. At the time of writing, this is a manual action.
The 'Is New' flag changes from 'Yes' to 'No' only when a rule causes a Fileset to be generated.
How
Only FileWave Administrators with necessary permissions may perform some or all of these actions, as set in:
Assistants -> Manage Administrators:
Manage Updates
Configure Automation Rules 
Select Automation Rules in the Software Updates toolbar to view existing rules or create new ones:
The example above has three rules: one exclusion rule, two inclusion rules, and a designated Default Group. Any updates marked as new that do not match the rules generate Filesets in the Default Group. This can help you identify new updates that were not handled by a specific rule.
If you do not set one, there is no Default Group.
Use the + and - buttons to add or remove rules. Select a rule to edit its target group or assignment type. If a Default Group is set, you can clear it.
If there is no Default Group, updates that do not match inclusion rules behave like exclusions: the 'Is New' flag stays set to 'Yes' and no Fileset is created.
Rules run from top to bottom. Exclusion rules prevent matching updates from being considered by later rules. The first matching inclusion rule generates a Fileset and sets the 'Is New' flag to 'No', so later rules no longer process that update. Only one Fileset is generated for each included update during a Run Automation pass.
Drag rules up or down to change the order.
Place exclusion rules at the top of the list to prevent Filesets from being created for updates that meet the exclusion criteria.
The rules view works like Reports (formerly Inventory Queries). Give each rule a clear name, then add criteria components to define which updates it should match:
The Fields tab lists updates caught by the rule definition:
Validate Automation Rules in FileWave 16.4
FileWave 16.4 improves rule creation and previewing so administrators can test policy intent before generating Filesets.
Platform and category suggestions: When defining rule criteria, use the suggested values based on Software Update data known to the Server. Suggestions reduce spelling and category mismatches.
Policy-to-update preview: Preview a Software Update Policy to see which reported updates match its criteria.
Update-to-policy preview: From an update, review which existing policy Filesets already cover it before creating another Fileset or rule.
Windows requested-update scope: Restrict the Windows auto-install preview to updates currently requested by managed devices when you want to test criteria against the environment’s current deployment requirements.
A preview does not create Filesets or run Automation Rules. Review exclusions, rule order, target Fileset Groups, and the Default Group before selecting Run Automation.
Define or edit the rule criteria and use the platform/category suggestions where applicable.
Open the preview and confirm that the expected updates match.
For Windows, limit the preview to currently requested updates when validating against active device demand.
Check whether existing policy Filesets already cover the updates.
Correct the rule order or criteria before running Automation.
Example
Consider the following rules:
These rules run in the following order:
Rule
Description
New
1: Exclude Drivers
The criteria of this rule are set to ignore all Windows drivers.
Updates remain as 'New'.
2: Defender Updates
This rule targets Windows Defender updates and places them in a similarly named Fileset Group for testing and assignment.
Updates altered to 'Not New'
3: Rule for macOS Update
This rule adds all macOS updates to a Fileset Group named 'macOS'.
4: Default Group
 
Any updates that are still marked as new and do not match the rules above will have Filesets created in this group, 'Unfiled Updates'.
This highlights updates that were new but did not match any rule criteria.
Exclusion Example
As described above, excluded updates remain marked as new. Consider the following three rules:
The macOSUpdate 26 rule includes all macOS 26 updates. The Windows Software Updates Security rule includes updates with the category 'Security Updates'.
The exclusion rule affects both of those later rules:
Only new updates older than 10 days are processed. Newer updates are ignored and remain marked as new. As time passes, those updates come into scope for the later rules and Filesets are generated.
This gives you a testing grace period, so brand-new updates are not processed even if you run Automation Rules.
Updates can be manually generated into a test Fileset Group.
Manual Fileset creation from the Software Update view also sets the 'Is New' flag as 'No'.  Updates left untouched will remain as new and come into scope after the defined period of time.
Devices associated with the test group should receive the updates. After testing is approved, you can consider those updates for broader deployment.
For each approved update, manually reset the 'Is New' flag to 'Yes'. When the update comes into scope by date, Automation Rules can generate Filesets in the groups targeted by each rule. If an update is not approved, leave it set to 'No' so it is not included when the date scope is reached.
This method lets you pre-assign both test and production update groups, reducing follow-up manual work.
 
Related Content
OS Software Updates – Obsolete Filesets Cleanup
Automated Windows OS Updates Policy
Best Practice Guide: Software Update Deployment (16.0+)

OS Software Updates - Obsolete Filesets Cleanup
What
In FileWave you can patch your Apple and Windows devices very easily but over time you will accumulate many Filesets related to OS patching.  This feature that was added to FileWave 16.2.0 will allow you to perform a quick and easy cleanup.
When/Why
While the updates don't occupy much space at all on your FileWave Server, you may not want to have hundreds or thousands of OS update Filesets in your Filesets view. In the past you would have to manually figure out what patches were old enough to want to purge. Now you can simply purge updates that have not been requested in a set amount of time. 
How
First it is important that your account has permissions to perform these actions. In Assistants -> Manage Administrators as shown in the below image notice if you have Manage Updates enabled. If you'll be using Automations then ensure you have that right as well. 
The next thing is to determine what you consider to be old enough to purge. In Preferences within FileWave Central you can pick 30, 60, 180, or 365 days. For most people 60 or 180 days is the best value. It gives an update enough time that it hasn't been requested. You'll want to go in to Preferences and pick a value.
In the Software Updates section of Central, select Obsolete Filesets Cleanup in the toolbar. Review the candidates in the dialog. Use Select All only when every displayed candidate has been reviewed; otherwise select individual Filesets before choosing Delete Selected.
Note that this will only purge OS updates, but will purge both Apple as well as Windows OS patches. If a device later needs an update that was purged it will appear as New in the Software Updates section and you can make a Fileset for it again. For this reason it might be too aggressive to pick 30 days since you might find that updates are often purged and then need to be created again.
Review obsolete Filesets in FileWave 16.4
FileWave 16.4 adds better filtering and direct Fileset navigation from Software Update views. Use these tools to verify cleanup candidates before deleting them:
Filter the Software Updates view to narrow the platform, request state, Fileset status, or other relevant update criteria.
Locate the related Fileset or Fileset Group directly from the update view.
Check whether a Software Update Policy Fileset already covers the update and whether devices still request it.
Open Obsolete Filesets Cleanup and compare the candidates with the update view.
Select and delete only the Filesets that are genuinely outside your retention and deployment requirements.
Do not treat “obsolete” as “never needed again.” If a managed device later requests a deleted update, it can return as a new Software Update and require a new Fileset.
Cleanup remains a deliberate administrator action. Review the filtered candidates before using Select All or Delete Selected.
Related Content
OS Software Updates - Automation Rules
OS Software Updates