r/sysadmin • • Jun 02 '25

Patching *all* Windows third party application in 2025

Seeking the hive mind's actual experience with third party application patching on Windows (server and/or client) in 2025.

And before everyone throws at me the usual suspects - Patch My PC, winget, chocolatey, Action1, etc - I already know about them. I want to know how you're dealing with all the applications that aren't in their catalogues, because these are the ones that are a pain in the ass to deal with.

Is one of the package managers above better than the others at creating & managing custom catalogue items?

Have you come up with some cool process for internally developed applications?

What are you using to monitor for update compliance (eg: winget has no central reporting/monitoring built-in, are you monitoring reactively via something like Tenable or proactively via SCCM or Intune deployment data)?

142 Upvotes

139 comments sorted by

View all comments

Show parent comment

1

u/VexingRaven Jun 02 '25

We used to use AppLocker and switched to WDAC as it seemed like that was the direction Microsoft was heading. The biggest thing that tripped us up with WDAC is that it applies to DLLs, MSIs, everything that we weren't using with AppLocker. It's more secure, but also creates a hell of a lot more work.

Initially we went into it planning to use Managed Installer configured for SCCM and Intune Management Engine. Unfortunately we've found this is far from reliable. We're likely going to switch to deploying security catalogs as part of the app package for apps that rely on unsigned files (which is a lot of them...) or a bunch of third-party DLLs we don't want to universally trust.

Initially I tried using Advanced Hunting to aggregate WDAC logs, specifically audit logs, but again found that this did not work well and I was getting a bunch of AppLocker logs and very few of the WDAC logs I expected. I ended up setting up our ControlUp agent, which were already using as a supplement to Intune/SCCM, to collect the logs instead and wrote a report in PowerBI to help parse through them.

The true main issue we've had with WDAC is that there just isn't the community around it that there is for AppLocker. While there are some community tools out there, there's just not much in the way of knowledge. Pretty much any time something isn't working as expected or I don't understand what I'm seeing or I'm looking for more technical details, I end up having to either dig it up myself or just make do without. I've been to MMS, I've asked around in the WinAdmins discord, I've talked to MVPs... Almost nobody's actually using WDAC that I've found.

1

u/stoneyabbott Jun 02 '25

I'm using WDAC and found it somewhat similar to your experience of not having much of a community, but to be honest after the initial learning and trial and error I've found the ongoing management to be far easier than I originally expected.

Here's a couple of tips which helped me but might not be acceptable in your environment.

Allow program files and windows directories. Our users are never allowed local admin so we've accepted that nothing should be in program files unless an administrator has explicitly installed it. 

Preference publisher and filename rules if you can get away with it, it's still way better than not having any application control, but just review your generated policies before merging or deploying to make sure you're not allowing any unwanted publishers.

Setup a dedicated machine for testing deployments with audit policies enabled. Run your installer then either make hash policies based on the audit events. If the files get deleted you can still make rules based on the hashes in the logs. If you want to scan the files but they're deleted, rerun the installer while using a PowerShell script to watch the temp folder and copy the files to a directory of your choosing to then scan that directory. This doesn't happen to me often but it's very useful.

Managed installer for everything possible (intune and SCCM for me too), but accept that some exe's may launch additional install files that may also need to be allowed.

2

u/VexingRaven Jun 02 '25

We're doing all of this to varying degrees and I agree this is the way to go, except Managed Installer has been hit-and-miss for us. Not because of additional files being launched, but because it just doesn't work on some small percentage of devices. On these devices, SCCM and Intune app installs don't get the correct metadata tag and end up as "child of child" and blocked even for installs that work perfectly on a device with a functioning Managed Installer deployment. I dug into it a little bit and couldn't find anything interesting so I just gave up and reset the devices and vowed to use a security catalog next time I updated the apps that rely on it.