Plan One or Multiple Deployments
What
A Deployment groups one or more payload assignments under shared delivery rules. Put assignments together when their timing, installation method, Kiosk behavior, and licensing rules should be managed as one unit.
Decide before you group assignments
Split assignments into separate Deployments when any of these settings need to differ:
| Setting | Use separate Deployments when |
|---|---|
| Assignment type | Some content installs automatically, appears in Kiosk, or exists only for license assignment |
| Activation and deactivation | Payloads need different start or end dates |
| Installation timing | Payloads need different installation windows |
| Kiosk rules | Items need different self-service visibility or presentation |
| Deployment on request | Only some payloads or target groups should use self-pickup behavior |
| Payload requirements | Platform, Booster, or runtime requirements do not match |
Fewer Deployments are easier to maintain only when the assignments genuinely share the same rules.
Example
Suppose you deploy TeamViewer Host and TeamViewer Full Client to both Windows and macOS. TeamViewer Host installs automatically at night, while Full Client is offered through Kiosk at noon.
Create one Deployment for the Windows and macOS Host Filesets, then another for the two Full Client Filesets. The shared behavior stays together, and you maintain two Deployments instead of one per payload.