Document BitLocker Information Crate
What does the Document BitLocker Information Crate do?
Our Document BitLockers crate automates the collection and documentation of BitLocker encryption details for computers managed through your RMM. Maintain visibility and compliance by syncing key encryption attributes into your preferred documentation platform. BitLocker details are collected by running a PowerShell script via the RMM, so only computers that are online during execution will have their BitLocker information documented. This Crate not delete BitLocker asset records that are no longer associated with active computers.
Why use the Document BitLocker Information Crate?
Keep documentation in sync with actual system configurations through scheduled execution.
Work with supported RMM and documentation platforms to automate asset management.
Save time by automating data collection and reducing manual documentation tasks.
Ensure critical disk encryption data like recovery keys and protection status are properly recorded.
Crate prerequisites
Before unpacking this Crate, you'll first need to have:
An active PSA integration with Rewst
An active RMM integration with Rewst
Unpack the Document BitLocker Information Crate
Navigate to Crates > Crate Marketplace in the Rewst platform.
Search for
Document BitLocker Information
.Click on the Crate tile to begin unpacking.
Click Unpack Crate.
Click Continue.
If desired, customize settings for:
Include Unprotected Devices: A trigger variable that defines whether to include computers without BitLocker enabled.
RMM Platform: A trigger variable that specifies which RMM to use for device listing and PowerShell execution.
Documentation Platform: A trigger variable that selects where BitLocker details are documented.
Cron Schedule: A trigger parameter that defines when the workflow will be executed. This determines the frequency at which computer configurations and BitLocker data updated.
Click Unpack.
Test the Crate
To test this Crate, you'll need to adjust the cron trigger's schedule to a few minutes in the future, then adjust it back to your regular schedule after the test. Alternatively, you could wait until the regularly scheduled run occurs and check your result, which would not require you to update the cron trigger schedule. The cron trigger for this Crate is set to trigger daily at 7:00 AM (UTC).
Navigate to Automations > Workflows.
Search for
[REWST - CRATE] Docs: Document Bitlockers
.Click on the workflow to open it in the workflow builder.
Click
to Edit Trigger.
Adjust the cron trigger's schedule to five minutes from your current time. The workflow will run on its own then.
Verify documented results. Depending on your configured documentation platform:
Check for computer assets/configurations and verify they match with your RMM.
Check for BitLocker assets/documents and verify they are correct for each computer.
Re-adjust the time of the cron trigger to when you would like it to routinely run.
![Screenshot of the Rewst automation interface titled “[REWST – CRATE] Docs: Document Bitlockers,” showing an enabled cron job trigger named “Cron Job.” The configuration includes integration overrides like ConnectWise Automate and others. The cron schedule is set to run daily at 7:00 AM UTC, with no errors detected in the external status.](https://docs.rewst.help/~gitbook/image?url=https%3A%2F%2F1835401289-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FAQQ1EHVcEsGKBPVHmiav%252Fuploads%252FrJyc7gatsdqylCnovpzJ%252FScreenshot%25202025-07-25%2520at%25203.51.53%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Ddf2495aa-49e2-4171-aba6-e7eacd6a783f&width=768&dpr=4&quality=100&sign=1511f12b&sv=2)
Organization variables associated with this Crate
agent_smith_is_installed
azure_iothub_name
azure_iothub_resource_group
azure_iothub_subscription_id
cwControl_CompanyName
cw_automate_client_id
cw_control_session_group_override
datto_rmm_site_id
default_rmm
documentation_platform
hudu_company_id
immybot_tenant_id
itglue_org_id
kaseya_vsa_10_scriptid
kaseya_vsa_org_id
kaseya_vsa_x_org_id
nable_customer_id
nable_device_filter_id
nable_rewst_powershell_script_id
ninja_org_id
ninja_run_as_user
preferred_domain_controller
superops_client_id
syncmonkey_company_id
Last updated
Was this helpful?