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

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

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