🤘 42 reputation



Joined: 4/24/2018

Last seen: Tuesday at 9:20 PM

  • You can create an Auto Report that saves the report to a CSV file. https://documentation.pdq.com/PDQInventory/

  • To request Customer Builds please contact support@pdq.com

  • Yes, unfortunately ProductKeyChannel does not exist in Windows 7. You could do "SELECT *", but it would be slower and take up more space in your database.

  • Are you trying to deploy the Microsoft .NET Framework 4.7.2 package? That package has Conditions so it will only deploy to Windows 7, 8.1, 10 (1607, 1703, and 1709), Server 2008 R2, 2012, 2012 R2, and 2016.

  • Probably. Start with this blog and change the registry key for Mode to Server. However, you'll probably run into credentials issues. I'll look into this more when I can.

  • Did you use the WMI query from my post or the one from the KB I linked to? ProductKeyChannel will only be present if you used the query from my post.

  • @TudorL

    That's a bug in You have to click the dropdown in the Column field and select ProductKeyChannel. Sorry I didn't mention this before, I'm using the Inventory 17 beta and this is fixed in that version.

    enter image description here

  • Is there any way to unlock this without having to ask them to close PDQ Inventory?

    The only way I know of is to restart the background service of the Server.

    How does it get locked in the first place?

    It should only lock if someone changes something in Preferences, but there have been bugs where it triggers if Dave sneezes in the break room at 3:29 PM on a Wednesday. If you have a sneeze-prone Dave, open a ticket with support@pdq.com because it potentially could already be fixed in a Customer Build.

  • Yep, that's on our end. Big hammers have been distributed to our devs, so hopefully it will be resolved soon! https://support.pdq.com/knowledge-base/1828

  • For computers that haven't been scanned you'll have to use the manual config file, which unfortunately is not as simple to push: https://documentation.pdq.com/PDQInventory/

  • Oops, you never said Inventory 😄

    Deploy Clients should be able to connect across domains. I suggest contacting support@pdq.com.

  • Which version of Inventory are you using? There was a bug where Clients couldn't connect if the Server wasn't set to "Listen on all IP addresses". This is fixed in 17 Beta 4 and the latest Customer Build of 16.5.

  • Yes. https://documentation.pdq.com/PDQDeploy/

  • This shouldn't matter, but try renaming "CitrixReceiver 4.9 LTSR.exe" to something without spaces.

  • Try this modified version of this WMI query:

    SELECT LicenseStatus, ProductKeyChannel FROM SoftwareLicensingProduct WHERE Name LIKE '%Windows%' AND PartialProductKey IS NOT NULL

    Now create a Basic Report with that ProductKeyChannel field:
    enter image description here

    Group by the ProductKeyChannel field to see which values are present:
    enter image description here
    enter image description here

    The meaning of the values for LicenseStatus are in this forum post.

  • That should be fine. Just make sure to set the permissions so only your service account(s) can access it.

    Inventory automatically updates all of its Agents. You don't need to push updates to them. Also, those files are always the latest version, so you are correct that you don't need to update the Deploy package.

    Also, I recently wrote a blog post that explains my choices further: https://www.pdq.com/blog/installing-the-agent-with-pdq-deploy/

  • Can you post a screenshot of your Install step please?

  • Unfortunately, if the target hasn't been scanned you do have to use the manually generated config file.

  • You are correct, there is no native way to do this. It's possible with PowerShell, but pretty messy.

  • Unfortunately no. Those collections are not configurable. However, you can make your own Dynamic Collections with "Computer | AD Parent Path | Starts With | Your OU Name Here".