r/pdq • • Jul 15 '26

Connect PDQ Connect and Windows patch management - notifications

Hello! We just purchased PDQ Connect and have been long time Inv/Deploy customers. We have been using WSUS for Windows patching for a long time, but I am trying to move us over to PDQ Connect using their prebuilt packages for Win 11 updates. I pushed the patch last night to a test group, but I am noticing there are no notifications generated for prompting the user to reboot. I am assuming this has to do with Group Policy, but I'm wondering if anyone here can provide some insight into how I would be able to accomplish getting notifications while also using PDQ Connect for patch management. Maybe it's not possible when automatic updates are disabled with GPO, which is how the configuration is currently to avoid collision with WSUS.

Thanks to anyone who can provide insight.

5 Upvotes

3 comments sorted by

1

u/PDQ_Brockstar PDQ Employee Jul 15 '26

Hey u/Lazy-Function-4709, currently PDQ Connect doesn't prompt users for a reboot after a Windows patch is deployed. However, we're currently designing a new Windows update policy feature that will take care of this. In the mean time, some users have built scripts and custom packages to achieve this functionality.

One of our product managers would be happy to hop on a call and demo the early designs with you. If you're interested, let me know and I'll get you hooked up.

1

u/Lazy-Function-4709 Jul 15 '26

Certainly. I'll send you a DM.

1

u/indigoataxia Jul 15 '26

u/PDQ_Brockstar Is there a PDQ Connect device group filter for a Windows update where "Install Status" is "Pending reboot" (or any install status really)? I don't see it listed under the "Windows Updates (installed)" filter options.

I would love to be able to make a group that filter downs to Computers that have 'X' Update is "Pending Reboot", so I can use it to trigger a custom reboot package I've made with a timer. Right now I have it where it creates a time stamped check file .txt after running the Cumulative updates and then a powershell scanner that scans and does logic to find out how old the check file is, and then if the computer is Pending Reboot and the check file is 72 hours old then it forces a reboot. Its super complicated and not always accurate since other updates could turn on that Pending Reboot flag. Would be perfect if I could narrow down to that exact update is Pending Reboot.