spgsitsupport Posted June 23, 2018 Report post Posted June 23, 2018 I have a script that I need to run daily (via Package/Program deployment). Not a problem, set it to always re-run & it does it fine at scheduled times. But on weekly basis the script changes (version number inside). I can re-distribute it & add another schedule, but the new .bat never makes to the client from DP Client keeps re-running the existing (by now old) local cache .bat Only way I found is to re-create whole Package/Program & deploy it again. But I find it rather drastic. Anybody has a better idea? Seb Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted June 23, 2018 Report post Posted June 23, 2018 That would only happen if the DPs are not updated with the newest source files. Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted June 29, 2018 Report post Posted June 29, 2018 Ofcourse DP is updated! That what re-distribute action does Yet on client the .cmd is NOT downloaded new Seb Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted June 30, 2018 Report post Posted June 30, 2018 I know that you don't like the answer but in a nutshell, it is right. Think about it. How does a CM client know that there are new source files? At a high level, the processes is a follows. Source Files are updated. CM is told to update source files CM creates the package for replication. CM update the source version within db. CM create a policy stating there is a new version for package x. DP are told to update source files DP actually get new source files. CM update the source version within db. Client contact MP and for all policies All policies are evaluated Client run package x, notices that it's version does not match package x Client downloads new source files Client run package x. If client do not see the latest version of the package then something is wrong in step 1-4. Once step 5 happens, all clients will wait for the newest source files to be on their DP once the policies are evaluated. Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted June 30, 2018 Report post Posted June 30, 2018 I understand, how it is supposed to work. But if I update the DP & then run it on a PC that never had it previously deployed then correct version is downloaded & executed (hence the version in DP is correct) But if I simply expect it to re-run on PC that had it previously deployed (and did run on it as part of schedule), then new .cmd is simply not downloaded & cached one is executed. That is what I see Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted June 30, 2018 Report post Posted June 30, 2018 Are you seeing the new policies being download? For example, if the computer is off the network, the computer will re-run with the old version, why because as far as it is concerned those policies are still current. Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted July 5, 2018 Report post Posted July 5, 2018 Yes, policies are evaluated & applied fine Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted July 5, 2018 Report post Posted July 5, 2018 Since that is not the expected results. You will need to open a support case with CSS (Microsoft Support) directly to get support for this issues. Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted August 7, 2018 Report post Posted August 7, 2018 I did test it again (and kept checking) and it did work in the end as expected. No idea what it was when it was not working, but works now, so I am happy!, thanks Quote Share this post Link to post Share on other sites More sharing options...
