Community Forums
Results 1 to 3 of 3

Thread: Retiring Licenses

  1. #1
    Join Date
    Jul 2015
    Posts
    2

    Retiring Licenses

    What's the 'best practice" for retiring licenses so they don't show as Under-Consumed. I've been changing the status of the licenses to RETIRED and changing the compliance status to NOT TRACKED but the license shows as Under-Consumed since its not installed anywhere. I don't want to DELETE the license and lose the historical tracking but also don't want to assign consumption where there is none. Suggestions?

  2. #2
    Join Date
    May 2014
    Posts
    8
    Hi Jrobs3,

    I think I understand what you're asking, but I want to turn it upside down and ask why it is in your favor to retire licenses...

    If compliance is your key focus, I think retiring licenses and having only keeping your most current offerings will simplify the picture. You will likely pay for more than you need, but things will be simple and straightforward. However, if optimization is your key focus, it is an advantage to have all the older licenses in the system - and still consuming where they apply - so you are not re-buying licenses at current rates when you have perfectly good ones on the shelf already.

    I can understand retiring applications, devices, etc. through decommissions or upgrades. But if you have perpetual licenses that do match existing installations, even if those licenses are somewhat under-consumed, do you really want to remove them from the pool of software assets? Maybe it would be better to find a way to call them out in reports, like adding a suffix to the license name, e.g., "Microsoft Visio 2003 [RETIRED]"?

    Regards,
    Matt

  3. #3
    Join Date
    Jul 2015
    Posts
    2
    Thanks, Matt. I'm specifically referring to old licenses/apps with no consumption due to upgrade, etc...Currently my Dashboard is indicating we are $7.6M under consumed. Not a good figure for the CIO to see. Yes, I can explain it away but that number should not be there. In fact, I logged a Support Case and evidently it's a known issue (bug) that is corrected in SP3. Thanks again for your response.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •