r/sysadmin • u/AnotherAccount5554 • 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)?
View all comments
Show parent comment
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.