Configuration Options
The deployment options are listed below. Some options may not be available on your system, depending on how your BigFix administrator has configured it.
- Set Start and End Time
- Schedule a deployment to start at a specific time, for example, to reduce network load and device-holder inconvenience. When scheduling across time zones you can schedule actions to start in the past, relative to your own time zone.
- Open-ended deployment
- An open-ended deployment has no end date. It runs continuously and checks whether endpoints comply. For more information, see the Glossary.
- Client time or UTC time
- Further refine when a deployment runs. Client Time is the local time on a BigFix client's device. Coordinated Universal Time is the primary standard for regulating clocks and time worldwide.
- Stagger deployment times to reduce network load
- Enter an interval in hours and minutes.
- Send this as an offer
- Allow device owners to accept or decline an action, and to control when it runs. For example,
whether or not to install an application, or to run an installation at night rather than during the
day. Note: Do not send an offer as an open-ended deployment. Open-ended offers can cause problems for device owners, such as an optional piece of software they cannot permanently remove.Offer options:
- ONLY to the Software Distribution Client dashboard - Display software offers on the Client UI’s Software Distribution Client Dashboard when it is enabled on the device, and the Self-Service Application is not enabled. When the Self-Service Application is enabled, all offers display there.
- Notify users of offer availability - Include a notification on the endpoint that a new offer is available.
- Offer Description - Defaults to the Fixlet description, which can be amended or changed. If the offer contains multiple actions the name of each component is included.
- Download required files now
- Pre-cache deployment-related files, transferring them from a vendor's server to a BigFix server before deployment. Save time when working with large files or a tight maintenance window by completing this part of the job first.
- Send a Notification
- Trigger an email alert when a deployment fails or completes. Enter one or more recipients in the
To: field, separating multiple addresses with a comma.
- Send on Failure - enter a threshold value (1 - 250,000) to receive an email if the deployment fails on the specified number of devices.
- Send on Completion - check the box to receive an email when the deployment completes on all targets. Note: this notification option is not available when targeting computer groups.
- Force restart
- Force a restart on an endpoint following a deployment, and offer the device holder a chance to
restart the device themselves at convenient time. Set the restart to occur:
- Immediately (following completion of the deployment)
- 1 day later
- 7 days later
- 15 days later
Send a default message or enter your own. For example,
Your system administrator requests that you restart your computer, please save your work and restart. Your device will restart automatically in 7 days.
- Run all member actions of action group regardless of errors
- Multiple Action Groups only. Actions in a multiple action group run sequentially and stop on the first action that fails. Check this box to instruct the MAG to ignore a failure and proceed to the next action. Use this option when the actions in a MAG do not depend on the actions that precede them.