Batchpatch simple question

[mikeleahy1234]

Hi All

I am new enough to batchpatch . I have a question though on what happens if you untick service packs and put patch exclusions in place

From what i see , the service packs etc still get downloaded to the VM but not installed, is this correct ? Do the excluded patches also get downloaded to the VM but not installed ?

[doug]

Looks like you found a bug. I just did some testing, and here is what I found:

When BatchPatch is running in default/normal/regular mode (NOT cached mode), BatchPatch will not download updates for which the update classification box is unticked in ‘Tools > Settings > Windows Update > Update Classification Filtering’

When BatchPatch is running in cached mode, BatchPatch will still download updates to the BatchPatch cache folder for which the update classification box is unticked in ‘Tools > Settings > Windows Update > Update Classification Filtering’. The update will be downloaded to the BatchPatch cache folder, and the update will be copied to the target computer’s temporary cache folder ‘C:Program FilesBatchPatchcache’, but BatchPatch will *not* actually cache the update in the target computer’s Windows Update repository. This is to the say that Windows Update on the target computer will not know anything about the downloaded update and will still think the update is NOT downloaded. The update files in question will only exist in the BatchPatch cache folder and in the target computer temp/staging/cache directory – default is ‘C:Program FilesBatchPatchcache’ but will not be “downloaded” to the Windows Update database/repository on target computers.

Note, if an update is excluded in the textual/graphical filters in BatchPatch, the update will not be downloaded at all. But if it is not excluded by the textual/graphical filters and it is only excluded by unticking the ‘update classification filtering’ box, then when cached mode is enabled, the update will still be downloaded to the BatchPatch cache as noted above but will not be downloaded to the target computer’s Windows Update repository, and so Windows Update will have no idea about it. This means that the only issue it can/would/should be able to cause is taking up space on disk in C:Program FilesBatchPatchcache on target computers, but you can safely delete this folder at any time.

We will look into getting this fixed asap.

Thanks,

Doug

[Author]

Posts