Modules > Asset Management > Software License Management > Managed Software List (MSL)

A suite is defined as an MSL title that includes other MSL titles as components. The collection of components is licensed as a suite. Examples include Microsoft Office and Adobe Creative Suite.

Often the titles included in the suite can also be licensed individually. That presents a challenge for keeping tracking of required licensing.

Each MSL title allows defining of suite components. Such components would be defined for a "Suite level" title. For instance, Adobe Creative Suite 5 would be a suite level title. Components would only be defined at the suite level title.

Suite level titles must never be added as components of other suites (no nesting of suites)

When a suite is defined, by adding one or more components to a given MSL suite-level title, the MIE will respond by automatically adjusting the entitlement (license) requirements of the various components as follows:

1. Each time Consolidate runs, the current list of authorizations will be checked for entities that have both the suite level title authorized and one or more components authorized as well.

2. The suite level authorization must have an Entitlement Units Required (EUR) value greater than 0.

3. The entity to be checked will depend on the "How Authorized" setting of the suite level title. If set to "By Device", then authorizations for a device will be checked. A user will be checked if set to "By User" and a group will be checked if set to "By Group".

4. Any components that are found to have an EUR greater than 0 will have their EUR set to 0. Credits will be staged for the number of EURs that existed prior to being zeroed. A component will have its EUR zeroed only if the suite level title is also authorized for the same entity and if that suite level title has an EUR value greater than 0.

5. Each time Consolidate runs, suite component membership is re-checked. If an authorization that had been adjusted is for a title that is no longer a component of a suite, that authorization will have its EUR value set back
to 1.

The net effect will be the carrying of the entitlement requirement at the suite level, and not at any of the individual components level.

This adjustment of suites happens early during Consolidate, before any harvesting and/or license allocation takes place.

NOTE:

This adjustment may very well work against any Authorization Analyzer (AA) rules that may be in place, but it will not override those rules (nor will those rules override this behavior). It is up to the rules designer to understand this suite adjustment logic and to no write rules that will contradict or conflict with this behavior.

ConsOverrideSuiteLicRequired – If set to -1, Consolidate will zero the required entitlement units for each suite component, regardless of whether the Suite MSL is licensed. The default value of 0 indicates that a license is required for the suite title before Consolidate will zero the required license units for the suite components.

Wiki Synchronization

If you have opted into the Wiki, suites created at the Wiki level are propagated down to your local MSL, assuming the suite is part of the family or publisher that you’ve opted into. This applies to the suite definition and its components. If, at the Wiki level, additional components are added to the suite, they are propagated down to the local level as well. By default, suite components removed at the Wiki level are not removed at the local level. This behavior can be altered by setting ConsMSLWikiSuiteSyncFull to -1.

ConsMSLWikiSuiteSyncFull

0=Sync new components locally,-1=Full sync including removal

Suites

Suites