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 :-)

The ability to set the local administrator password via a GPO was removed in an update years ago and it was deemed a potential security issue. LAPS is certainly the way to go now.

My understanding is that quotas are calculated based on files that the user is an owner of. Are the user shares on the same drives as any other shared areas?

The main thing that the process tries to do in CC4 is to copy over a default NTUSER.DAT from a copy of the RM Default Profile on the server into each user's profile directory (you can tell if it's worked either by checking for error messages in the Event Logs, RM logfiles or checking that the NTUSER.DAT file on the server is 512KB). I can't recall if it touches any other aspect of the user's profile unfortunately. When the user logs in, unless the profile on the station is completely corrupted, it should recreate user-specific aspects of the profile and then save it all back to the server when they log off.

My copy automatically updates as well, the website opens to show the release notes (amongst other things). Even if you download a fresh copy and extract it over your existing copy, your settings/downloads should be preserved.

Out of interest, when was the last time any maintenance was done on the WSUS instance on the server? Unless it's a very old installation I would expect WSUS to store its updates on the D: drive and if the default product selections are still in place then WSUS could well have downloaded updates for software that was never/is no longer in use. Also, are there any old packages (particularly RM system ones) that can be removed from the RMMC (assuming none of the stations need a core update of course)? While each one may not free up a lot of space, removing a large number of them can free up quite a bit of space. May be worth running TreeSizeFree or something over the drive to see exactly where the space is being taken up.

WSUS3/2008(R2) can't support the Feature Upgrades functionality of Windows 10. The only way to fully update/upgrade Windows 10 clients through WSUS is via WSUS4/2012 or later. One mention of it from Microsoft is here : https://blogs.technet.microsoft.com/wsus/2015/12/03/important-update-for-wsus-4-0-kb-3095113/

The negative space has been a UI bug for years that I think they've probably deemed as unimportant ( I do recall a more technical explanation but it didn't involve a permanent fix). If you're still having issues creating users then check the Event Logs on the server as the RM User Manager software should be logging issues when it encounters them.

Fair enough. I remember the initial panic at work when it first came out and the post-install steps hadn't been fully released/spotted.

Out of interest, why remove KB3159706 rather than following (or scripting) the post-install configuration items to allow the WSUS console to work again?

If done through the RMMC (and assuming it works properly) then the home drive and profile should be deleted when the user is.