New advertisement uses old package from the cache in machine

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

February 27th, 2015 5:06am

A policy change or new advert has nothing to do with the content and will not cause the content to be re-downloaded. The only reason the content should be re-downloaded is if the content itself changed. And as with all changes, clients must update their policy to learn of content changes if they have been made.

Exactly what error are you seeing and what log are you getting the error in?

Free Windows Admin Tool Kit Click here and download it now
February 27th, 2015 9:47am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics