Redeploy existing configurations to a device

Force-deploying existing configurations to a managed device ensures that its policy rules are fully regenerated and applied. This procedure is recommended during maintenance windows or when disruption to network traffic is minimal. Force-deploy takes longer than regular deployment because it generates all policy rules for the device.

Caution

When you deploy, resource demands may result in a small number of packets dropping without inspection. Additionally, deploying some configurations restarts the Snort process, which interrupts traffic inspection. Whether traffic drops during this interruption or passes without further inspection depends on how the target device handles traffic. Refer to Snort restart traffic behavior and Configurations that restart the snort process when deployed or activated.

Before you begin

Review the guidelines described in Best practices for deploying configuration changes.
Plan to perform the redeployment during a maintenance window or low-impact period.

Procedure

Step 1	Choose Devices > Device Management.
Step 2	Click Edit () next to the device where you want to force deployment.
Step 3	Click Device.
Step 4	Click Edit () next to the General section heading.
Step 5	Click Force Deploy ().
Step 6	Click Deploy. The system identifies any errors or warnings with the configurations you are deploying. You can click Proceed to continue without resolving warning conditions. However, you cannot proceed if the system identifies an error.

What to do next

(Optional) Monitor deployment status; see View deployment messages.
If deploy fails, see Best practices for deploying configuration changes.