Authorization Transaction Table

<< Click to Display Table of Contents >>

Navigation:  Modules > Asset Management > Software License Management > Authorizing Software >

Authorization Transaction Table

The MIE maintains a trimmed MSL Authorization Transaction table.  The table records all MSL authorization events, along with a code that defines how the MSL item was authorized and/or how authorization was removed.  The following codes are logged as part of each authorization / authorization removal event:
 

Code

Definition

AAAUTHORIZE

MSL item was authorized by an Authorization Analyzer rule.

AUTHORIZE

MSL item was authorized either through the user interface (directly editing current authorization records or through mass update), or by an adjustment made due to a linked counter value change.

BULKAUTHORIZE

MSL item was authorized via the Bulk Authorization process.

CIAUTHORIZE

MSL item was authorized via Configuration Item-based authorization.

MOVEMSLAUTHORIZE

MSL item was authorized by a Move MSL applications Catch Point screen.

PORTALAUTHORIZE

MSL item was authorized by the Software Request Portal.

REASSIGNAUTHORIZE

MSL item was authorized by reassignment.  An existing authorization's MSL title was changed to the current MSL title.

ROGUEAUTHORIZE

MSL item was authorized through rogue discovery (via autodiscovery).

ROGUEUSAGEAUTHORIZE

MSL item was authorized through rogue discovery (via the WDA Usage Collector)

STATUSAUTHORIZE

MSL item was authorized via Status-based authorization.

SUITEAUTHORIZE

MSL item was authorized via a suite adjustment (this is an unlikely event as most suite adjustments will be to zero out the required entitlements of component-level titles, in which case it will be a SUITEHARVEST event)

GROUPAUTHORIZE

MSL item was authorized due to a change in the membership of an authorized group.  If membership is increased using the MIE's user interface, any new members will be "Group Authorized".  If membership is increased due to rogue discovery, those members will be "Rogue Authorized"

AUTOHARVEST

Authorization for MSL item was removed by auto-harvest.

DOWNSIZEHARVEST

License unit count required to cover an existing authorization was reduced.  The reduction in count triggers a down-size harvest event for the number of required license units removed.

EQUIVALENTHARVEST

Authorization for MSL item was removed as it is a defined equivalent to another authorization that is assigned to the same asset.  This is generally the result of earlier versions of a given title being harvested.

HEADERHARVEST

Authorization for MSL item was removed due to the removal of one or more MSL matching aliases.

MANUALHARVEST

Authorization for MSL item was removed by the user or a technician via a Catch Point screen, and the MSL item was covered by a license (which means authorization was removed and the license was returned to the unallocated pool.)

MANUALHARVEST-NC

Authorization for MSL item was removed by the user or a technician via a Catch Point screen, and the MSL item was not covered by a license (which means authorization was simply removed from the asset.)

MOVEMSLHARVEST

Authorization for MSL item was removed by the user or a technician via the Move MSL applications Catch Point screen.

NONMSLHARVEST

Authorization for MSL item was removed because the setting SLMHarvestNonMSLAuths was set to -1 and the authorization was created for an MSL title that has its Item is officially on the MSL setting unchecked.

ORPHANHARVEST

Authorization for MSL item was removed because the MSL title is set to be authorized to a device and there is no longer a device record in the assets table (the record was likely deleted.)

REASSIGNHARVEST

Authorization for MSL item was harvested in order to change the MSL title assigned to an authorization.

STATUSHARVEST

Authorization for MSL item was removed by status-based harvesting.

SUITEHARVEST

Authorization for MSL item was removed by suite processing.

UPGRADEHARVEST

Authorization for MSL item was removed due to an upgrade.