This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
BitLocker encrypts a volume. The planner drafts a rollout from answers you type. The recovery-key checker looks at the shape of a key you type. Neither tool encrypts a disk and neither tool stores a key.
The recovery key goes to the store you already use, not into the ticket and not into chat. Encrypt later, one pilot machine you can still sign in to if the key is wrong. Do not enable it on a machine you do not administer, and do not use it to lock someone else out.
A key you cannot find is a disk you cannot open. Write where the key will live before any later enable.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the host named in the ticket. Read the draft, then the host, then decide.
Rollback is the file, the package version, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.
- Name the pilot computers you administer.
- Name the store for recovery keys.
- Draft the plan.
- Do not paste a recovery key into the note.
- Do not encrypt during the reading.
- Stop.
Mistakes that outlive the command
BitLocker Deployment Guide goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A recovery key in the ticket.
- A machine you do not administer.
- Encryption started during the reading.
- No place named for the key.
- BitLocker used to lock someone else out.
Decisions to write down
One decision for BitLocker Deployment Guide: The computers are yours. The key store is named. No key is in the note. Nothing was encrypted yet. And the pilot is one group.
Checks before you call it done
Confirm this before you call the change done: The pilot is written. The key store is written. No key is in the note. Nothing was encrypted. And a second person can say where a key would go. If one of those fails, stop.
# Recovery keys stay in the store.
# Do not paste one into the ticket.
# Computers you administer.
# Do not encrypt during the reading.Before you leave the host
BitLocker Deployment Guide ends when the hostname in the prompt matches the hostname in the ticket. If it does not, you are on the wrong host. Stop. A command that succeeded on the wrong host is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the host and does not know which disk is empty. You delete a line that names a host, a path, or an account you did not write down.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a host because a draft included them.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save in the ticket or in git. The real secret stays in the password store.
One change is the window. If two things move and the result is wrong, you will not know which one did it. The next change waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied change produces a host nobody can rebuild. Restore the copy you took first.
A second person reads the hostname and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the host alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a host you do not administer. You do not disable a firewall, AppArmor, or SELinux to make a check pass.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.