0 Replies Latest reply on Mar 21, 2014 11:00 AM by Thomas Scaccabarozzi

    How BMC Asset Management, manage licence software assurance? (for ex. MS)

    Thomas Scaccabarozzi
      Share:|

      Deal all, Inside asset management documentation (7.6.04) I cannot find anything about the best practice to manage licence software assurance. A software assurance allow to update a software to all software available version till service assurance expiration date.

      Someone that worked on Asset License Management (SAM) can explain me how he manage it?

       

      I try to explain better throught an example:

      First Year: [2014]

      Customer buy 100 licenses (software assurance) for Microsoft Project.

      Solution on Remedy:

      - Create a Software Contract "AAA" - Period of validity 2014-2015

      - Create a Certificate - Period of validity 2014 - 100

           Product Name = Microsoft Project 2013

           Product Name = Microsoft Project 2010

           Product Name = Microsoft Project 2007

       

      Second Year: [2015]

      Customer decide with MS to decrease licence to 80 licenses (software assurance) for Microsoft Project.

      Solution on Remedy:

      - Update the Software Contract "AAA" - Period of validity 2014-2015 with new Certificates

      With new software assurance 80 license can be updated to"Microsoft Project 2015" and 20 cannot upgrade and have to have max "Microsoft Project 2013" version.

      In your opinion which is the best way to manage the compliance software?

      Regards

      Thomas