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.

Feature Request: Product Key & Custom Field Pre-Defined Values

Avatar
Andrew Kriger

It would be nice to be able to create master Product Keys or Custom Fields and have pre-defined values for them.

Eg. For a Product Key when you click in Vendor you get a list of Vendors you have defined. Once selecting a vendor you will get products you've defined to that vendor, and available product keys for the selected Product.

Same could be done with custom fields.

We have quite a few Volume Licenses, and we have to manually type them in on a computers Product Key to have our dynamic groups in PDQ inventory pick them up for that computer so that PDQ Deploy knows what key to install with a particular program.

0

Comments

1 comment
Date Votes
  • Avatar
    Christian Bacher

    You can use custom variables for this unter PDQ Deploy -> Options -> Variables:

    Example:

    I have 3 different Office 2016 Keys for 3 sites, now i set up 3 custom variables:

    @(01_Office_2016PP): xxxx-xxxx-xxxx-xxxx-xxx

    @(02_Office_2016PP): yyyy-yyyy-yyyy-yyyy-yyyy

    @(03_Office_2016PP): zzzz-zzzz-zzzz-zzzz

    Now i install Office 2016 and after that i start the pkey activation step:

    Office 2016 Pro Plus activation site A: (cmd deploy Step with condition = Is a Member of collection site A):

    cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /inpkey:@(01_Office_2016PP)

    cscript "c:\program files\microsoft office\office16\ospp.vbs" /act

    Office 2016 Pro Plus activation site B: (cmd deploy Step with condition = Is a Member of collection site B):

    cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /inpkey:@(02_Office_2016PP)

    cscript "c:\program files\microsoft office\office16\ospp.vbs" /act

    Office 2016 Pro Plus activation site C: (cmd deploy Step with condition = Is a Member of collection site C):

    cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /inpkey:@(03_Office_2016PP)

    cscript "c:\program files\microsoft office\office16\ospp.vbs" /act

    I don't need a extra deploy for each site, setting up the custom variables and the conditions in the steps helping me to use only one deployment for all sites. Fire and forgot.

    Greetings

    0