<< Click to Display Table of Contents >> Navigation:  Modules > Asset Management > Master Catalog > Processors and Cores

Strict Processor and Cores computation:

Strict Processor and Cores is a highly flexible, Consolidate based management tool that delivers more control to users for managing processor information. End users are now able determine what asset data comes into the MIE, how to flag assets with unknown core values, as well as maintain a complete list of processors with correct information. SPCC enhances the tools already within the MIE to make processor management as automated as can be, and allows for greater user control to ensure asset processor data is accurate.

 

At its base, the Strict Processor and Cores table (SPCC) functions as an extension to the pre-existing Processor and Cores table. MIE users will be able to find the table under the Asset Management tab as a flyout of Master Catalog. It will be labeled “Processor and Cores(Strict)”. Here is where users will manage their processors if strict computation is turned on.

 

Strict Processor and Cores computation works as a part of Consolidate, and is based on several Consolidate settings (link to cons settings help) that determine how Consolidate will handle processors coming through asset data feeds. Given the correct settings, SPCC has a multitude of functions that make managing the processor list compiled in the MIE much more automated than previous versions.

 

One specific function of SPCC is to throw a staging exception during consolidate every time an asset record comes into the system with an unknown processor. If an asset record comes through SCCM or another type of auto-discovery, or through an import job, any record that has a processor manufacturer that is not presently in the SPCC table will be thrown as an exception, and that processor will be added to the SPCC table to be updated manually. If the ConsUnknownCoresFlagValue has been set, those assets with unknown processors will be given the value in this setting as their temporary core count.

 

Once these SPCC records have been updated, a subsequent consolidate will update these assets with correct core, logical core, and logical processor counts.

 

SPCC is also capable of correcting virtual machine core counts upon initial inventory. Unlike physical machines, virtual machine core counts will be set to the processor count of the physical machine it is related to rather than computing cores from the SPCC table. This ensures more accurate VM core counts on those tracked in the MIE.

 

For any import job configured to import data in for the processors and cores table, there must be a catchpoint assigned, and that catchpoint must have the auto-discovery role. Also note that feeds from the WDA do not require that.

 

There are 5 settings for  the Strict Processors and Cores, please check them under the help for consolidate settings