There is an encryption policy in effect, limiting writing to flash drives to those drives that are encrypted with BitLocker. From time to time, a user will call in, reporting that the encryption process has stalled, and does not seem to want to continue. Invariably, this occurs on drives that already contain data, and the encryption stalls when the process starts encountering actual data. A workaround is easy enough to enact, if a bit fiddly. Here’s how:
Having gone from Windows XP to Windows 7, we are seeing a rash of new problems. One of these is that a lot of our users are unable to boot into Windows, as they are prompted for a BitLocker Recovery Key. The temporary fix for this is simple enough; look up and tell the user the BitLocker Recovery Key, and have them enter it. Well, I say simple, but the BitLocker Recovery Key is a string of eight segments of six digits, and having to enter this each and every time you reboot gets … tiresome … very quickly.
So, let’s see if we can’t improve on that. There are two methods, the first usually suffices, but sometimes, I’ve had to go for the second. The first solution is as follows: