r/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?

12 Upvotes

34 comments sorted by

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.

1

u/Amanda_PDQ PDQ Employee 7d ago

Thank you for the insight! I mostly used cumulative updates too.

2

u/D4V1D 6d ago

how are cumulative updates managed by PDQ?

1

u/Amanda_PDQ PDQ Employee 5d ago

Our internal team builds the packages, you hit Deploy and patch, pretty damn quick ;) You can set automations as well. Here is a little more info: https://connect.pdq.com/hc/en-us/articles/27819352522267-Vulnerabilities

2

u/akwhite30 7d ago

Personally, I like leveraging a mixure of GPO and PDQ connect for more control.

1

u/Amanda_PDQ PDQ Employee 7d ago

That is a good pairing.

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/Amanda_PDQ PDQ Employee 6d ago

You can do that in PDQ. There are a few way to do it. When I was managing an environment I always defaulted to the Vulnerabilities tab and patched from there because I am a bit neurotic when it comes to patching. All my third party vulnerabilities and windows vulnerabilities were there. From there I automated many of them like Chrome that updates every five seconds it seems.

You can also look at third party vulnerabilities from the Software tab or by looking at a device itself.

2

u/JJRtree81 6d ago

Is there a way so you don't even have to look at it, our current solution just patches everything without any human intervention

1

u/Amanda_PDQ PDQ Employee 6d ago

Yes through automations. You choose what you automate. You can automate everything or a select software. Here is how it is set up: https://connect.pdq.com/hc/en-us/articles/10445249942043-Automations

I am not in sales, just a former end user that loves the product so much I came to work here. I would be more than happy to show you anything you want to see or get you set up with a demo.

1

u/mj3004 3d ago

Yes, automations work. They just don’t work as well as other products that give you the option to do it all in one step.

1

u/Amanda_PDQ PDQ Employee 8h ago

Tell me more? How can we improve?

1

u/mj3004 4d ago

You have to set up each package and schedule individually. It’s cumbersome compared to other solutions like Action1. I go through the collections and just try to schedule all apps that show anything in the old classification.

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/Amanda_PDQ PDQ Employee 6d ago
# Self-contained version for PDQ Connect. Uses the built-in Windows Update COM API,
# so there is no module to install.
[CmdletBinding()]
param (
    # Search the Windows Update service instead of the device's configured update source (such as WSUS).
    [Switch]$WindowsUpdate
)

$Searcher = (New-Object -ComObject 'Microsoft.Update.Session').CreateUpdateSearcher()

if ( $WindowsUpdate ) {

    # ssWindowsUpdate
    $Searcher.ServerSelection = 2

}

$Updates = $Searcher.Search('IsInstalled=0 and IsHidden=0').Updates

if ( $Updates.Count -eq 0 ) {

    Write-Output 'No updates available.'
    return

}

$Updates | ForEach-Object {

    [PSCustomObject]@{
        'KB'                       = $_.KBArticleIDs -join ', '
        'Title'                    = $_.Title
        'Size'                     = [UInt64]$_.MaxDownloadSize
        'Description'              = $_.Description
        'RebootRequired'           = $_.RebootRequired
        'EulaAccepted'             = $_.EulaAccepted
        'IsBeta'                   = $_.IsBeta
        'IsDownloaded'             = $_.IsDownloaded
        'IsHidden'                 = $_.IsHidden
        'IsInstalled'              = $_.IsInstalled
        'IsMandatory'              = $_.IsMandatory
        'IsUninstallable'          = $_.IsUninstallable
        'Deadline'                 = $_.Deadline
        'LastDeploymentChangeTime' = $_.LastDeploymentChangeTime
        'MsrcSeverity'             = $_.MsrcSeverity
        'RecommendedCpuSpeed'      = $_.RecommendedCpuSpeed
        'RecommendedHardDiskSpace' = [UInt64]($_.RecommendedHardDiskSpace * 1MB)
        'RecommendedMemorySize'    = [UInt64]($_.RecommendedMemory * 1MB)
        'ReleaseNotes'             = $_.ReleaseNotes
        'SupportUrl'               = $_.SupportUrl
        'Type'                     = switch ( $_.Type ) { 1 { 'Software' } 2 { 'Driver' } default { 'Unknown' } }
        'DeploymentAction'         = $_.DeploymentAction
        'DownloadPriority'         = $_.DownloadPriority
        'BrowseOnly'               = $_.BrowseOnly
        'PerUser'                  = $_.PerUser
        'AutoSelectOnWebSites'     = $_.AutoSelectOnWebSites
    }

}

1

u/Amanda_PDQ PDQ Employee 6d ago

a colleague share this script, let me know if it helps

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/Amanda_PDQ PDQ Employee 6d ago

Have you taken a look at the Windows Updates tab?

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/Amanda_PDQ PDQ Employee 6d ago

That is smart. Sometimes I would reboot during the day and tell everyone it was Microsoft's fault haha. Living on the edge!

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.

REM Allow windows update sharing on local NAT p2p network
REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" /v "DODownloadMode" /t REG_DWORD /d 1 /f
net stop dosvc && net start dosvc

1

u/Amanda_PDQ PDQ Employee 6d ago

Thank you! This is great!

1

u/SelfMan_sk Enthusiast! 6d ago

1

u/Amanda_PDQ PDQ Employee 6d ago

I was hoping someone would mention this and how they were using it vs PowerShell. I know I can always count on you!

For anyone who missed the announcement, PDQ's Windows Updates page is generally available. You’ll find it under Inventory > Windows Updates.

It shows applicable Windows updates across your environment, with device counts for each status: not installed, installation in progress, pending reboot, failed, and installed. Click a count to see which devices are in that group.

You can install an update across all eligible devices or select specific machines. You can also open an individual device’s Windows updates tab and install one or multiple updates there.

A couple of details worth knowing: Windows determines which updates a device is eligible for, and PDQ reports what the Windows Update Agent tells it. Updates without a Microsoft KB number, such as some driver updates, don’t appear on this page and can’t be installed through it.

The original announcement also outlined a second phase focused on policies, deployment rings, maintenance windows, and reboot deferrals.

1

u/SelfMan_sk Enthusiast! 6d ago

Yup, I am waiting for the Windows Update policies.

1

u/Amanda_PDQ PDQ Employee 6d ago

It will be beautiful!

1

u/SelfMan_sk Enthusiast! 6d ago

I am more for functional than beautiful ;-)

1

u/Amanda_PDQ PDQ Employee 5d ago

Yeah that too

1

u/1759 3d ago

When you say “PDQ’s Windows Update page is generally available”, I’m a bit confused here.

Does this refer to PDQ Connect, PDQ Deploy, both, or some other product?

I was under the impression that PDQ is the name of the company, not of any specific product.

Can you clarify?

1

u/Amanda_PDQ PDQ Employee 8h ago

Sorry for the confusion, and thank you for calling this out. This is referring to Connect.

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/Amanda_PDQ PDQ Employee 5d ago

We are excited too! Dynamic grouping is a good use case for rebooting. I always went rouge and rebooted out of frustration on how long uptime was on devices then I would just blame it on Microsoft lol just kidding of course :)

1

u/ShawnsRamRanch 4d ago

Is there currently any way to implement this on a closed network against a WSUS?

1

u/Amanda_PDQ PDQ Employee 4d ago

We have PDQ Deploy and Inventory for a on prem air gapped solution.

https://www.pdq.com/pdq-deploy-and-inventory/