1. PDQ Inventory — Endpoint Discovery, Visibility & Data Collection

This section highlights the configuration and management of endpoints using PDQ Inventory. It demonstrates the ability to add devices, troubleshoot discovery issues, interpret collected system data, and prepare endpoints for targeted deployment.

The workflow emphasizes accurate inventory tracking, validation of online/offline states, and readiness of endpoints for enterprise software management.

Objective

To demonstrate the ability to:

• Add endpoints to PDQ Inventory
• Troubleshoot discovery issues
• Validate online/offline status
• Run scans
• Interpret & Understand collected system data
• Prepare endpoints for targeted deployment.

Steps Taken:

1. Adding Endpoints via Active Directory

   I added the workstation via the PDQ Inventory console → navigated to Computers → right-clicked on the page → Add Computers → selected Active Directory - Browse by name → Computer OU, then I added it.

   

   <aside> 💡

   I already added the PCs before the screen snip, that's why I didn't move the PC

   </aside>

2. Troubleshooting Missing or Offline Endpoints

   • Issue encountered:

     1. Workstation added but not visible / unreachable from the server.
     2. Inventory scans failing

   • Troubleshooting Steps Taken:

     1. I checked the domain credentials configured if it was correct and I tried to ping the workstation, then I noticed I couldn’t, even though I could ping the server from my workstation.

     2. I checked the Windows Firewall on the workstation → inbound rules and I allowed these rules: ICMPv4, WMI, RPC & SMB (all domain & private).

        This allows PDQ Consoles to be able to communicate with domain-joined endpoints.

        By default, Windows client firewalls block inbound management traffic, so I had to allow them.

     3. I verified that the server could now ping the workstation and I re-ran inventory scan. Then, the workstation came online.

   <aside> 💡

   I also discovered that in cases like this that often say "The network path was not found", remote repair can be used to diagnose why (it tells you exactly which setting is broken).

   It performs a checkup on the target PC for three things:

   • ADMIN shares - This helps PDQ server see the hidden folders on the target PC
   • Windows firewall - To check if the firewall is blocking the ports PDQ needs (SMB/RPC/ICMPv4/WMI)
   • WMI/service health - To check if the WMI service is running on the target. </aside>