The File Distribution Policy module is used to remotely and centrally push various files—such as configuration files, training materials, and promotional assets—to designated devices or device groups. It supports one-click bulk distribution and tracking of delivery results.

This module exists as an independent policy and is not involved in the “module-level merge, latest configuration takes precedence” policy stacking mechanism, nor does it support policy compliance detection or automatic remediation.

The platform supports a complete policy lifecycle, including Create, Configure, Submit, Approve, Publish, Edit, Deactivate, Restore, and Delete. The distribution process is visual, controllable, and traceable.

Notes

Primary Operations

Secondary Operations

Typical Use Cases

The File Distribution Policy is used to batch push one or more uploaded files (such as configuration templates, training manuals, promotional materials, etc.) to target devices or device groups. The policy configuration includes file selection, delivery schedule, download behavior, and target device scope.

Unlike Application Policies or Device Policies, the File Distribution Policy is an independent policy type, not involved in the “module-level merge, latest configuration takes precedence” stacking mechanism, and does not support device compliance detection.

Administrators can use the Details page to view the complete configuration and execution status of a File Distribution Policy. The details include the policy overview, file list, distribution schedule, target devices, delivery logs, and system logs, which facilitate policy verification, operational tracking, and troubleshooting.

You can enter the policy details view by clicking the Details button on the policy list page.

The top section displays the core policy information, including:

The policy details contain the following tab pages:

1) Selected Files

Displays all file information bound to the policy, including:

2) Distribution Configuration

Displays the delivery method and behavior settings, including:

3) Deployment Configuration

Displays the target object scope of the policy, including:

4) Operation Logs

Records all operation actions on the current policy, including:

Supports filtering by operation type, time range, and operation ID.

5) System Logs

Automatically records the delivery execution status, including:

If there has been no automatic delivery behavior, the list will be empty.

The submit operation is used to advance a Draft status File Distribution Policy to the Pending Review stage, entering the approval process. Once submitted, the current configuration of the policy will be locked and cannot be edited again until it is reviewed and processed by an approver before proceeding to publication.

This operation is suitable for scenarios that require policy review and control, such as multi-role collaboration, unified content management, and important configuration verification.

When a File Distribution Policy is submitted by its creator, it enters the Pending Review status. Approvers can review the policy in the policy list and choose to either Approve or Reject it. Only after the policy is approved will it be officially published and trigger the file distribution process.

The approval operation is typically performed by accounts with approval permissions, ensuring that the policy content meets standards, file content is compliant, and the target device selection is reasonable.

If the system’s approval process is disabled, policies will be automatically considered Approved upon submission, requiring no manual action.

When a published File Distribution Policy needs to be updated (such as file list, delivery schedule, or target device scope), administrators can perform the Edit operation. The system will create a new version based on the current policy, automatically archiving the original version. The new version must be resubmitted and approved before it becomes effective.

Editing a policy does not affect previously executed historical versions; it only impacts execution for the new version. The platform supports multiple edits within a policy's lifecycle, with each edit generating an independent version for future reference and tracking.

When a File Distribution Policy is in Published status, administrators can manually execute the Distribute Policy action to immediately push the policy content to its associated devices or device groups, ensuring files are delivered to endpoints promptly.

This feature is useful in scenarios such as:

The Distribute Policy operation does not modify the policy content; it only triggers a new delivery task. Execution results can be viewed in the Operation Logs.

Administrators can execute the Disable operation on a File Distribution Policy that is in Published status. Once disabled, the policy will immediately become inactive, and no further file delivery tasks will be executed to devices. All associated devices will no longer receive files from this policy.

This operation is commonly used in the following scenarios:

Once disabled, the policy will no longer participate in scheduling. It can later be reactivated via the Enable Policy operation.

The Enable operation is used to reactivate a File Distribution Policy that is in Disabled status, restoring it to Published status. Once enabled, the policy becomes effective again, and the system will deliver the configured files to the associated devices at the scheduled time.

This feature is suitable for scenarios where an old policy needs to be restored or a temporarily disabled policy needs to be re-enabled. It eliminates the need to recreate the policy, improving operational efficiency.

Enabling the policy does not affect its original version number or configuration, and it does not re-enter the approval process. Once enabled, the policy is immediately ready for delivery.

After enabling, you can go to the Details page or Operation Logs to track the policy execution status. If you need to trigger immediate delivery, use the Deliver Policy operation.

The Archive operation is used to remove historical versions or unused File Distribution Policies from the main list and move them to the Archived section for centralized management and record retention. Archived policies are not deleted — they retain complete records and support View, Restore, and Delete actions.

This feature is suitable for the following scenarios:

The archive action does not require a confirmation popup. Once clicked, it takes effect immediately and the policy is moved to the Archived tab.

When a policy has been archived but needs to be modified, resubmitted, or re-executed, the Restore function can be used to move it from the Archived list back to the main policy list. After restoration, the policy will always enter the "Draft" status, allowing further operations such as submission, approval, or modification.

This feature is useful in scenarios such as:

The restore action does not require a confirmation popup — it takes effect immediately upon clicking.

The delete action is used to permanently remove a file distribution policy from the system and is only available for policies in Archived status. Once deleted, the policy will no longer appear in any list, and all version information will be cleared.

Before deletion, the system will display a confirmation dialog to ensure the user fully understands the action, preventing accidental deletion.

This action performs a logical deletion — the main policy information (including content and all versions) will be removed, but related log records (such as operation logs and system logs) will be retained for auditing and traceability purposes.

This section explains the configuration items involved in the File Distribution Policy to help understand their meaning and the impact on device behavior.

​