Verification
Fileset verification controls what happens when a deployed file is missing or changed and whether FileWave removes it when the deployment is removed. Choose the behavior per file based on whether FileWave should enforce the packaged copy, restore only missing content, or leave the delivered file unmanaged after installation.
|
Self Healing |
Verification restores the Fileset copy when the deployed file is missing or differs from the packaged version. |
Removing the Fileset deployment removes the file from the device. |
|
Download if Missing |
Verification restores the file only when it is missing. Changes made after the initial deployment are left in place. |
Removing the Fileset deployment removes the file from the device. |
|
Ignore At Verify (Left Behind) |
After initial delivery, verification does not restore or replace the file. |
Removing the Fileset deployment leaves the delivered file on the device. |
Two additional options refine initial deployment behavior:
|
Don’t overwrite existing files upon deployment |
Deliver the file only when a file with the same name does not already exist. |
|
Overwrite only if the existing file is older |
When overwrite behavior is enabled, replace the device file only if its modification date is older than the matching file in the Fileset. |
FileWave compares files by name and modification date.
When another Fileset already supplies the same required file, FileWave does not transfer a duplicate between the server and client. Initial-deployment overwrite settings are the exception.
No comments to display
No comments to display