Skip to main content

What legacy operating systems can read a Windows 7 Bitlocker To Go encrypted USB drive?

Windows 7 Bitlocker-to-Go allows you to encrypt information on an entire volume. Even if the volume is a removable drive or USB memory key. To support the use of your portable devices, XP SP3 and Vista SP1 can open the encrypted key.

When you allow the key to autoplay, an application on the unencrypted portion of the drive brings up the BitLocker –to-Go reader and asks for the password. If you explore the device without using the reader, you will only see the unencrypted portion of the drive containing the reader software. Also, if you look at the properties of the drive, it is completely filled. The encrypted side will reserve all the space on the volume, minus the small portion for the reader.

Reference: http://blogs.msdn.com/rockyh/archive/2009/03/01/bitlocker-to-go.aspx

Comments

Popular posts from this blog

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...