Hardware FixRecommendedDevice not working? Your driver may be the problemCheck updates for common hardware issues.Fix DriversThanksgiving DealsAmazon USThanksgiving week: Black Friday picks start earlyAmazon US: current deals, useful picks and tech finds.Check DealsWindows FixRecommendedWindows errors stealing your time? Find the fix fastScan stability, cleanup and performance issues.Fix Now×
FREEDOM251

Freedom251 › Blog

Best Method To Manage Bitlocker Using SCCM

By Freedom251 Team · · 9 min read

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.

For supported on-premises Windows clients joined to Active Directory, the best method is the current-branch BitLocker management feature in Microsoft Configuration Manager (formerly SCCM). Create a BitLocker management policy, configure its recovery service, deploy it to pilot and production collections, escrow recovery material through the management point, and monitor encryption and recovery compliance. This is Microsoft’s lifecycle-management path and can replace MBAM. Windows Server is the important exception: manage Server BitLocker with Group Policy, not a Configuration Manager BitLocker policy.

At a glance
Name Best for Key spec Platforms Checked
Configuration Manager BitLocker management policy On-premises Windows clients joined to Active Directory Policy-driven encryption, recovery escrow through a management point, site-database recovery records Supported Windows client editions; CMG-connected clients where the documented version and join state support it Nov 2026

What is the best way to manage BitLocker with SCCM?

Use the native BitLocker management feature in a supported current branch of Configuration Manager. Microsoft describes it as full BitLocker lifecycle management for on-premises, Active Directory-joined Windows clients and as a replacement for Microsoft BitLocker Administration and Monitoring (MBAM). Start by proving that your clients, site version, management points and collections meet that scope, then deploy a narrowly targeted policy before expanding it.

As an Amazon Associate I earn from qualifying purchases.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The policy controls encryption scope, protectors, recovery behavior and compliance reporting. It also deploys the recovery service to a management point so clients can upload recovery keys, recovery packages and TPM password hashes. Treat escrow and recovery testing as part of the encryption project, not as optional reporting work.

Which computers can use this SCCM BitLocker method?

Use it for eligible Windows client operating systems that are joined to your on-premises Active Directory and managed by a supported Configuration Manager current branch. Record the client edition, Configuration Manager version, AD DS join state, management-point assignment and whether communication goes directly to an MP or through a cloud management gateway (CMG).

Popular on Amazon
Integral 16GB Crypto-197 256-Bit Hardware Encrypted 3.0 USB Secure Flash Memory Drive - Certified to FIPS 197, Brute-Force Password Attack Protection & Rugged Double-Layer Waterproof Design
  • Certified to FIPS 197 - High-level information security standard approved by the U.S. Government
  • Brute-Force Password Attack Protection - Data is automatically erased after 6 failed access attempts. The data and encryption key are securely destroyed and the crypto drive is reset
  • Rugged Double-Layer Waterproof* Design - Protects the crypto drive against knocks, drops, break-in and submerging in water. The electronics are shielded by a hardended inner case. The rubberised silicone outer casing provides a final layer of protection
  • Auto-lock - The crypto drive will automatically encrypt all data and lock when removed from a PC/Mac or when the screen saver or "computer lock" function is activated on the host PC/Mac
  • Secure Entry - Data cannot be accessed without the correct high-strength alphanumeric 8-16 character password. A password hint option is available. The password hint cannot match the password

Windows Server is a separate policy boundary. Microsoft states that Server does not support BitLocker configuration through CSP or Microsoft Configuration Manager; deliver Server settings through Group Policy instead. Keep Server devices in a separate compliance scope so they are not marked noncompliant merely because they cannot consume the client policy. Microsoft’s BitLocker configuration guidance documents this limitation.

How does SCCM escrow BitLocker recovery keys?

When BitLocker Management Services are configured, the client backs up recovery keys, recovery packages and TPM password hashes to the Configuration Manager site database through the management point recovery service. Administrators use those records in the authorized help-desk or self-service recovery workflow when a user is locked out. The planning model and supported scope are described in Microsoft’s BitLocker management planning documentation.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Do not assume that an object in AD DS or a recovery-key object in Microsoft Entra ID is the authoritative record for this on-premises Configuration Manager workflow. If your runbook expects AD DS escrow, document that as a separate control; for Configuration Manager, verify the site-database record and the recovery portal result. A client can report compliance while the expected recovery record is absent, so test both signals.

How do I set up the policy safely?

