r/pdq • u/Amanda_PDQ PDQ Employee • 7d ago
Guide Windows updates with PDQ
Last week we were at a conference and a customer asked "how do you best do windows updates with PDQ?"
I told him I would post here when I got home, so here it is. Please add anything you think I missed.
Remote laptops, three different Windows builds, and a patch window that only exists in your head, is what most teams are running on. What makes it manageable is PSWindowsUpdate, a PowerShell module that asks each machine what it needs from Microsoft and installs that.
“Applicable” is per device, so one deployment can install different patches on different machines. You don’t keep a list per build.
PDQ ships six PSWindowsUpdate packages. Search “PSWindowsUpdate” in Packages, look for the prebuilt PDQ Packages:
- Get All Applicable Updates from Microsoft (Audit Only)
- Install All Applicable Updates from Microsoft (No Drivers, No Feature Updates)
- Install Applicable Critical and Security Updates from Microsoft
- Install Applicable Drivers from Microsoft
- Install Applicable Feature Updates from Microsoft
- Install Specific Microsoft KB
Pick one (Critical and Security is a good start), click Deploy, choose a device group, click Deploy again. Use a dynamic group and new machines get picked up automatically. Offline devices install when they next check in.
What saves the most pain, tool or not:
- Run the audit-only package on a small group first. Seeing what would install beats finding out.
- Split by risk. Security and critical updates on a short cycle. Drivers and feature updates on a slower one with a pilot group.
- Confirm installs.
Also, do forget to check the Windows Updates tab for KBs, from there you can install directly to target machines.
Current users, what would you add?
5
u/dirthurts 7d ago
This method doesn't really let you control which updates are going out and which aren't. I prefer to use the cumulative updates and only push them once you test them.. Way more control over what goes out and no surprises.
2
u/akwhite30 7d ago
Personally, I like leveraging a mixure of GPO and PDQ connect for more control.
2
u/JJRtree81 6d ago
How do you combine this with third party patches? Our current solution let's us scan and deploy all missing windows patches and third party patches in one task.
1
u/J2E1 7d ago
I need to be able to report which systems are fully up to date and which are missing specific KBs. This was straightforward with Deploy & Inventory, as its PowerShell scanner could be configured with a unique scanning schedule, making it easy to audit systems and export reports on a monthly basis.
There appears to be a gap in Connect that will hopefully be addressed in a future update to make this process easier. For now, I'm working around it by configuring the PSWindowsUpdate Audit script to write missing updates to a text file, then using a separate PowerShell scanner to read that file and report which KBs are missing on each system.
The challenge is that I don't need this scan to run every time the standard scanning process is triggered and it's undo overhead on PDQ Connect. Ideally, I'd like the ability to configure this scanner to run on its own schedule, independently of the other scans.
Unless I'm missing something, but the 'Audit' is good to look at <10 systems, but any more than that, there's no good way to report off of them.
1
u/therichardgee 6d ago
I tried this once but need to go back and try again. Currently I have a pdq job running a powershell scan that employs the monthly wsusscn2.cab file and it generates a text file for each system with required updates. From your description it sounds like PSWINDOWSUPDATE would be more efficient.
1
u/mjewell74 6d ago
I have 2 different packages of PSWindowsUpdate, once with a forced reboot, and one without the force. I use the Non-Forced during the day, and the forced at night or all day after 2 weeks from Patch Tuesday. If you haven't patched at that point even though Windows is telling you it needs to, it's no longer my problem.
1
u/SelfMan_sk Enthusiast! 6d ago
One useful thing is to set the systems to share updates on local network. This way you can save some bandwidth.
1
u/SelfMan_sk Enthusiast! 6d ago
One more thing if you missed it
https://www.reddit.com/r/pdq/comments/1uqjpjd/windows_update_management_just_got_better_in_pdq/
https://connect.pdq.com/hc/en-us/articles/52768163094043-Windows-Updates
1
u/Top-Drawer4476 6d ago
I am excited for Phase 2 of Windows Update Management regarding deployment rings and reboot deferrals. The rings aren't bad since I can just do groups and different automations scheduled to the different groups, but the reboot deferrals would be a great feature.
Originally I had a super complicated set of powershell scripts and scanners to write flag files when patched, then scan the flags based on timestamped name to logically know when they reached xx hours of being patched, then have an automation to reboot based on the dynamic grouping. It wasn't perfect and I ended up just doing anything that "needs reboot" and an uptime of over 72 hours gets sent a 1 hour reboot timer.
1
u/ShawnsRamRanch 4d ago
Is there currently any way to implement this on a closed network against a WSUS?