--- title: "Deploy pending changes to a device" slug: "deploy-pending-changes-to-a-device-10" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:28:35Z published: 2026-11-19T12:28:35Z canonical: "docs.trellix.com/deploy-pending-changes-to-a-device-10" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Deploy pending changes to a device When you make any configuration changes or policy changes on the Manager, or a new/updated signature set is available from Trellix, you must apply these updates to the devices (such as Sensors and NTBA Appliances) in your deployment for the changes to take effect. Note the following: - Configuration changes such as port configuration, non-standard ports, and interface traffic types are updated regardless of the changes made to the Sensor, interface/ subinterface. - NTBA configuration updates refer to the changes done in the several tabs of the **Devices** node. - Policy changes are updated on the Sensor or NTBA Appliance in case of a newly applied policy, or change made to the current enforced policy. - Signature updates contain new and/or modified signatures that can be applied to the latest attacks. - When policy and rule updates are applied to the devices, the current traffic analysis is not impacted until the last phase of configuration updates (i.e the Manager status update is at 95%). - Policy deployments are governed solely by the verification of a valid core Base System License. Refer the following steps to deploy the configuration changes to all devices in the admin domain or at a device level. 1. Go to **Devices** → **** → **Global** → **Device Manager**. The **Device Manager** page is displayed. **Device Manager** ![Device Manager](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-8b4cab66-5499-52de-6ced-b11ac318f93b(9).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A16Z&se=2026-11-20T11%3A08%3A16Z&sr=c&sp=r&sig=B96vg29VNOsCqWXFSwnLhwZl5QhEcrU2%2BkVDGSWuAtU%3D) 2. Click **Sensors** tab. Select the required Sensor from the list. 3. Select **Sync**. The **Sync: ** window is displayed. 4. Select the required configurations and click **Sync**. > [!NOTE] > Note > > The Manager provides an option to concurrently deploy pending changes for multiple Sensors. When you select multiple Sensors for deployment, the **Bulk Sync** window is displayed and enables all check-boxes by default. Select the options you wish to deploy and click **Sync**. **Sync: window** ![Sync: <Device Name> window](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-527586c7-6aba-11c4-6267-a76667bbc045(4).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A16Z&se=2026-11-20T11%3A08%3A16Z&sr=c&sp=r&sig=B96vg29VNOsCqWXFSwnLhwZl5QhEcrU2%2BkVDGSWuAtU%3D) 5. If you deploy signatures to a Sensor running software earlier than version 11.1M12 and has Suricata snort enabled, review the confirmation warning dialog box. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/image(130).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A16Z&se=2026-11-20T11%3A08%3A16Z&sr=c&sp=r&sig=B96vg29VNOsCqWXFSwnLhwZl5QhEcrU2%2BkVDGSWuAtU%3D) 1. Click **OK** to proceed with deployment to the legacy Sensor. 2. Click **Cancel** to abort deployment and upgrade the Sensor software first. 6. A **Deployment Details** dialog box is displayed. Click ![GUID-16F4A5CB-64F8-49D7-9C0D-A9BB21DAA8A6-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-59a740b8-96ad-6562-51dc-cc1f9d1e23c0(9).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A16Z&se=2026-11-20T11%3A08%3A16Z&sr=c&sp=r&sig=B96vg29VNOsCqWXFSwnLhwZl5QhEcrU2%2BkVDGSWuAtU%3D). **Deployment Details** ![Deployment Details](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-bdb0a8b9-f9f5-e314-c636-ef9cb7d860cd(9).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A16Z&se=2026-11-20T11%3A08%3A16Z&sr=c&sp=r&sig=B96vg29VNOsCqWXFSwnLhwZl5QhEcrU2%2BkVDGSWuAtU%3D) > [!NOTE] > Caution > > If signature compilation fails on a Sensor running Suricata 3.x, the status window displays an enhanced error banner: > > "***Error: Please close the window. Failure in compilation process***." Click the **failure report** hyperlink in the banner to download the diagnostic report. 7. You can also deploy the changes to a specific device from **Devices** **** **Devices** **** **Deploy Pending Changes**. Select the required configurations and click **Deploy**. **Device-level deploy pending changes** ![Device-level deploy pending changes](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-062ae198-a0dd-5e06-2a03-7c88a684b8b3(3).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A16Z&se=2026-11-20T11%3A08%3A16Z&sr=c&sp=r&sig=B96vg29VNOsCqWXFSwnLhwZl5QhEcrU2%2BkVDGSWuAtU%3D) The following status can be viewed from **Sync** section of **Status** column: | Status | Description | | --- | --- | | **Synchronized** | Indicates that no pending changes are required. | | **Sync in progress** | Indicates when the deployment is in progress. | | **Sync required** | Indicates if any pending changes are required. | | **---** | Indicates that there is no trust established between the Sensor and the Manager. | 8. Click **Export Sync File** under **Other Actions** to view and export the deployment changes file to indirect mode Sensors. The changes can then be deployed to the Sensors manually using the CLI command window. 9. Click ![GUID-DE8F9231-1BB5-42A7-B78B-1FDD431543A8-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-dee6af6b-3b7c-566d-9e87-c2e3fc01abd8(9).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A16Z&se=2026-11-20T11%3A08%3A16Z&sr=c&sp=r&sig=B96vg29VNOsCqWXFSwnLhwZl5QhEcrU2%2BkVDGSWuAtU%3D) to refresh the page and the status of the deployment.