>Another thing to be wary of is that in some circumstances current versions of Windows (server or client) will "block" files that arrive as an e-mail attachment or are downloaded from the Internet. In those cases the files need to be manually unblocked.
>
>This could come into play depending on how updated EXEs are delivered to the target environment.

Worse. I had a case when I discovered a bug in the exe, and since it was some simple thing and a simple fix, I built a new exe and downloaded it via ftp. And it worked once, but the fix wasn't complete (case when fixing one bug uncovers another), so I wrote another, found I made a typo, made a third. And then the third one didn't contain the fix. The filetimes were OK, this WAS the third version, but it worked like the 2nd. So I built a fourth version, which now also logged its version number. It downloaded alright, filetime has changed, all fine and dandy - but it DID NOT log the version number. Then I zipped the exe and downloaded it and hey, the filesize changed.

The smart feature in windowses was obviously thinking that I think the file didn't arrive alright the last time, but it knew it did, so there was no need to repeat the download, it simply changed the timestamp on the existing file, I guess to save me time. Even with zips, I had to name them with ordinal numbers, just in case.

Nothing to do with scheduled tasks, except that it happened in a case related to it. But then I saw it happen a few other times, I guess W2010 and/or later, not sure.