View - Deployments

• Create Deployment
• Deployment Targets
• Deployment Payloads
• Deployment Options
• Deployment Summary
• Deployment Drafts
• Deployments Targeting LDAP Groups

Create Deployment

What

Create a deployment when you need FileWave Anywhere to connect one or more payloads with devices or groups. Deployments can also include exclusions for devices or groups that should not receive the payload.

When/Why

For a simple deployment, target a manual group or individual devices, such as every device that owns an Adobe Photoshop license. For a scoped rollout, target a broader group such as Production, then add an exclusion for the Managers Smart Group. Deployments can also target LDAP OUs.

How

To create a new deployment, select the plus ( ) in the top right.

Give the deployment a clear name in the top left. Good names make deployments easier to filter and audit later.

The related deployment articles cover each tab in this view.

Deployment Targets

What

The Targets of a deployment are the endpoints that we'll define for deploying to.  Targets allows us to choose individual devices, groups, smart groups and LDAP sources for our deployment.  Targets also allows us to avoid deploying to certain devices or groups as well.

When/Why

We'll want to define here the targets and exclusions:

Targets - What you want to receive  Groups - Static, Smart Groups, and LDAP OUs to include   Devices - Specific devices to include
Exclusions - What you don't want to receive Groups - Static, Smart Groups and LDAP OUs to exclude Devices - Specific devices to exclude

If left blank, the deployment can be saved, but without targets it won't send payloads anywhere.  This may be nice for archival purposes.

How

1. From the Targets tab.
2. Select devices you want to get a payload(s). Either groups or individual devices
3. (optional) Select exceptions, groups or devices you do not want to receive any payload(s)
4. Save your work to finish later or next to finish creating your deployment

Deployment Payloads

What

In the Payloads tab, we'll choose all of the payload(s) we want to include in this deployment.  That is, items, such as software you want to deploy.  This can be one item, many items, or even nothing.

When/Why

Of course the point of a deployment is to deploy something, so we'll pick payloads we want in this view.  Note that the list of payloads can always be amended.  Additions will be installations, and removals of payloads will be uninstalls (based on verification settings).

How

1. Press the plus () in the top right or "Add Payloads" button in the center
2. Select one or many payloads
3. You may delete them with the x ()
4. Select Save to continue later or next to finish the deployment

Deployment Options

What

The Options tab controls deployment behavior, including install type, timing, and VPP license assignment when the payload supports those settings. The available options depend on the payload type.

When/Why

For simple payloads, such as an iOS VPP app, you might leave the defaults alone. For a Windows MSI deployment that should install after 5 PM on Friday, you can use the timing options to control when FileWave offers or installs it.

How

1. Select the install type:
   1. Direct: installs automatically.
   2. Kiosk: appears in the Kiosk for the user to install.
2. Optionally set timing. If no timing is selected, FileWave downloads and installs as soon as the deployment can run.
3. For VPP apps, optionally select license distribution:
   1. Device
   2. User

Deployment Summary

What

The Deployments Summary tab shows you the effective action that your deployment will perform.

When/Why

It is very important to review this tab to make sure that at minimum the number of devices being impacted makes sense.  This is your opportunity to sanity-check your settings before you update the model and commit your changes.

How

Note that no actions can be taken directly on the summary tab, but it gives you to overview to evaluate your deployment:

The tab shows the number of endpoints impacted, and the overall size of the deployment.  Note that an explicit exclusion wins over an inclusion. (e.g. a device is in a group that has a payload assigned, but that device is also explicitly exluded means that that endpoint will NOT have the payload(s) installed.)

Deployment Drafts

What

When you create a deployment in FileWave Anywhere, an unfinished deployment may appear as a Deployment draft on the Deployments page.

When/Why

Deployment drafts protect work that you have started but not finished. If you close the browser, move to another task, or leave the deployment before saving it, FileWave Anywhere can keep the draft so you can return to it later.

Drafts are stored for the user and browser that created them. For example, a draft created in Chrome will not appear if the same administrator signs in from Firefox.

How

Deployment drafts appear on the Deployments page. To continue a draft, click its name or use the ... menu and choose Edit. To discard it, use the same menu and choose Delete.

If you click Cancel while editing a draft, FileWave Anywhere asks whether to keep the draft for later or delete it now.

Deployments Targeting LDAP Groups

What

FileWave Anywhere can target LDAP organizational units (OUs) directly when defining a deployment. That means you can deploy to directory-based groups without first building a separate Smart Group just to mirror the OU.

When/Why

Use this when the LDAP OU is the source of truth for the devices you want to include or exclude. Directory-based targeting works well when the directory data is reliable; if device membership in LDAP is stale, the deployment target will be stale too.

How

Target or exclude an LDAP OU in a deployment the same way you would target another deployment source. The example below shows the workflow: