Understanding of Hide and Exclude list

BatchPatch Forums Home Forums BatchPatch Support Forum Understanding of Hide and Exclude list

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #12342
    Bernd Kallfelz
    Participant

    Hi,

    i have understanding problems with the hide and exclude feature. On some windows servers
    there are updates that are not allowed to be installed.
    So i can put the KB number into the hide and/or exclude list. But what will happen if the
    KB number changed? It is not really helpful to fill the KB numbers into the hide/exlude list every
    time before batchpatch will run scheduled.
    So i fill the hide/exlude list with following words for example:

    “preview”
    “Preview”
    “sql”
    “SQL”

    So will batchpatch look if the KB number or the phrase is in the list? If the phrase (not the KB number) is in the exclude list, will batchpatch install all other updates and a SQL update will not be installed but list as an available update?

    Kind regards

    #12343
    doug
    Moderator

    You may match on title text instead of KB ID. Matching is done by comparing the update title to the text of each item in the list. If the text of any item in the list is contained in the update title, the update will be excluded or hidden, depending on whether you are using the ‘exclude’ feature or the ‘hide’ feature.

    To guarantee uniqueness, we recommend entering the KB IDs, but if your goal is to always exclude or hide any update with ‘preview’ in the title, then you may enter ‘preview’ into the exclude or hide list (without the quotes) instead of using the KB ID.

    Excluding vs hiding:

    Excluding an update means that it will just be skipped for the current action. However, it will continue to appear in the list of available updates every time you scan for updates.

    Hiding an update means that it will become hidden on the target computer and will no longer appear in a search for available updates on that target computer. Caveat: Microsoft does have the ability to force a previously hidden update to become unhidden. This is not something that they do frequently, but they do it occasionally if they re-release an update under the same KB ID.

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