Stop the use of Filtered collections.

BatchPatch Forums Home Forums BatchPatch Support Forum Stop the use of Filtered collections.

  • This topic has 1 reply, 2 voices, and was last updated 4 weeks ago by doug.
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #14341
    bk
    Participant

    We use WSUS to do all patch filtering. I need BatchPatch to install all available updates. Many of the Host are reporting “There are no applicable updates in the Filtered collection” We do not want any filtering. I know there are patches that need to be available. How do we stop the filtering?

    #14342
    doug
    Moderator

    First review the BatchPatch.log (the current run is printed in the Remote Agent Log column) for the host that is reporting no applicable updates in the filtered collection. You can view this under Actions > Windows updates > View BatchPatch.log

    In the BatchPatch.log you’ll see the reason why an update was filtered out. In between the following two sections of log each update that is filtered out will be printed with a reason such Reason:UpdateClassificationFiltering or similar.

    ::Begin filtering collection
    ::End filtering collection

    =============================

    Update classification filters are configured globally under Tools > Settings > Windows Update

    Update date filtering is configured globally under Tools > Settings > Windows Update

    Individual update filtering is configured per-row under Actions > Windows updates > Filter… and are stored in the column Download/Install Filter

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