ajs

It's possible I have some old copies of the media stored somewhere from when my employer used to work closely with RM, I'll have a look but please remind me in a week or two if I haven't got back to you.

What's the actual build number of the 21H2 install? Are the cumulative updates properly installing?

There's a small section in the following link that covers exporting/importing printer drivers as a package through the use of two commands that may be useful: https://lakeforestconsulting.com/adminprintnightmare/

The few times I've had to use the option, the update disappears from the client's list of available updates.

My understanding is that it will remove it when a machine has it installed but won't offer it as an update for those that don't.

Most of the time when I've seen this it's down to a resource issue on the WSUS server. It may be worth looking through the queue length and the private memory limits mentioned here: https://support.microsoft.com/en-us/help/4490414/windows-server-update-services-best-practices

Have you looked at Datto and their RMM offering (previously known as Autotask Endpoint Management and Centrastage prior to that). I spend most of my working day in it and find it works well for managing a wide variety of devices/sites.

I don't think Update Rollups are useful anymore since Microsoft when to the cumulative update model with Windows 10 but that doesn't mean they won't change their minds again in the future. If you have the disk space then it wouldn't hurt to have them enabled.

As far as I'm aware the generated files are all placed into the user's AppData directory (the font-cache stuff specifically going into AppData\Local\fontconfig\cache). You could, I guess, have some sort of script that copies files into that directory from a share but I would imagine they may still get regenerated from time to time (or perhaps cause other issues if they don't match what's on the system)

The main issue I found when looking at older versions of Dreamweaver on Windows 7 was that UAC was getting in the way. How is yours configured?

Try running Get-WindowsUpdateLog in Powershell and reading the generated file to see what's going on.

As far as I'm aware making sure that neither KB4011050 nor KB4011165 are installed are the only ways to fix the SIMS issue. I'm not aware of any updates released as part of the October set that replace either of the other updates.

Which then goes and breaks SIMS reports that use Pivot Tables :-)

Indeed it is, that'll teach me not to read things back before posting. KB4011140 is what I meant to type.

KB4011040 was released the other day which supersedes KB4011039 :-)