Create a BitLocker Encryption Compliance Report with Powershell in SCCM
This can be achieved fairly easy using SCCM Configuration Items (CI) and Configuration Baselines (CB).
Script release history
Script
Script parameters
- DriveType
Specifies the drive type(s) for which to get the bitlocker status. Default is: ‘3’. - DriveLetter
Specifies the drive letter(s) for which to get the bitlocker status. Default is: ‘All’.
Gets the BitLocker protection statusConfiguration Item
Create the CISet the Operating System on which the CI can runCreate a new setting and add the PowerShell scriptCreate the first Compliance Rule for Script Error DetectionCreate the second Compliance Rule for BitLocker Status DetectionYou should end up with something like thisBaseline
Create a new Baseline and add the Configuration item to itDeploy the Configuration BaselineValidation
On the machine where you deployed the Baseline run Machine Policy Retrieval & Evaluation CycleThe Configuration Baseline should show up in a couple of minutes in the Configurations tabYou can view a local report to check the complianceSee “Instance Data” for the compliance check resultsOr you can check the deployment results in the Monitoring node on the Site ServerReporting
Report previewYou can download my Configuration Baseline report from here