Here is one scenario.
Old package installed successfully on 1000 machines.
Now, there is a logic change in the package, hence re-staged the package and updated DP's with newer package and source version.
Question is, we have many machines which showup content mismatch error. On the DP's the package is fine. When checked the logs, we see the machine is using the earlier package version from the local cache and trying to run it, inturn giving up content mismatch.
When there is a new advertisment created, it means newer policies go to the machine, so ideally it should freshly download the package from DP;s, which is not happening. whats the reason??
If i clear the cache, reset policies on machines, it download and installs all fine.
Ideally when new advert goes, policies refresh why does it go lookout and run the older version package from cache?? Ideally it should compare and sense that, there is a source version change, and download the newer version of package from DP. And should wait for me to clear the cache and on next re-run the new ad