1 of 1 people found this helpful
In checking this I found what the problem is. The file being downloaded is actually correct and will install the latest file version, but when Protect downloads the patch it is being renamed based on the "Shavlik File Name" in our logic. So, even with it named this way you can still successfully deploy the latest version (for the time being).
I spoke with our content team about this, and they will be updating the 'Shavlik File name' so that the name of the file downloaded reflects the version properly. This should be fixed in the next XML release.
Thanks for letting us know about this.
I think if you already had a 5.22 version, the 5.23 version didn't even get downloaded. I know that when I did a few test deployments, the MSRT update failed until I put the new files in with the old name. (We deployed patches at noon today after doing the renaming and I'm not seeing any MSRT failures for the machines that have already rebooted.)
I think if you already had a 5.22 version, the 5.23 version didn't even get downloaded.
Yeah that will probably be true since the name isn't changed. However, it will be fixed after the next XML release. Sorry about the problems this caused. I'm sure our content team will try to make sure the Shavlik File Name gets updated whenever MSRT is updated from now on.
This is now corrected as of XML 18.104.22.1684 Last Modified 4/16/2015.
The fix was not announced, but I've confirmed the download name should now be correct.