Perpetual License Reporting

Comments

7 comments

  • Colby Bouma

    You could store the license expiration date in a Custom Field and set up an Auto Report that shows you which ones are about to expire.




    1
    Comment actions Permalink
  • Brandon Bunnelle

    This is good stuff! I will definitely take this into consideration and give it a try.

    Thank you for taking the time to answer my question.

    0
    Comment actions Permalink
  • Stephen Valdinger

    Colby's option of a Custom variable for the expiration date is spot on. You can also store actual license information inside of Inventory as well. That way when you generate your auto report, which he beat me to showing you, you could have Computer Name, Software Name, License Key, Expiration Date as fields in the Report

    Here are a couple ways to do this:

    You have a couple of options for this. If you are dealing with a License key that is the same across many machines, you could edit each of those hosts in Inventory and include that information:

    Create New or Import from CSV

    I clicked on New and then entered this data into the line:

    If you were doing this to many machines, I would create a custom tool, and use something like nirsoft's produkey.exe which has a command line interface:

    http://www.nirsoft.net/utils/product_cd_key_viewer.html (scroll down, there are a TON of command line options).

     

    With that, you could dump a copy of produkey.exe on a file share and call it with Powershell, including your command-line options

    Copy-Item \\fileserver\share\produkey.exe C:\temp

    Start-Process C:\temp\produkey.exe -NoNewWindow -ArgumentList '/sjson C:\keys.json , '/sort "Product Name"' , '/sort "Product Key"' ...etc

    $keys = Get-Content C:\keys.json | ConvertFrom-Json

     

    Foreach($key in $keys){

    #send the info to inventory

    }

    *EDIT*

    Remove-Item C:\temp\keys.json -Force
    Remove-Item C:\temp\produkey.exe -Force

    Should probably clean up after myself :)

     

    1
    Comment actions Permalink
  • Brandon Bunnelle

    You both just solved my issue of keeping track of Perpetual Licenses. This is gravy!

    Another reason I'll keep throwing my money at PDQ.

    0
    Comment actions Permalink
  • Brandon Bunnelle

    COMMENT DELETED

    0
    Comment actions Permalink
  • Colby Bouma

    Which Type did you choose for the Custom Field? In my example I used Date.

    0
    Comment actions Permalink
  • Brandon Bunnelle

    I ended up using "Date", like you suggested, for the Custom Field and the report is doing pretty close to what I wanted it to do.

    I just have to get used to every Custom Field being on the report even if the date isn't pulled when ran.

    I deleted my last comment because i had a big "ah-ha! moment!

    Thank you for your assistance.

    0
    Comment actions Permalink

Please sign in to leave a comment.