PDQ has shipped a major update to its cloud-based endpoint management platform, PDQ Connect, delivering three features that admins have been requesting since the product’s launch: a Windows Update dashboard, a native macOS Package Library, and the ability to trigger device reboots directly from the cloud console. The release, announced this week, significantly narrows the gap between the cloud service and the company’s on-premises stalwarts, PDQ Deploy and PDQ Inventory, while turning Connect into a viable single-pane solution for mixed Windows and Mac fleets.

What Arrived in the Update

The update lands in three distinct pieces, each attacking a long-standing pain point.

Windows Update Dashboard

Until now, overseeing Windows patch status in PDQ Connect meant leaning on third-party tools or waiting for the on-premises Inventory product. That changes with a new dashboard that surfaces which updates are installed, which are missing, and which require a reboot to finish applying. Admins get a unified view across all connected Windows endpoints—servers, workstations, laptops—without having to remote into devices or comb through logs. The dashboard lets you filter by update category (security, critical, feature packs) and status, then push missing updates to selected machines or groups on demand. For organizations that have been patching blind, this is the headline feature.

macOS Package Library

PDQ Connect previously offered basic Mac management—inventory data, remote command execution, and the ability to run scripts. But deploying applications meant building your own packages from scratch. The new Package Library port brings the same convenience that Windows admins enjoy: a curated repository of ready-to-deploy packages for common macOS software, including browsers, productivity tools, and creative apps. The library supports both .PKG and .APP formats, and admins can upload their own packages as well. Deployment uses the existing PDQ Connect agent on the Mac, which now handles package installation, version checks, and post-install actions. The update also extends smart scheduling and approval workflows to Mac packages, so you can roll out updates incrementally just as with Windows.

Direct Reboots

Rebooting endpoints after installing patches or software has always been a friction point, particularly for remote users who may not be logged in. The new direct reboot capability lets admins initiate a restart from the PDQ Connect console, with several safeguards: you can prompt the user with a customizable message and a countdown, force a reboot after a set timer, or schedule it for off-hours. Reboots can be targeted at individual devices, groups, or all devices that show a pending reboot status. This feature works on both Windows and macOS endpoints, closing the loop on installations that require a restart to complete.

What This Means for You: Practical Impact by Role

For IT Administrators in Hybrid Shops

If you’re managing a mix of Windows laptops, desktops, and a growing Mac fleet, this update might let you retire one or two supplementary tools. Windows update visibility was the biggest missing piece—without it, many admins kept a PDQ Inventory server running on-premises just to track patches, or they cobbled together scripts with Windows Update for Business reports. Now you can see and act on update status within the same console you use for inventory and software deployment. For Macs, the library means you spend less time packaging common apps and more time on higher-value work. Direct reboots remove the awkward phone call or email to a remote worker asking them to restart now, please.

For Organizations Using PDQ Deploy & Inventory

This release doesn’t kill the on-premises products, but it does make the cloud option a lot more attractive, especially if you have devices that rarely touch the corporate network. Feature parity isn’t complete—PDQ Inventory still offers richer reporting and custom scans—but for many small and midsize businesses, Connect now covers the 80% case. If you’ve been holding off on the cloud because of missing update visibility or Mac support, now is the time to reassess.

For MSPs and Internal Service Desks

Direct reboots with user prompts give you a professional way to enforce restarts without disrupting work. Pair that with the enhanced patching, and you can close tickets faster. The cross-platform nature means a single workflow for both Windows and Mac, cutting training time for new technicians.

For Home Users

PDQ Connect is a commercial product; the update has no direct impact on personal devices. However, the concepts it employs—central update visibility, curated package libraries, polite reboot nudges—are features many Windows users wish Microsoft would build into Windows Update itself.

How We Got Here

PDQ has been a darling of the Windows sysadmin world for over a decade, starting with PDQ Deploy in 2008 and later PDQ Inventory. The software gave admins a simple, scriptable way to push out applications and collect hardware/software data across a network. But the model was strictly on-premises, reliant on Active Directory and a LAN. When the pandemic forced millions of employees home, VPNs and cloud-first management became a requirement, and PDQ responded with PDQ Connect in 2022.

Connect was a ground-up cloud service with an agent, not a re-skinned Deploy. Early versions could install software and report basic inventory, but they lacked the deep Windows Update integration and the Package Library that made the on-premises products so powerful. Mac support was present only in a limited, script-based form. Since then, PDQ has been steadily backfilling features. A Package Library for Windows arrived in PDQ Connect in early 2023; last year brought improved scripting and role-based access controls. This latest update—adding Windows Update visibility, the Mac library, and direct reboots—feels like the moment Connect grows into a legitimate dual-platform management platform, not just a cloud adjunct.

What to Do Now: Actionable Steps

If you’re already a PDQ Connect subscriber, the new features should be live in your console; you may need to update your agents to the latest version. Here’s how to get started:

  • Windows Update dashboard: Navigate to the new “Windows Updates” section from the main navigation pane. The system will begin gathering update status from agents. Enable automatic scanning if not on by default, and configure notification thresholds for critical missing patches.
  • Mac Package Library: Browse the library in the Packages section—switch to the macOS tab. Deploy a test package to a sandbox Mac to verify agent compatibility. If you have existing custom packages, you can upload them directly.
  • Direct reboots: In the device details panel, you’ll see a new “Reboot” action. Establish a company policy around reboot prompts (e.g., 2-hour countdown with a message). The feature respects maintenance windows, so set those up if you haven’t already. Warn users before enforcing reboot policies to avoid data-loss complaints.

If you’re evaluating a new endpoint management tool, and the cloud is non-negotiable, PDQ Connect’s latest update moves it up the list. It’s worth comparing against NinjaOne, Syncro, or even Microsoft Intune, depending on your tech stack. PDQ Connect’s per-endpoint pricing remains unchanged with this release, but check the website for the latest tiers.

What’s Next for PDQ Connect

With this update, PDQ has addressed the three loudest feature requests. Looking ahead, the company has hinted at deeper integration with identity providers for device enrollment and possibly Linux support to match the cross-platform aspirations. The endpoint management market is in a consolidation phase, and PDQ’s challenge will be to keep pace without bloating the product. For now, Windows and Mac admins have a significantly stronger tool in their hands.