Reporting in CM12 is Replaced with SSRS with more features and little complicated if you are not used to it.
To know the Status of content (Packages) ,you can look at monitoring Node—>Distribution Status—>Content But somehow i did not like this to go Every time (I feel it takes much time to load all the packages) if i want to know the Compliance Status of all created packages in CM12.
I then created simple SQL Query which you can use to create SSRS report in nice format or Run it from SQL Server management Studio.
What you get from this : Software Name,PackageID,Package Type ,Targeted,Installed,Not Installed,Compliance,Manufacturer,Source Size in MB,Source Version.
SELECT distinct v_Package.Name [Software], PSD.PackageID,
Case v_Package.PackageType
When 0 Then ‘Package’
When 3 Then ‘Driver’
When 4 Then ‘Task Sequence’
When 5 Then ‘software Update’
When 7 Then ‘Virtual’
When 8 Then ‘Application’
When 257 Then ‘Image’
When 258 Then ‘Boot Image’
When 259 Then ‘OS’
Else ‘ ‘
END AS ‘Type’,
PSR.Targeted ,PSR.Installed,(psr.Failed+psr.Retrying) as [Not Installed],
ROUND((100 * psr.installed/PSR.Targeted),2) as ‘Compliance’,
v_Package.Manufacturer, SMSPackages.SourceSize / 1000 AS [Size (MB)]
,v_Package.SourceVersion
FROM v_PackageStatusDistPointsSumm PSD
INNER JOIN v_Package ON PSD.PackageID = v_Package.PackageID
INNER JOIN SMSPackages ON v_Package.PackageID = SMSPackages.PkgID
inner JOIN v_PackageStatusRootSummarizer PSR ON PSR.PackageID=PSD.PackageID
group by v_Package.Name,psd.PackageID,v_Package.PackageType,psr.Targeted,PSR.Installed,v_Package.Manufacturer,SMSPackages.SourceSize,v_Package.SourceVersion,
PSR.Failed,PSR.Retrying
ORDER BY 7
More fields,customize it.
Next post,will be SSRS SQL report :Status of Failed Packages on what Distribution Points.This can be linked to above report nice way for Troubleshooting.
SCCM Configmgr SSRS SQL report:Status of All Packages with Targeted,Installed ,Compliance % is a post from: Eswar Koneti's Blog