Combining payloads into a singular deployment based on metadata

What

Every Deployment stores metadata about how content is assigned: the targets and exclusions, delivery method, timing, license assignment, and payload revision choices.

When/Why

Use one Deployment for multiple payloads or destinations only when the content should share the same metadata. If one payload or target needs a different install method, schedule, license assignment, target list, 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 payloads use the same delivery method, such as Kiosk or Standard/direct installation.
• The timing options match.
• The license options match, such as device-assigned VPP licensing.
• The same targets and exclusions should receive the content.
• There are no payload revision conflicts.

For example, if Firefox should be available through Kiosk for both Accounting and HR, those groups can be included in the same Deployment as long as the rest of the settings also match.

If Firefox should be available through Kiosk for Accounting but installed directly for HR, do not combine those into one Deployment. The delivery metadata is different, so they should be separate Deployments.

Digging Deeper

Association-to-Deployment conversion follows the same rule: combine Associations only when their metadata matches. The example below shows selected Associations that are good candidates to move into one Deployment.

These Associations are good candidates because:

• They are all direct installation items (Type: Standard).
• They have common timing.
• They use the same destination group or platform scope.
• The VPP apps use the same license type (Assign to Device).
• There are no payload revision conflicts.

Pro tip: Filtering by Type, such as Kiosk or Standard, is a quick way to isolate similar Associations before moving them into Deployments.

For more on planning Deployment structure, see Should I create one, or multiple Deployments? and The FileWave Associations-to-Deployment Conversion Tool.