this post was submitted on 07 Feb 2024
738 points (97.7% liked)
Technology
58992 readers
4567 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
FYI: You can set it to require a PIN + TPM, or even just a password eg using
manage-bde -on c: -password
.https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/manage-bde-on
Thanks, that sounds really useful. I'm guessing it won't work unless you're local admin though.
Yep, you'll need local admin of course.
Which kind of makes it useless in many corporate environments where it's most needed, since the users won't be able to set their own password.
I mean, if it's a corporate device then it's really a policy IT should be setting - this can be easily be done via a GPO or Intune policy, where an elevated script can prompt the end-user for a password.
Yarp. And when they forget it we use the 48 numerical recovery key found using the recovery ID that shows on the screen when you hit escape (from the bitlocker screen)
It would be insane to let non admin change settings like this.
I'm talking about letting the user change their own password. I'm honestly not sure how that would be technically accomplished in this situation without having to contact IT each time. It seems like something Microsoft should provide a no-frills GUI for that doesn't require elevation.
Yeah, that could be neat as long as they still add a recovery key to the AD or somewhere else. A problem with that is that the users will likely choose shit passwords. That could be mitigated with password rules but still
I suspect Microsoft wants you to use TMP or physical keys instead of passwords.