SLMHowToCredit

This is a drop-down that specifies how credits will be issued.  The default is First In, First Out, which means the next credit issued will be the first one that was staged for consideration.  

Entity Charged (only on debit) applies to credits that are made on the next debit event.  This selection gives priority to the business entity that is being charged at the time of debit.  Instead of staging the next credit for processing, priority is given to any credits that are available for staging that match the business entity that is about to be charged for the debit.  This will cause movement of authorizations within the same business entity to cancel each other, financially, within the same processing period.

SLMHowToDebitCredit

This is a drop-down that specifies the minimum organizational information that must be present in a credit/debit record to participate in credits/debits.  If the minimum organizational information is not present in the record, it will be skipped.  It will be processed when sufficient organization information has been added to the record.  Organizational information contained in the corresponding asset record is used to fill in blanks in the credit/debit record each time the credits/debits job is run.

SLMMinDaysBeforeReclaim

This specifies the minimum number of days an asset must wait before it can reclaim its own harvested software.  This setting is used to overcome latency that may exist in the system that would cause the immediate reclamation of harvested software by a given asset.  Such latency would be due to the frequency with which autodiscovery runs and feeds information to the MIE.  Given latency, it is entirely possible for a piece of software to be harvested after autodiscovery has run but before the current run has been fed to the MIE for processing.  That would cause the MIE to see the harvested software back on the asset, which would cause an immediate reclamation.  This wait period allows the latency to pass, thereby reducing the probability of immediate reclamation.  

SLMWhatToCharge

This is a drop-down that specifies which price to charge.  Both the Charge Price and the Market Price are maintained in the Managed Software List table.

SLMWhatToCredit

This is a drop-down that specifies which price to credit.  Both the Charge Price and Market Price are maintained in the Managed Software List table, and the current value will be credited.  In addition. you may choose to credit the Deployed Price, which was what was originally charged when the software was last deployed.

SLMWhenToCharge

This is a drop-down that specifies the event upon which a charge is assessed. When Discovered will cause charging to occur when the next Credit/Debits run happens for all assets that have a Managed Software List (MSL) item for which they have not been charged. When Covered will cause charging to occur when the MSL item on the asset has been allocated a license.

SLMWhenToCredit

See When to Credit.

SLMGraceFromAssetCreation

Establishes the first of three windows used to extend grace to rogue MSL software discoveries.  Grace is basically the waiving of a charge or debit.  If this setting is negative, this grace window is not available.  If this setting is zero or positive, it will be added to the date of creation of the asset record on which the MSL application has been authorized.  If the date of authorization of the MSL application for this asset falls between the asset creation date and the asset creation date plus this setting, grace will be extended.  For example, if this setting is 7 and the creation date for the asset record is 8/1/2007, then grace will be extended to any MSL applications authorized as rogue discoveries to be on this asset between the dates of 8/1/2007 and 8/8/2007, inclusive.

SLMGraceFromMSLStartCharging

Establishes the second of three windows used to extend grace to rogue MSL software discoveries.  Grace is basically the waiving of a charge or debit.  If this setting is negative, this grace window is not available.  If this setting is zero or positive, it will be added to the MSL Debits (charges) start on this date for rogues for this MSL application setting.  Any rogue MSL application authorized to be on any asset prior to the end date of this window will be extended grace.  If the Debits (charges) start on this date for rogues for this MSL application setting is blank or null, this window is not available.

SLMGraceFromAddAlias

Establishes the third of three windows used to extend grace to rogue MSL software discoveries.  Grace is basically the waiving of a charge or debit.  If this setting is negative, this grace window is not available.  If this setting is zero or positive, it will be added to the date the alias that was used to match the  application to the MSL, was added.  This grace window ensures that rogue discoveries that would have been graced if all aliases had been known and properly set at the time of discovery are extended grace.  For example, assume an alias is added to the MSL for Acrobat Professional.  The addition of the new alias causes all assets with the matching alias to be discovered as rogue installs on the next consolidate.  Depending on when the alias was added, those rogue discoveries would fall outside the other two grace windows and would be charged.  This grace window extends to only those MSL applications that are matched to the newly added alias, which would allow all the assets with matching aliases to be extended grace.

SLMOnlyRogueAuthorizeStatus

One or more status values, separated by piping characters ("|"), which an asset must be in before any rogue software discovered may be rogue-authorized for that asset.  The MSL title must be set for assign authorizations to the device for this setting to be honored.  If left blank, all asset status values will allow rogue authorizations.