Cached Mode Updates Downloading

BatchPatch Forums Home Forums BatchPatch Support Forum Cached Mode Updates Downloading

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #13507
    Blue Sky
    Participant

    Hi

    Just bought version 2022.7.6.12.33
    I am having problems when using cached mode, it seem to be connected with Microsoft URL
    changes mentioned in this post:

    https://batchpatch.com/forums/x/topic/cached-mode-and-updates-not-downloading-to-the-local-update-cache-directory/

    Is there a fix for this yet?
    I am using a Job Queue to patch around 100 VM’s ranging in versions from 2008 to 2019.
    It is a bit of a pain to disable Cache Mode in my looped update check and takes a lot longer.
    Is there a way of checking for a failed download, that way I could disable only if there is a failed download,

    Yes I know 2008 is EOL, but these are customer VM’s and we cannot force a customer to upgrade 🙁

    #13508
    doug
    Moderator

    Hello –

    First, I would note that nothing in BatchPatch has changed. The 3 workarounds provided in the link that you included in your posting are still the same 3 workarounds that you can use today. The issue itself has not been “fixed” as there is no way for us to “fix” it currently.

    Second, I would note that online cached mode is really not a recommended mode. If you’re able to use online cached mode, then you really should just use online standard mode (non-cached), and then you don’t need to worry about this issue in the first place. If you have access to the internet or access to a WSUS then you generally should be using standard online mode (with NO caching). If you do not have access to the internet or a WSUS, then you would use offline mode. We do not generally recommend using online cached mode.

    Third, the job queue can check for a complete failure to download updates, but it cannot check for a “success with errors” which is generally what would happen if the overall operation completed, but an individual download was not able to complete, like in the scenario you are describing. That said, you do have a different option that you could use in the job queue called “If most recent ‘Check for available updates’ found any updates, goto label:X”. So instead of checking for the inability to download a particular update, you could just do a new check for updates, and if it finds any updates available, then it means not all updates have been isntalled yet. And in that case you could then switch to the other mode and do a new download/install to get that missing update installed.

    -Doug

    #13510
    Blue Sky
    Participant

    “Second, I would note that online cached mode is really not a recommended mode.”

    This is one of main the reasons I purchased BatchPatch, without caching I can
    schedule the update with a simple batch script on each of the VM’s running in task scheduler!

    I added a step in my loop after 3 runs “Disable cached mode(override global setting for this queue only)”

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.