Use these guidelines to avoid common issues when you use Discovery and System Center Configuration Manager (SCCM) together.
Decide Whether you will use Asset Intelligence
It is very important to not switch back and forth between Asset Intelligence (AI) and non-AI
software data sources as the software correlation data is tracked differently. If you must
switch at between data sources, remove all the software installation records imported by SCCM
before the switch occurs.
When Software Asset Management is not enabled, software installation records are stored in the
Software Instance [cmdb_software_instance] table. When Software Asset Management is enabled,
software installation records are stored in the Software Installation [cmdb_sam_sw_install]
If records are not removed before the switch, duplicate records may exist. In the unfortunate
event that the AI and non-AI data becomes mixed, the Software Installation table should be
Leverage the SCCM Asset Intelligence Feature
In Fuji, you can leverage the AI feature in the following SCCM plugins:
- Integration - Microsoft SCCM 2007 version 3.1.0
- Integration - Microsoft SCCM 2012 v2 version 4.1.0
To prevent duplicate software imports, you activate either the AI or the non-AI scheduled
import for these plugins.
To activate the AI scheduled imports:
Tracking Your Software With Both SCCM and Discovery
When Discovery and SCCM are both enabled on a system, the software records found through both
tools could overwrite each other. If you prefer that your Windows software data be collected by
SCCM instead of Discovery, you can set the Windows software is SCCM managed property.
If this property is set to Yes and an internal process
determines that the computer is managed by SCCM, then Discovery does not populate the software
records for Windows software data. The following information level message is written to the
Discovery log file.
Skipping software population because the CI is managed by SCCM
SCCM Integration is active before Discovery is enabled and the property is enabled, then
Discovery ignores the population of software for any CIs that are also imported through SCCM. If
Discovery is enabled before the SCCM Integration, it is possible for software installation data
from both sources to be mixed.
Set an Appropriate Import Frequency
It is recommended that the import frequency be no greater than the frequency of the cleanup
of the table that keeps track of deleted software in SCCM.
Remove Deletion Table Records
Remove the deleted software table records within the SCCM MSSQL database the very first time
software is imported to Discovery. This eliminates the need to check against deleted software,
and therefore has faster performance.