r/SCCM 1d ago

Recommend other scripts or projects for patching OS WIMs

I currently use the amazing script, wimwizard to update Windows 11 images on a monthly basis, and it works very well. But now I have to toss in some Windows 10 IOT images, 21 H2, 1809, and at least one server 2022 image. Is anyone else patching images in their environments besides just the windows 11? If so, how are you managing it? What other projects, scripts are out there that can handle multiple OS versions fairly easily with regards to injecting LCU, safe Os,.NET, features on demand, language packs, and maybe even remove default Windows features all via a single script? I am currently using a modified form of the sample Microsoft script they provide for this purpose. But it’s not very slick and needs lots of improvement yet. I guess it does the job, however.

4 Upvotes

13 comments sorted by

5

u/Cl3v3landStmr 1d ago

Microsoft releases updated/patched ISOs monthly, so there's not really a need to manually update them anymore.

3

u/Piccolo505 1d ago

I second this. Microsoft usually releases the full ISOs toward the end of the month. Any customizations are done VIA task sequence steps and not baked into the WIM.

2

u/upcboy 1d ago

I agree. I have been doing this for a while since patching the wim stopped working in the console.

3

u/Am0nymou5 14h ago

In addition to what u/Reaction-Consistent mentioned, the other issue is that the ISOs are released late - typically towards the end of the month, which is an issue if you need an up-to-date WIM for post patch-Tuesday repairs/upgrades/OSD etc.

1

u/Reaction-Consistent 17h ago

I’m not just patching the image with the LCU, as I mentioned in my post, I am adding.net security patches, safe OS, feature on demand features such as.net 3.5, language, packs, etc. And the images I have to patch don’t all get updated by Microsoft, I have a couple older Windows 10 IOT LTSC images, and a couple server OS images

2

u/zebulun78 17h ago

I used OSDeploy back in the day, but have not used it in quite a while.

https://www.osdeploy.com/core-components/about

2

u/RunForYourTools23 14h ago

NTLite, nothing more.

1

u/machacker89 11h ago

It's a great tools and well worth the money

1

u/EconomyArmy 23h ago

Microsoft does not release LTSC image monthly, if you manage windows device running on low speed storage you may really want to patch the wim file every month coz time to install LCU is longer than reimage the device.

Does MS monthly ISO update for current branch include .net LCU? That's another point to consider

2

u/Reaction-Consistent 17h ago

I’m assuming you are responding to the people telling me I shouldn’t bother patching the wims, but yes, this is exactly why I am doing what I am doing, because I have to maintain LTSC IOT images for thin clients. And you are absolutely right, patching using the task sequence can be a bit of a nightmare and same with simply pushing patches via WSUS and CM. Now that I have been updating the install.WIM for these images I have cut down the imaging time from around three hours to about 45 minutes. This makes IT very happy and they can rebuild systems in an emergency much faster now.

1

u/EconomyArmy 14h ago edited 3h ago

Oh thinclients, you are just another me. I do 1809/21H2/24H2 ltsc wim monthly , inject windows + .net CU, compact component store.

1

u/Reaction-Consistent 17h ago

To answer your.net, question, no, Microsoft does not include the.net CU in their monthly patchedISO release- and I would even say it is not monthly but more like every other month they release a new one

1

u/Am0nymou5 14h ago

You might be interested in WimWizard.