• On the Software Entitlement form, there are new licensing types to support Microsoft Software Assurance licenses.
  • Microsoft Upgrade licenses are upgraded to Step-up licenses.
• Content-related upgrade information:
  • Existing software models and entitlements are updated with downgrade rights content. If you've already specified downgrade rights, deactivate any duplicate entries that may occur.
  • Existing software models are updated with the next version. Updated content doesn't override a software model that's specified with the next version.
    Note: Once you upgrade, you may see a change in your reconciliation results. Downgrade rights that are added by Content on license entitlements are used to evaluate the rights needed for compliance.
  • When downgrade rights or next version is set, a new software model is created if one doesn’t exist. This creation could result in duplicate software models because the Version and Edition values on the existing software model are used to check if a software model exists.
• Any existing entitlements with Per Core (Physical Core) and Per Core (Virtual OSE) license metrics are upgraded to the new Per Core license metric.
  Note: Once you upgrade, you may experience a change in your reconciliation results. Rights are calculated for both Per Core (Physical Core) and Per Core (Virtual OSE). The results display the option that results in the lowest number of rights needed.
• On the Software Entitlement form, the Agreement type None is no longer supported and any agreements with this value are upgraded to the type Generic.

• Software that's delivered through Citrix XenApp and XenDesktop is licensed based on potential access rather than actual usage. During the upgrade, all existing installations for software delivered through Citrix are deleted. However, the referenced Discovery models are not deleted. On the next execution of discovery, after the upgrade, all the installations based on potential access are created and associated to the existing ServiceNow® Discovery models. Discovery must be executed within three weeks of the upgrade.
  Note: If Discovery isn't run during the three-week time frame, an existing scheduled job deletes any orphan Discovery models without installation records. Recreating these Discovery models causes unnecessary rework.

• Download the latest SAP ABAP code from the Downloads menu under the SAP Compliance and Optimization module. ABAP code deployed in an SAP environment should be compatible with the ServiceNow release.

If you upgrade and have software models with this option selected, you can do a bulk update and clear the License Under Management option from any software models you don’t want to include in your reconciliation results. When you run reconciliation again, only the software models with the option still selected will display in your results.

• SaaS License Management (included with the Master plugin)
• SaaS License Management Integrations (included with the Master plugin)
• Spend Detection (you must first get the Software Spend Detection SKU at no additional cost, before you request this plugin in ServiceNow® HI)