I wanted to clarify the behavior of performing Extra.dat upgrades via ePO client tasks.
We have an extra.dat checked into the master repository.
We have multiple distributed repositories.
We have initiated a replication task to deploy the extra.dat to the have multiple distributed repositories, but, either:
The replication has not completed on repositories yet, or
The replication has failed on some repositories.
If we run a client update task to deploy the Extra.dat to a PC whose closest repository doesn't have the new Extra.DAT (it still has an old Extra.DAT), will the clients attempt to pull the Extra.dat from another repository? Or will the update task fail?
If we have an existing client update task created already for an old Extra.dat that's been set to run "asap" months ago, will the client task re-run again "asap" once the new Extra.dat is checked in? Usually to be on the safe side I delete and recreate the client task, but I just wanted to confirm the behavior.