License upgrade and downgrade with the legacy Software Asset Management plugin
Summarize
Summary of License Upgrade and Downgrade with the Legacy Software Asset Management Plugin
The legacy Software Asset Management plugin enables ServiceNow customers to manage software license upgrades and downgrades effectively. This functionality is essential for reconciling software licenses and ensuring compliance with licensing agreements.
Show less
Key Features
- Downgrading Licenses: Customers can purchase a license for a newer version while using an earlier version. This is particularly useful as downgrading is more common than upgrading.
- Upgrade Path: The system creates a software model record for unlicensed versions defined as downgrade children, linking them to their licensed upgrade parents.
- License Counting: If a downgrade child has no entitlement, it can be counted against its licensed upgrade parent, preventing the need for uninstallation of unlicensed versions.
- Date Management: Users can set start and end dates for software licenses, ensuring only relevant licenses are counted within specified periods.
- Upgrade and Downgrade Methods: Licenses can be upgraded or downgraded via either software license records or software model records.
Key Outcomes
By utilizing the legacy Software Asset Management plugin, ServiceNow customers can:
- Maintain compliance by effectively managing software usage and entitlements.
- Avoid unnecessary uninstallation of software by counting unlicensed versions against licensed versions.
- Streamline the software license management process through effective tracking and record-keeping.
The concept of upgrading and downgrading licenses is built in to the legacy Software Asset Management (com.snc.software_asset_management) plugin.
This is helpful when reconciling licenses. Downgrading a license is the process of purchasing a license, but using an earlier version. Upgrading a license occurs when a newer version of a license is not purchased, but you are allowed to use the newer version. Downgrading is more common than upgrading.
For example, you have licenses for the software model Microsoft Word 2010, but no licenses or entitlements for Word 2007. Discovery finds installations of Word 2007 being used in your organization. Rather than force users to uninstall all instances of this unlicensed version, you decide to count installations of Word 2007 against your Word 2010 license. To do this, you configure Word 2007 as a downgrade child in the Word 2010 Software Model record. A Software Model record is automatically created for Word 2007 which specifies Word 2010 as the upgrade parent.
If a software version has a downgrade child or an upgrade version that can be counted against the parent, the number of installs counted is restricted to the number of available rights of the parent. For example, Microsoft Word 2010 has a downgrade to Word 2007. Both versions have an active counter. Microsoft Word 2010 finds all entitled copies of Word 2007, and also takes out of compliance any installs from that downgrade counter until the available downgrade rights are used. However, if Microsoft Word 2010 only has 100 rights, then the maximum number of rights to be taken from the downgrade counter is 100.
You can set the start and end dates for a software upgrade parent and downgrade child to be valid. The software counter counts the upgrade and downgrade licenses within the selected dates. If the software counter runs outside of the date range, the upgrade and downgrade licenses are not counted.