1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Inventory
 

Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Product keys are not giving the true product name

Avatar
Charles Maes

We use various products of Microsoft Office, from Publisher to Home and Business. I'm trying to run a report on all versions of Office we have in each group. Unfortunately to my disappointment it seems that PDQ Inventory only reports a key as "Office" regardless of it's true product name. For example, standalone Publisher or Outlook is still reported as Office. Standard and Home and Business are lumped in there as well.

I can't tell the difference in the reporting. Is there anyway to get the report to differentiate the true product name? Thanks.

0

Comments

1 comment
Date Votes
  • Avatar
    Brigg Angus

    Hi Charlie,

    You can run a SQL report much like the example below, with the product names changed to fit what's in your applications report. Keep in mind that it's very difficult to pull product keys from specific installations due to a wide variety of variables (location in the registry, encryption used, etc.). In some cases, it's not possible at all, such as with the new Adobe products and volume licensed MS products that keep the key on a server, not on the local machines. Because of the difficulty in obtaining these keys, there are a few standalone products that exist solely for this purpose. Our products are used to fill a different role, with product keys being more of a convenience than a necessity to the overall goals and operation of the programs.

    If we remove the product key variable, we can begin to differentiate between Office versions and editions, standalone Office products, and just about any other installed software through filtering (either Dynamic Collections or Reports). The only difficulty is tying specific products to specific product keys. 

    As for creating custom reports/collections to show the relevant information you require, we cover that much better than I can here in the form of colorful, very informative videos:

    Advanced Collection and Report Filtering in PDQ Inventory

    Advanced Collections and Report Filters - Part II

    And here is the example report (change to meet your needs):

    select
    Computers.Name as "Computer Name",
    Applications.Name,
    ProductKeys.Key
    from Computers
    join Applications using (ComputerId)
    join ProductKeys using (ComputerId)
    where <ComputerFilter>
    and Applications.Name like '%Microsoft%Office%2013%'
    and ProductKeys.Vendor = 'Microsoft'
    and ProductKeys.Product = 'Office'
    and ProductKeys.Version = '2013'
    union
    select
    Computers.Name as "Computer Name",
    Applications.Name,
    ProductKeys.Key
    from Computers
    join Applications using (ComputerId)
    join ProductKeys using (ComputerId)
    where <ComputerFilter>
    and Applications.Name like '%Microsoft%Office%2010%'
    and ProductKeys.Vendor = 'Microsoft'
    and ProductKeys.Product = 'Office'
    and ProductKeys.Version = '2010'
    union
    select
    Computers.Name as "Computer Name",
    Applications.Name,
    ProductKeys.Key
    from Computers
    join Applications using (ComputerId)
    join ProductKeys using (ComputerId)
    where <ComputerFilter>
    and Applications.Name like '%Microsoft%Visio%2010%'
    and ProductKeys.Vendor = 'Microsoft'
    and ProductKeys.Product = 'Visio'
    and ProductKeys.Version = '2010'
    union
    select
    Computers.Name as "Computer Name",
    Applications.Name,
    ProductKeys.Key
    from Computers
    join Applications using (ComputerId)
    join ProductKeys using (ComputerId)
    where <ComputerFilter>
    and Applications.Name like '%Microsoft%Visio%2013%'
    and ProductKeys.Vendor = 'Microsoft'
    and ProductKeys.Product = 'Visio'
    and ProductKeys.Version = '2013'

    0