/build/static/layout/Breadcrumb_cap_w.png

Software Licensing - multiple licenses, same product

Good Morning,

If I have multiple licenses that were bought at different times (with different license keys and purchase info), should they be entered under the same "License" asset? Or two separate licenses? Which way do you do it?

It seems that the License Compliance screen supports multiple license entries and calculates the total licenses (15), but other reports (Software_Catalog_-_License_Reconciliation_Report) sees it as two different licenses . 

Kace software licensing has changed a lot over the years, so I am unsure what the best practice is for these things now. 

Thanks,

0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: Hobbsy 6 years ago
Red Belt
1

Top Answer

You can do either, so adding in license information into your license asset works ok, but my preference, I can't claim it as Best practice , would be to create a fresh license Asset for every purchase and include the PO information and perhaps a date in the Licenses Asset Title i.e. Adobe Acrobat X full version - PO122345 - Dec 18.

It makes sense to do it this way as each asset can link back to the PO and provide a full audit track

Comments:
  • I agree with you. I just started doubting myself when I found there are some License Compliance reports that don't seem to play well with entering it as separate licenses. But that is ok, I will just use the license compliance page.

    -Thanks for your input, it is appreciated! - reneed33 6 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