Advanced Search
Search Results
6 total results found
Explanation of Clones with Deployments
What In FileWave, a clone is a reference to an existing device or device group. This article explains how clones behave when you move from Associations to Deployments. When/Why An admin might choose a clone on purpose, or choose one because it is convenient du...
How to decide what is included in a single deployment?
What Deployments let you group multiple payloads and manage their deployment rules together. The practical question is which Filesets and payloads belong in the same deployment. When/Why This applies when you create new deployments and when you convert existin...
Fileset Groups
Fileset Groups organize related Filesets and let you assign the group to a client or Client Group in one workflow. Create one with New Fileset Group, then drag existing Filesets into it. You can nest Fileset Groups to match your deployment structure. A Fileset...
What makes Deployments better than Associations?
What Deployments and Associations both assign Filesets or payloads to devices. Deployments are usually easier to maintain because one Deployment keeps its targets, exclusions, Filesets, and shared delivery options together. Deployments are not automatically be...
Combining payloads into a singular deployment based on metadata
What Every Deployment stores metadata about how content is assigned: targets and exclusions, installation type, timing, applicable license distribution, and Fileset revision choices. When/Why Use one Deployment for multiple Filesets or destinations only when t...
Managing Deployments with the FileWave API (16.4+)
What FileWave 16.4 adds supported public API endpoints for creating, listing, reading, updating, and deleting Deployments. These endpoints allow integrations and administrative automation to manage the same Deployment objects used by FileWave Central and FileW...