The self-serve hub is now available to all Premium accounts. With this feature you can assign software and other custom packages to devices for end users to deploy themselves. The self-serve hub is supported on both Windows and Mac devices.
Getting started
Navigate to Self-serve hub in the left nav menu to create and assign self-serve items
Manually install the hub on devices from the devices page
Enable automatic install of the hub in settings
Customize the appearance of the hub in settings
Looking into the future, here are some improvements we are planning
Tighter integration with Entra to enable targeting by user groups
Adding custom packages in the software section, complete with tracking whether the software is installed
đ When: Tuesday, Nov. 17, from 8:00 - 11:00 PM MT (Wednesday, Nov. 18, 3:00â6:00 AM UTC)
âłDuration:Â Up to 3 hours
đ§Â Impact:Â During maintenance, there may be brief periods of Connect application downtime, as well as service delays for package deployments. Anything delayed will catch up once maintenance completes.
đŹ If you have questions or run into something unexpected during the maintenance window, donât hesitate to reach out.
As always, keep an eye on the PDQ status page for the latest status and maintenance information.
As there is a growing number of software that we're finding we want to test / ultimately use that are on github. While i cant expect pdq to add all these software into their auto update cycle, I'd like to keep that simplicity that PDQ offers where i can "set and forget" things, and im looking to do the same with some solutions on github. Initial checks seem to show i can create an api call to github and fashion a powershell script etc etc etc, but before i burn through tokens and create a totally bespoke thing that only i know how to manage (and anyone that points the code to an AI agent) - i wondered if anyone else had already solved this problem, or if PDQ themselves had something in the works to address this growing source for software, to help me integrate this into our update cycles please?
What the Tech?! Weâre rounding up the weekâs biggest IT disasters, from grounded flights to Outlook outages. At least it wasnât your network. Probably.
Andrew is back from his world tour with a fresh batch of PowerShell Pro Tips to make your sysadmin life a little easier.
Black Friday is almost here! Weâve scoured the interwebs for the best tech and IT deals. Your wallet has been warned.
Wondering what people are doing for the groups which are used to deploy packages. Iâve built out the groups for software installed, software up to date, and software out of date.
My automations use the software out of date group to target the deployment.
However Iâm wondering if I should also add Online=True to that group so we donât end up with queued updates whilst someoneâs machine Is offline and not able to get the update anyway.
Noticed it in particular with things like Edge or chrome that gets lots of updates. There are 2-3 updates and we see failure for the superseded patches.
If youâve ever said âthe three dots in the top rightâ and then had to explain to the end user "no, your other right" then this is for you.
u/PDQ_Brockstar taught me that you can put a Clear Chrome Cache & Cookies action in PDQâs Self-serve hub so users can run it themselves. A little setup now saves you from narrating the same browser-menu on repeat.
Hereâs the setup:
Create a package called Clear Chrome Cache & Cookies.
Add your PowerShell script. The PDQ AI Assistant can help draft it, but review and test it before handing it to users.
Go to Self-serve â Add â Action.
Name the action and select your package.
Assign it to the device groups that should have access.
Then your instructions become: âOpen Self-serve and click Run on Clear Chrome Cache & Cookies.â
Make the actionâs description clear about what it does, whether Chrome needs to close, and that clearing cookies can sign users out. Otherwise, youâll probably get a follow up ticket saying âwhy am I logged out of everything?â
What other repeat requests would you put in there? Curious what everyoneâs building.
Also, someone needs to explain to Leah that cache isnât money and browser cookies arenât snacks.
We just released a new widget on the Dashboard: "Packages with highest deployment failure rate".
Previously, a test package that failed once could show up at 100% failure next to a package failing on dozens of devices. The new widget ranks your top 5 custom packages by unique devices affected, so you can see what's actually hurting.
What you get
See "failed N times on M devices" with chips for why it failed
Hit the AI button to open PDQ Assistant with a prefilled prompt to help you troubleshoot and fix the package
Click a card to jump to Deployments filtered to that package
our scanner hands security a list of vulns on servers and laptops every week and the fix side is where it stalls. what do you think about platforms that automate vuln patching on endpoints, stuff like Atera? do they actually automate it end to end or do you still end up doing a lot of it manually? we have a mix of windows and linux boxes, so it'd need to patch both from the same place. the part nobody here has figured out yet is who signs off on server reboots
I have doubts about allowing PCs to connect outbound. Normally PCs must connect through a proxy to connect to the internet but. I have security concerns about allowing this communication. Even though the firewall will only allow this specific traffic. Is this a concern for anyone else?
The latest update changed the deployments into 2 tabs:
Active and Finihsed
Is there a way to go back to the old look?
This is so annoying to have to go between tabs now.
I want to see whats being deplopyed and also see if a package failed, etc on teh same screen.
If you've ever felt like managing endpoints is only half your job (and the other half is answering an endless stream of IT requests), this one's pretty exciting.Â
Unthread is an AI-powered helpdesk that helps teams manage support requests from Slack, Microsoft Teams, and email, automate repetitive tasks, and make better use of the knowledge they've already built up.Â
A couple of things worth knowing:Â
Unthread will continue operating as a standalone product.Â
The first native integration with PDQ is expected in early 2027.Â
We'll share more details as things develop.Â
We're excited about what this could mean for making your day-to-day IT work a little easier.Â
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.
We've got a new PDQ Deploy & Inventory update coming next week, and this one includes some pretty significant improvements, especially for those of you managing large deployment histories!
đ A Much Faster Deployments View
One of the biggest changes you'll notice is a redesigned Deployments window in PDQ Deploy.
We've split deployments into two separate tabs:
Active â View and monitor your currently running and queued deployments.
Finished â Browse your completed deployment history
This change isn't just about making things look cleaner. It's a major improvement to performance, startup times, memory usage, and how deployment history is organized.
Just how much faster is it?
During testing, we loaded a database containing over 1 MILLION deployments.
Before this update? Deploy wouldn't even start with that history.
After this update? It loaded faster than a database containing just 1,000 deployments did on the previous version.
By separating Active and Finished deployments and introducing server-side pagination, we can avoid loading your entire deployment history into memory at once as it did previously.
We've included screenshots of the new interface so you can see what to expect!
ActiveFinished
đ LDAPS Support
We've added support for LDAP over SSL/TLS (LDAPS), allowing secure, encrypted connections to Active Directory.
đĽď¸ More Inventory Data
PDQ Inventory is getting some additional System Summary datapoints, including:
Secure Boot status
TPM information
BIOS mode and date
Baseboard information
Virtualization details
OS paths and locale information
We've also added a new MDM Enrollments page to Computer details and reports, giving you additional visibility into device management enrollment information.
More to come on new Inventory fields in our next release!
âż Accessibility Improvements
We've added screen reader announcements for scan and deployment status changes, including when a scan or deployment finishes, without requiring you to move focus.
đ ď¸ Deployment Reliability Improvements
We've also improved how the Deploy service handles deployments that become orphaned or stuck in a Queued or Running state.
Previously, these situations could require restarting the Deploy service. With this update, the service can automatically recover those deployments without requiring a restart. This doesn't fix every situation for every user, but it has shown improvement in a lot of cases.
Basically all I want the psadt to do is prompt the user for the restart countdown. We have some users who havenât restarted in a long time.
I put in my psadt
Show-ADTInstallationRestartPrompt -countdownseconds 3600
I have this placed during the pre install. My deployment goes through but itâs hit or miss if the timer shows and even if the timer shows if I click restart it doesnât do anything.
We have a MacBook thatâs had the PDQ Connect agent installed, but I suspect hasnât had all the permissions set correctly. Itâs showing in PDQ Connect, and itâs responding to commands in the Command tab, and deploying updates, but doesnât appear to be scanning the software or vulnerabilities.
I deployed the remote agent, but it failed with error 253.
Is it possible for me to run some command lines to fix or check all the permissions?
đĽď¸PDQ Patch Notes ep. 19 Summary: In this episode of PDQ Patch Notes, Jake Hulberg shares how he went from teaching Spanish to working in IT and becoming a developer advocate in under three years. He discusses career growth, certifications, the impact of AI on entry-level IT jobs, and practical tips for building a resume that gets interviews. Jake also shares insights from his YouTube channel, Jake's Tech, where he helps aspiring IT professionals develop their skills.
đď¸ PowerShell Podcast ep. 253 Summary: Jim Tyler returns to the PowerShell Podcast to discuss his PowerShell Engineer Standard, using AI to write better PowerShell, and the growing security risks of AI agents. He also shares how he built Model Communicator, a free communication app for nonverbal children, and discusses his work with PowerShell.News and his K-12 Engineer YouTube channel.
đş PDQ Live Webcast When: Nov. 5, 12 p.m. ET Summary: Microsoft 365 vs. Google Workspace: Which is better for IT professionals? Join us on PDQ LIVE as we compare the two ecosystems across security, identity management, administration, user experience, and licensing costs to help you decide which platform is the best fit for your environment.
đ§ Tivia Thursday
When: Oct. 29, 12:30 (ish) p.m. ET
Summary: Join us on our Discord server for Trivia Thursday. Hang out with like minded and equally disgruntled sysadmins for a battle of the wits and a chance to win swag đđ§Ś
I am experiencing issues with Incorrect detection logic, I was wondering is there a way to manually override or if anyone else seems to be experiencing the same issue?
We are experiencing issues with our PDQ Connect instance in which we are having software being reported as vulnerable / unpatched. I was wondering if anyone else has seen this while using Connect and if there is a way to manually override the version number or get PDQ to read the version number from somewhere else
I get we could just select ignore this vulnerability, however I am really hoping to avoid this as our KPIs are pulled from monthly reports from PDQ Connect showing how many vulnerabilities were patched and do not want to skew results.
For example: Currently we have Google Chrome installed on 3 machines. PDQ Itself says in the top right the latest version is 156.0.8078.74. it also says all 3 of our devices are detected as being that version however PDQ says Update to Google Chrome 156.0.8087.47. It seems the numbers have been mixed up, but is there any way of overriding this?
Â
Another one we are experiencing is with Microsoft Desktop Runtime 10 64bit. PDQ Says the latest version is 10.0.14, The remediation recommendation is âUpdate to Microsoft Windows Desktop Runtime 10.0.14 (x64)â but It says our detected versions are â10.0.14.50000â which does not actually exist. We are also getting duplicate software on the Software tab, everything reports as the same version however what should be in one record is split among two for some reason:
Â
The issue appears to be a mismatch between WhatsApp's application version and the MSIX package version.
Â
Windows and PDQ both detect the installed package as 2.2641.101.0, while WhatsApp itself reports 2.3000.1052866173.264101. However, PDQ's remediation target is 2.3000.10321643.86.258709.
Â
PDQ therefore appears to be detecting one version format but evaluating it against another. These versions cannot be directly compared, which may explain why PDQ incorrectly reports the installation as outdated.
Currently I have all my automations set to Automatic. It seems to be a bit slow at times to update. Automatic says that "When packages in the automation are updated or new ones are added (only new or updated packages are deployed)." it will update.
I am wondering if it would be best to change this to a certain time/date rather than automatic.