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 the content should share the same metadata. If one Fileset or target needs a different installation type, schedule, license-distribution model, target list, exclusion, or revision behavior, split it into a separate Deployment.
How
A single Deployment is a good fit when all of the following are true:
- The Filesets use the same Installation Type, such as Direct Installation or Kiosk Self-Service.
- The timing options match.
- Applicable VPP/Apps and Books applications use the same Device or User license-distribution model.
- The same targets and exclusions should receive the content.
- There are no Fileset revision conflicts.
For example, if Firefox should be available through Kiosk Self-Service for both Accounting and HR, those groups can be included in the same Deployment when the rest of the settings also match.
If Firefox should be available through Kiosk Self-Service for Accounting but installed directly for HR, do not combine those assignments. The delivery metadata differs, so use separate Deployments.
Association conversion
Association-to-Deployment conversion follows the same rule: combine Associations only when their metadata matches and the resulting Deployment should apply every included Fileset to every included target.
In the Associations view, filter the list to find candidates, select the matching Associations, and choose Move to Deployment. Review the conversion preview before publishing. The preview shows changes to targets, Filesets, options, timing, and revisions; no conversion is committed until you choose Publish.
Conversion replaces the selected Associations. Do not combine Associations merely to reduce their count. If the preview adds content to a target, removes an assignment, changes timing, or resolves a revision differently than intended, cancel and split the conversion.
Quick metadata check
| Compare | Question before combining |
|---|---|
| Targets and exclusions | Should every included target receive every included Fileset, with the same exclusions? |
| Installation Type | Should all content use Direct Installation or all use Kiosk Self-Service? |
| Timing | Should download, activation, inactivation, and deletion timing apply together? |
| License Distribution | Should applicable Apps and Books licenses use the same Device or User model? |
| Fileset revisions | Can the resulting Deployment use one intended revision of each Fileset? |
No comments to display
No comments to display