I'm trying to download the latest patches using the PowerShell script and the .xml file that my offline Console created. The patches do download with no issues or errors, with the exception of one file...the engines.manifest.cab file. The error it produces is "Failed: Error - System.Net.WebException: The remote server returned an error: (404) Not Found. The full path of the script looks right to me and if I manually attempt to download the engines.manifest.cab file through a web browser I get the same error. Does anyone have any ideas as to why?

Thank you for your quick response. However, the PowerShell script I just downloaded from that link is the same one I am currently using. Is it possible that it's "too early" to be downloading the DataFiles and Patches? The better question is, how do I know when Ivanti is ready to release the Patches to the public? I signed up for the webinars but there is no clear email notifying users that the patches are ready for download every month, unless I am missing something. Thanks again.

There is no such thing really as downloading stuff to early. Our Datafiles can be technically downloaded at any point. As for patches, the only things that should download are ones that you have scanned as missing in your scan results and are listed in the exported CSV file.

Can you provide the command you're using when trying to download the datafiles? I downloaded a fresh copy of the script and don't see anything regarding an engines.manifest.cab file being downloaded, so I'm not sure where you're getting that from, but that shouldn't be happening.

As for when updates are released in our XML updates, you can either visit protect7.shavlik.com or use this link to register your email to get the notification emails.

This is for Ivanti Patch forSCCM just to be clear on the product that I am using. The SCCM Console is on an Offline Network and I have not had any problems in previous months of patching. This just started this month. I am a little weak with PowerShell and scripting, so perhaps I may have messed up the command from last month, but I'm not sure anymore.

I forgot to mention one more thing...I went back to the Offline SCCM Console and reproduced another .xml file just to make sure there wasn't any corruption in the first one, and my results were the same with that command above and the new .xml file. Thanks looking into this for me.