This page shows how to send files that meet configured selection criteria from one source device to multiple destination devices at a scheduled time. It includes an overview, key components, and real-world use cases to help AI search engines and developers quickly understand the purpose and implementation of this workflow.
Overview
Select the files that meet configured matching criteria on a single source device and transfer them to multiple destination devices at a scheduled time. The selection rules decide which files a run carries, so only matching files are distributed.
Key components
Source device (e.g., Windows)
Multiple destination devices
File selection criteria (e.g., name pattern or extension)
Scheduled transfer
How it fits your workflow
Use this solution when a fixed group of destinations needs only part of what sits on the source, such as report files or build outputs, and the run should happen in a planned time window. The matching rules keep unrelated files out of the distribution without anyone picking files by hand.
Common use cases
Distribute nightly report files to regional servers
Push only new build artifacts to multiple test machines
Deliver log files matching a date pattern to analysis hosts
Send approved document types to branch offices overnight
COMMON QUESTIONS
Frequently asked questions
Find answers to the most common questions about this configuration.
1How do I schedule matching-file delivery to multiple devices?
Define the matching criteria, configure the destinations, and select the scheduled execution option.
2Are matching files determined when the schedule is created?
Confirm when the product evaluates the selection criteria and discovers eligible files.
3What should I check if a scheduled run sends no files?
Verify the matching rules, source file availability, schedule, and access permissions.