Collect the following before opening the console: supported Windows client inventory, AD DS connectivity and join state, Configuration Manager current-branch version, all management points, CMG use, TPM status, existing MBAM dependencies and the people authorized to retrieve recovery material. Exact console labels vary by current-branch release, so confirm them in your site’s BitLocker management node.

  1. Define the scope. Decide whether the policy covers operating-system, fixed-data and removable drives. Specify required protectors, TPM behavior, recovery-password handling, encryption method and user prompts. Align each choice with your threat model and support process rather than copying an old MBAM configuration.
  2. Create a BitLocker management policy. Configure the Client Management settings so clients know where and how to escrow recovery information. The policy model deploys the recovery service to a management point.
  3. Use a pilot collection. Include representative hardware, TPM generations, laptops that roam and any CMG-connected clients. Confirm that clients receive policy before adding broad production collections.
  4. Secure the network path. For version 2103 and later clients, verify the management-point message-processing engine and secure client-notification channel. For version 2010 and earlier clients, provide the required HTTPS recovery-service path and certificate on every management point those clients can select.
  5. Protect the site database. Deploy the documented SQL certificate named BitLockerManagement_CERT, grant the recovery database roles control over it, and back up the certificate and private key under your disaster-recovery controls. Enable plain-text recovery storage only as a documented exception with compensating safeguards.
  6. Validate encryption and escrow. On pilot devices, verify that encryption starts with the intended protector, recovery material reaches the site and the device appears in compliance views. In BitLockerManagementHandler.log, version 2103-or-later clients report entries beginning “Recovery keys escrowed to MP”; version 2010-or-earlier clients use the “Checking for Recovery Service at” cue.
  7. Test authorized recovery. Use a test device and the approved help-desk or self-service process. Confirm that the disclosed key is logged appropriately and that the client generates and escrows a replacement key.
  8. Expand by rings. Move from pilot to a small production ring, then broader collections only after policy receipt, encryption, escrow and recovery all pass.
  9. Separate Server management. Link and monitor a Group Policy design for Windows Server, and keep its reporting logic separate from client Configuration Manager compliance.

What changes between Configuration Manager 2103 and 2010?

The important distinction is the recovery transport, not the SCCM name. A current site can still have older clients, so inventory the client versions before removing legacy certificates or HTTPS bindings.

Decision axis Configuration Manager 2103 or later Configuration Manager 2010 or earlier
Recovery-service implementation Management-point message-processing engine Legacy recovery service on the management point
Key transport Secure client-notification channel HTTPS recovery-service path required
CMG support Supports the message-processing-engine model and expanded recovery capabilities More limited; perform version-specific checks
Troubleshooting log cue “Recovery keys escrowed to MP” “Checking for Recovery Service at”
Primary design risk Client-notification and management-point reachability Certificates, IIS binding and HTTPS on every possible management point

Microsoft documents the architecture change and the legacy-client requirements in its recovery-data transport guidance. For 2010-or-earlier clients, one uncovered management point can cause failover to break escrow.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How should recovery data be protected?

Protect recovery material in transit and at rest. The transport must use the secure path appropriate to the client generation. In the site database, use BitLockerManagement_CERT to encrypt recovery data, protect its password and private key, restrict Configuration Manager role and SQL permissions, and include the certificate in site-database disaster recovery. Microsoft warns that restoring the database without the certificate can leave recovery keys inaccessible. The implementation details are in Microsoft’s recovery-data encryption documentation.

Recovery material is effectively an access path to encrypted data. Limit portal and help-desk permissions, record who disclosed a key, and make certificate backup ownership explicit. Plain-text storage is an opt-in fallback, not the preferred design; if enabled, document why and add compensating controls.

How do I monitor SCCM BitLocker compliance and escrow?

Use the Configuration Manager monitoring and reporting views available in your current branch, then correlate them with client logs and the recovery record. A single “compliant” state is not enough: check encryption state, protector state, policy receipt and escrow separately.

  • AD DS computer account and connectivity: Confirm the computer account is present, enabled and resolving correctly, and that the client can reach AD DS and its assigned management point. A stale account, broken secure channel or offline client can leave policy and escrow in mixed states.
  • Azure AD/Microsoft Entra recovery-key objects: Treat these as a separate identity-platform signal, not proof that the Configuration Manager site database contains the key. For this SCCM method, validate the management-point upload and site-database recovery record.
  • Client says compliant, but keys are not in storage: Recheck the policy assignment, recovery-service path, certificate protection and the timestamped client log. Do not close the incident until an authorized recovery lookup succeeds.
  • Devices in mixed states after reimaging: Reconcile the new computer record with the previous device identity, confirm policy receipt and force a fresh escrow cycle. Keep the old record only according to your retention policy so operators do not retrieve a key for the wrong machine.
  • Encryption in progress: Verify that the intended protector exists, the device remains powered and policy is still assigned. Allow the client to complete before judging compliance.
  • Encryption not started or not compliant: Check client eligibility, collection membership, policy receipt, TPM readiness, user prompts and available management-point connectivity.
  • Encryption stuck in progress: Compare the reported state with local BitLocker status and BitLockerManagementHandler.log; investigate pending reboot, protector failure, storage problems or loss of policy communication before redeploying.
  • Escrow missing in AD DS: Remember that Configuration Manager’s documented recovery destination is its site database. Verify the SCCM recovery record and portal rather than declaring failure solely because an AD DS object is absent.
  • Unknown: Treat unknown as an investigation state. Check inventory freshness, last policy request, management-point reachability and log timestamps, then refresh the device record.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

