well there's 2 strategies:
- you can have the active member download, install and sync to peer, this will download and install, then copy the file over to passive and install there too (or you can download and sync, which will download and copy but not install)
with this setting the secondary device does not really need a schedule ince the primary will perform that task
- or you can have each member do their own schedule and not use the sync option but that could lead to mismatch if one has install and the other has download only
There is a revert option available in the dynamic updates themselves which i would recommend to prevent running into the mismatch:
If your main concern is that a bad content package would be installed and you need a fallback, i would look into using the 'threshold' function first
This will check for the release date/time of a content package and adds x time (as configured in the threshold) before checking the update server again. if the same file is still available it will go ahead and install, if a newer update is available (emergency content release or content package retracted) the instll will be aborted and the threshold is reset if a new package is available. after the second threshold a last check is done and if the package is still available, the emergency package is installed. if yet another version is see, the install will be abortted altogether and wait until the next scheduled event (watch out for AV updates as these can have several valid releases in a day where content is usually updated once to twice a week)
on top of the above, there's still the manual revert
hope this helps!
well there's 2 strategies:
- you can have the active member download, install and sync to peer, this will download and install, then copy the file over to passive and install there too (or you can download and sync, which will download and copy but not install)
with this setting the secondary device does not really need a schedule ince the primary will perform that task
- or you can have each member do their own schedule and not use the sync option but that could lead to mismatch if one has install and the other has download only
There is a revert option available in the dynamic updates themselves which i would recommend to prevent running into the mismatch:
If your main concern is that a bad content package would be installed and you need a fallback, i would look into using the 'threshold' function first
This will check for the release date/time of a content package and adds x time (as configured in the threshold) before checking the update server again. if the same file is still available it will go ahead and install, if a newer update is available (emergency content release or content package retracted) the instll will be aborted and the threshold is reset if a new package is available. after the second threshold a last check is done and if the package is still available, the emergency package is installed. if yet another version is see, the install will be abortted altogether and wait until the next scheduled event (watch out for AV updates as these can have several valid releases in a day where content is usually updated once to twice a week)
on top of the above, there's still the manual revert
hope this helps!
