Can you set up BitLocker to use your domain password?

To both unlock a BitLocker encrypted hard drive and log on at the same time is not possible. When starting up a computer that has its boot drive encrypted by BitLocker, the bitlocker software will prompt for the user to enter their PIN number in before BitLocker allows the OS to start. You can still allow your users to set their BitLocker PIN number to be the same as their domain logon password by turning on enhanced PINs for startup in Group Policy. To do this:

Create or edit an existing GPO on you network.
Browse to Computer Configuration à Policies à Administrative Templates à Windows Components à BitLocker Drive Encryption à Operting System Drives.
Open the setting for Allow Enhanced PINs for startup.

Normally only numbers are used for the PIN. With this setting, all valid characters allowed for a domain password can be used for a startup PIN. If you are looking for a single sign on option with BitLocker, it is not possible. Should your users set their domain password to be identical to the BitLocker PIN, they run the risk of inadvertently typing the wrong PIN in after changing their domain password. Should this happen, the recovery key would be needed to gain access to the hard drive.

Using this method also negates the two factor authentication that is provided with BitLocker. For this reason, I recommend that users do not utilize the same PIN and domain password.

Comments

Anonymous said…

Is this still the case?

March 28, 2011 at 12:50 PM

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog