With SCCM being offered free (or at heavily discounted rates) to volume licensing customers, it is a popular choice for inventory and distribution. We looked at the problems of software inventory with SCCM in an earlier article So here we are going to look at some of the other problems you can expect using SCCM and how to overcome them.
SMS uses WMI to gather the processor information. So, on older OS’ e.g. Windows Server 2003 running on newer hardware the processor and core information may be incorrect. This could be picked up in a vendor audit (e.g. by Oracle or IBM who license their products by processor) and cause compliance problems.
Application monitoring/ Software Metering and reporting
SCCM does have the ability to monitor software usage, but this can only be achieved with the skills of a trained SCCM expert setting up and configuring the software. It does not work out of the box. Furthermore, the data from this configuration can take many days to produce.