Have you been able to upload new KB from Shavlik since you did the Upgrade to 12.7.1? Was this upgrade 2 steps (12.7.0) and then the Patch to 12.7.1?
Just trying to understand when this process broke... I would suggest putting in a ticket as time is ticking and devices need to be patched...
Are there any entries in the Master Server (Patch Manager) immediately following the placement of these XML files that reveal that the application tried to parse the files but failed?
You mean CAB files...?
Could it be that you are working according to this workaround:
The right WA (for 12.6 + 12+7):
If you had previously installed version 12.6, my statement is superfluous... because you already know how it works...
Good morning Steve! Apologies on the delayed response.
We are actually on 12.7.0 and using the new patch (build 180427q). This was a 12.6 --> 12.7 upgrade, and installed the latest patch via downloads.
We submitted a case on the same day I made this post. 12.7 utilizes the ivanti...looks like a CDN, for catalog updates and those are acquired via using the mtxpatch.exe script to download the manifest file. Sites will have issues with this if they have not coordinated with their NETMAN appropriately. CABs are no longer required/utilized as far as what we've been told.
We're conducting local troubleshooting now to ensure our proxy is not blocking the manifest file.
Will update with progress later, have a great one Steve!
Thank you for the reply. Not superfluous at all! New updates sometimes bring new procedures. The manifest.xml is failing for our site however and we believe it is a proxy issue. Working with our NETMAN and will update this thread soon-ish.