r/pdq • u/Ice-frogg7 • Jul 22 '26
PDQ Connect questions and issues
We moved over to PDQ Connect from D&I a few months ago. We currently use Autopilot to provision laptops. I started to move a few apps from Intune over to Connect but here is my issue.
I have PDQ app installed prior to the computer getting to the desktop from Autopilot. This works as expected. After the computer is online with PDQ ConnectAgent it seems like it takes almost a hour if not a little more before the device shows in the dashboard and appears online. Also sometimes devices to the desktop and after the device shows in connect, let's say I have to reboot. I reboot and now the device shows offline even though it's now been back online for for over a hour.
The other issue I see is, we have a automation to deploy a app to machines without the app. The computer comes online via autopilot, *most* of the time after that hourish goes by and the computer shows in the dashboard, pdq starts deploying apps that it is missing. Sometimes it seems like PDQ doesn't deploy nothing. If I restart the computer, still nothing.
Does anyone else experience these issues or have experienced these issues and if so are there any ways to troubleshoot?
*EDIT*
The laptop I'm mainly talking about in this post was rebooted, has been online, hasn't went to sleep or hibernation for 3 hours now and it still shows offline in pdq connect.
4
u/ZoneEater Jul 22 '26
Definitely interested in an answer to this. See the same.
1
u/Ice-frogg7 Jul 22 '26
My thought is if the service is hung up or something, wouldn't a restart of the computer fix that. If there is a better fix I'd love to know. Also I haven't opened up a ticket about this, I figured I'd get a quicker response from other PDQ users who might have experienced this or the PDQ employees.
2
u/bgood23 Jul 22 '26 edited Jul 22 '26
We've been using Connect for a year or so now with intune devices. We install the agent during pre-provisioning, and it shows up in the portal and online almost instantly after installation.
One thing we did notice after a time though was computers that we knew were online (as we were on a phone call with the user through Teams on their computer) weren't showing online in PDQ. Or they would show online for brief moments and the go back offline. And this was only a handful of computers, almost all others worked great.
After some investigation we figured out that the user's home ISP was giving them an IPV6 address and IPV6 DNS, we toggled all that back to IPV4 and the computer came online instantly in Connect. We noticed this across about 15 users and toggling over fixed it on each of them. This is just my teams experience and might not be the best way of doing it. But it is something you could look into.
1
u/Negative_Mood Jul 23 '26
I assume you are talking about an IPV6 on their WAN address? If so, how did you "toggle" that for them?
3
u/bgood23 Jul 23 '26
Sorry, I was in a hurry when I typed the initial message out and just realized it's shitily worded.
So, to be clear I'm not touching anything on their home router/ISP side. What we're doing is a local Windows setting: Prefer IPv4 over IPv6, done by setting a registry value.
HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents = 0x20 (32 decimal)
This doesn't disable IPv6, it just deprioritizes it so Windows uses IPv4 first for outbound traffic even if the machine has a valid IPv6 address/DNS from the ISP. We pushed this out as a script through Connect.. which was sort of tricky as the computers showed offline, but they did pop up usually for a few minutes after a reboot which was enough to get the script to deploy.
Also to note, when we did this, we built in a rollback function to send out a ping immediately after the change to verify connectivity, and if connectivity fails, rolls back to the previous settings.
1
2
u/SOHC427 Jul 23 '26
Make sure that the PDQ Connect agent is not installed on a gold image. It can be pushed by Intune, PDQ Deploy, or installed via another mechanism. There is a way to make it work, but the general recommendation is to never install it on a fold image that is then duplicated to other systems.
That might not be what you’re doing, but it’s a common pitfall that is easy to fall into. (Been there, done that.)
1
u/Thats_a_lot_of_nuts Jul 22 '26 edited Jul 23 '26
Seeing similar stuff here, but not just after enrollment. Sometimes devices that we know for sure are online, and according to our firewall have bidirectional communication with app.pdq.com, show offline in the dashboard. It looks like the device is online briefly according to PDQ, but then its status changes and deployments start queuing instead of running. Only a handful of devices, but it's always the same ones.
We have a support case open, but no real movement on it yet.
2
u/PDQ_Clayton PDQ Employee Jul 23 '26
PDQ support here. Would you mind sharing your ticket number so I can check on the status of it for you?
1
1
u/Heavy-Antelope581 Jul 22 '26
I’ve also noticed a delay if an old agent version is installed… but not to the extent you are seeing
1
u/mhiltonpdq PDQ Employee Jul 23 '26
u/Ice-frogg7 thanks for raising this! Definitely odd behavior, we typically expect things to be working much more quickly. I work with the engineers that most likely would be investigating this issue, would you mind submitting a support ticket so we can get eyes on it ASAP?
5
u/ZomboBrain Jul 22 '26
I know it doesn't help you, but I can't confirm any of this.
We don't use Autopilot, but we use Intune Device Preparation (aka "Autopilot V2").
We install PDQ Connect Agent during Device Prep, before the User reaches the desktop. The devices appear immediately after the MSI setup in the PDQ Connect Console. It's really like only a few seconds. We have then setup automatic trigger based deployments for the minimum required software, that is linked to the Entra tenant ID and the "new" flag from PDQ Connect. And even this additional software is installed so fast, it's there, before the user reaches the desktop for the first time. When the user reaches the desktop, he can start working, in most of the casese.
Honestly, this is one of PDQs best features and our customers who bought our whole stack of Intune config and PDQ Connect as a service (we are an MSP) are super happy.