Associations to Deployments Strategy Guide
Deployments are the replacement for Associations as you move forward with FileWave in future. Deployments allow you to set rules for content delivery just as associations do, but deployments also allow you to group “associations” into one place to edit and organize them commonly.
When using the webadmin you will notice that you can not create associations any longer, and will use deployments in their place. But, don’t worry, deployments are easy to understand and use!
How Are Deployments Different than Associations?
What Both Deployments and legacy Fileset Associations assign content to devices. An Association l...
What makes Deployments better than Associations?
What Deployments and Associations both assign Filesets or payloads to devices. Deployments are us...
How to decide what is included in a single deployment?
What Deployments let you group multiple payloads and manage their deployment rules together. The ...
Combining payloads into a singular deployment based on metadata
What Every Deployment stores metadata about how content is assigned: targets and exclusions, inst...
Plan One or Multiple Deployments
What A Deployment applies every included Fileset to every included target. Use one Deployment onl...
Convert Associations to Deployments
What the conversion tool does The Associations conversion tool in FileWave Anywhere turns selecte...
Resolving Conflicts in Associations Conversion
What When you convert legacy Associations to Deployments in FileWave Anywhere, the selected assig...
Explanation of Clones with Deployments
What In FileWave, a clone is a reference to an existing device or device group. This article expl...
Deployments in FileWave Central
What A FileWave Deployment keeps its target rules, Filesets, exclusions, and deployment options t...