🤘 61 reputation



Joined: 4/24/2018

Last seen: Thursday at 10:33 PM

  • You have to left join the CustomComputerValues table, and it can get a little tricky depending on exactly what you want your report to do. Here are a couple of examples:



  • Thank you for your request. We have an internal feature request ticket for this, but I have no ETA on when/if it will be implemented.

  • Thank you for reporting this. I have confirmed that it is not currently possible to use variables in number fields. I have submitted an internal bug ticket. I have no ETA on when/if this will be changed.

  • Thank you for the feedback. This is something we are looking into, but I have no ETA on when/if it will happen.

  • If you are using Inventory 16.6, it has some potential integration issues. Please reach out to support@pdq.com.

  • That is a bug in that will be fixed in

  • Can you send screenshots of the issue you're having and exports of the problematic tools to support@pdq.com please? We were able to reproduce part of the issue, but not all of it.

  • I believe that is a bug in that is fixed in the latest Customer Build. Contact support@pdq.com to request that.

  • It looks like you found a bug! I have opened an internal bug ticket for this. I have no ETA on when this will be fixed.

  • Sorry, we missed a step when publishing these last week and they didn't go live. If you refresh your console they should be there now.

  • I'm not familiar with what you can do from ServiceNow, but if it can run scripts you can call PDQDeploy.exe Deploy -Package <Package name> -Targets <Comma separated list of computer names>.

  • Not really. The closest thing I can think of is Auto Reports. Technically you could read the database directly, but that can cause issues, so I don't recommend it.

  • I think as long as you use a name that we never use, you should be fine. I don't think we erase extra tables during updates.

  • Please post a screenshot of the error you're getting and export your package to XML (Right-click --> Export). You can paste the XML into your reply as code or upload it to something like pastebin or gist.github.com.

  • I talked to a coworker to clarify what I was trying to remember. It does reconfigure all applications (event ID 1035 in the Application log), but it's probably fine. There's a possibility of it messing with some timestamps and some poorly written applications may misbehave after being reconfigured. We call MsiExec with a GUID because it has fewer side effects.

  • It's generally not a good idea to use WMIC to uninstall programs like that. I'm having trouble finding the link I'm thinking of, but if I recall correctly WMIC reconfigures all applications when you do this. I recommend looking at our Uninstall packages in the Package Library. We enumerate the Registry to look for the GUID and pass that to MsiExec.

  • Thank you for reporting this! I have opened an internal bug ticket.

  • Yeah, sorry about that. This is a bug we're investigating. You found our recommended workaround of deleting/renaming the log.db file.

  • This is a known bug we are investigating. Here's what you can try:

    1. Stop the PDQ Inventory service.
    2. Rename or move "log.db" and "InboundMessages.db" in "C:\ProgramData\Admin Arsenal\PDQ Inventory".
    3. Attempt to launch PDQ Inventory again.

    If that doesn't work, please contact support@pdq.com.