How do TPM 1.2, TPM 2.0 and “TPM not ready” affect deployment?

Inventory TPM 1.2 and TPM 2.0 separately and make the policy’s protector requirements explicit. A device with TPM hardware can still report “TPM not ready” if firmware initialization, ownership or the operating-system readiness state is incomplete. Do not force encryption on that device until the approved hardware-remediation process is complete; use a documented recovery-password path only when your security policy allows it.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Also popular on Amazon
Sale
Kingston IronKey Vault Privacy 50 16GB Encrypted USB | FIPS 197, AES-256bit, BadUSB Attack Protection, Multi-Password Options, IKVP50/16GB
  • FIPS 197 with XTS-AES 256-bit Encryption: Provides business-grade security with hardware-based encryption to protect your sensitive data
  • Brute Force and BadUSB Attack Protection: Safeguards against unauthorized access attempts and malicious USB attacks with digitally-signed firmware
  • Multi-Password Option with Complex/Passphrase modes: Offers flexible password configuration options to meet various security requirements and user preferences
  • New Passphrase Mode: Enhanced security feature allowing users to create longer, more memorable password phrases for easier access without compromising protection
  • Dual Read-Only (Write-Protect) Settings: Enables write protection functionality to prevent accidental data modification or deletion when needed

When a device has no usable TPM, an unexpected protector combination or an unknown inventory state, keep it in the pilot exception collection and resolve the hardware or policy cause. This prevents a broad deployment from producing apparently compliant records without a recoverable protector.

What happens when a recovery key is disclosed?

After an authorized self-service or help-desk portal discloses a recovery key, Configuration Manager requires the client to rotate the key and escrow a replacement. Microsoft’s recovery-service documentation describes this behavior. Record the disclosure and verify the replacement upload; do not treat the disclosed key as a permanent credential.

How should an MBAM migration be handled?

Use the Configuration Manager policy as the destination lifecycle plane, but keep the legacy MBAM service available for the agreed transition window. When the first Configuration Manager policy reaches a migrated device, the client rotates its key and sends the new key to the Configuration Manager recovery service. Reconcile devices that never receive the new policy, and do not rely on registry workarounds or unsupported scripts as the primary design.

Does SCCM BitLocker management work through a CMG?

Microsoft documents BitLocker policy and recovery-key escrow over a CMG from Configuration Manager 2010. Domain-joined clients communicating through CMG use the management-point message-processing engine, and hybrid Microsoft Entra joined devices also use that engine. From version 2103, CMG-connected management supports recovery keys for removable drives and the TPM password hash; verify the exact capability against your supported branch and join state before promising it in a runbook.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How we picked the method

The recommendation follows Microsoft’s documented support boundary, lifecycle coverage, recovery escrow workflow, transport architecture, database-encryption requirements and Server limitation. It favors the native current-branch policy over legacy MBAM components because it provides one supported management plane for eligible clients, while preserving Group Policy for Windows Server and explicit version checks for older clients.

Frequently Asked Questions

Where are BitLocker recovery keys stored when SCCM manages them?

The documented Configuration Manager workflow sends recovery keys, recovery packages and TPM password hashes to the site database through the management point recovery service. Access them through the authorized recovery workflow, and protect the database certificate so a site restore does not make the records unreadable.

Can I use one BitLocker policy for Windows clients and Windows Server?

No. Configuration Manager BitLocker configuration is for supported Windows client devices in this scope. Build and link a separate Group Policy design for Windows Server, then report the two populations independently.

Why did a recovered BitLocker key stop working later?

Configuration Manager rotates the key after an authorized self-service or help-desk disclosure and escrows a replacement. The old value should therefore be treated as spent once the rotation completes.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What should I check first when escrow fails after a management-point failover?

Identify the client generation. Older 2010-or-earlier clients require an HTTPS recovery service and certificate on every management point they might select; newer clients depend on the secure client-notification and message-processing path. Then inspect the corresponding BitLockerManagementHandler.log entry.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply. Prices as of November 20, 2026 5:51 am GMT+0530.

Leave a Reply

Your email address will not be published. Required fields are marked *

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Recommended PC Tool
Recommended PC Tool
Outdated Drivers Are Slowing You DownFree scan - exact matches
PC Slower Than It Used to Be?Free scan - under a minute

Two free Windows tools

One Free Minute Could Fix That PC

Before you go - each of these free tools takes about a minute and tackles what quietly slows a Windows PC down.

Special offer. View Outbyte info, uninstall instructions, EULA, and Privacy Policy.