forums.wsusoffline.net

Now that MS has released a rollup for Win7 I would like to exclude those patches from my wsuoffline bundle. It's still very useful to use the wsuoffline to cover IE, .net & WMF 5 install. What is the best way to blacklist a set of KBs from getting bundled into the wsuoffline archive? Currently if you run wsuoffline it just re-installes all the KBs again.

info on the Win 7 rollup.
https://blogs.technet.microsoft.com/win ... 7-and-8-1/

Thanks,
Blake

Here is the list of redundant KBs I generated for Windows 7. Build two VMs. One with the rollup and one without. Then Diff'd the list of installed KBs to generate this list.

https://gist.github.com/trodemaster/fe8 ... 63554357d5

Hello Blake,

Although there isn't an official statement of the WOU author (i.e. WSUSUpdateAdmin) yet, I bet that a next release of the WOU software package will include the download and installation of the April 2016 rollup for Windows 7. So, if you aren't in a hurry, you could wait for that one.

For now, you can exclude the relevant updates from download by just creating a new text file .\exclude\custom\ExcludeList-w61-x64.txt that contains your list of KBs (without header, with empty line at the end).

Greetings
Gerby

Alright, I've not seen the discussion about the rollup package in this forum before. There are some arguments against using this package (telemetry, spy...). Let's see what happens...

Link to the thread (starts German): viewtopic.php?t=5622

I found they list all the updates they're replacing in the Package Details when you go to down the update.

I've copied them here for your convenience:

Code: Select all

KB2574819
KB2603229
KB2607047
KB2607576
KB2633952
KB2639308
KB2640148
KB2647753
KB2660075
KB2661254
KB2677070
KB2679255
KB2699779
KB2709630
KB2709981
KB2719857
KB2726535
KB2731771
KB2732059
KB2732487
KB2732500
KB2735855
KB2739159
KB2741355
KB2749655
KB2756822
KB2760730
KB2762895
KB2763523
KB2773072
KB2779562
KB2786081
KB2786400
KB2791765
KB2794119
KB2798162
KB2799926
KB2800095
KB2808679
KB2813956
KB2829104
KB2830477
KB2834140
KB2835174
KB2836502
KB2843630
KB2846960
KB2846960
KB2847077
KB2852386
KB2853952
KB2863058
KB2868116
KB2882822
KB2888049
KB2890882
KB2891804
KB2893519
KB2904266
KB2905454
KB2908783
KB2913152
KB2913431
KB2913751
KB2918077
KB2919469
KB2922717
KB2923398
KB2923545
KB2928562
KB2929733
KB2929755
KB2966583
KB2970228
KB2973337
KB2977728
KB2978092
KB2980245
KB2981580
KB2985461
KB2994023
KB2998527
KB2999226
KB3000988
KB3001554
KB3004394
KB3005788
KB3006121
KB3006137
KB3006625
KB3008627
KB3009736
KB3013410
KB3013531
KB3014406
KB3020338
KB3020370
KB3040272
KB3045645
KB3048761
KB3049874
KB3054476
KB3065979
KB3068708
KB3075249
KB3077715
KB3078667
KB3080079
KB3080149
KB3081954
KB3092627
KB3095649
KB3102429
KB3107998
KB3112148
KB3118401
KB3121255
KB3133977
KB3137061
KB3138378
KB3138901
KB3147071
KB3148851

Quick update on this. We have slipstreamed the rollup kb and the servicing kb into our win7 .iso. Then I created a exclude list for WOU and generated a smaller patch archive. These two things are working quite well for us now. We have automated windows 7 VM builds so this level of automation is needed. Finally doing a few pswindows updates and reboots gets us a fully patched system. The end result has reduced VM build time by 4-6 hours.

For WOU I highly suggest the next version start by installing the servicing KB and then the rollup KB. The systems seem to function quite well after that rollup is in place.

Thanks!!

Blake

Congrats, you now have Telemetry crap.

boco wrote:Congrats, you now have Telemetry crap.

That's actually desirable for using these images on our fully licensed enterprise private cloud. Let's be clear I'm not personally using windows 7 for anything in 2016 at that would be ridiculous...

See, requirements can be very different. I'm using Windows 7, exclusively, and don't touch anything 8 and beyond (at least for productive use). Using Windows 7 is not ridiculous, it is the last true Windows that wasn't made for hipsters. Good luck with that spyware-infected WinX crap.

Nobody will say anything against an optional inclusion of that pack - however, an inclusion for everyone would be ridiculous. Even Microsoft themselves tell that this pack is NOT a precondition for anything. You can completely ignore it and not miss anything. That's why calling it "Service Pack 2" is wrong. Likewise, it isn't a Rollup in the classical meaning (classical Service Packs and Rollups actually are preconditions for later patches).

Practically, we only need an alternative statics and exclude set. One that statically downloads and installs the pack, as well as excludes all security patches that the pack replaces. And a second one that stays as it is - no pack and no additional excludes.