![]() You may need to enable the BitLocker feature in Windows and ensure command line management is available. For the purposes this article, the following code should work on Windows Server 20 R2, and Windows 8.x. I know that some versions of Windows 7 cannot make BitLocker drives, but CAN read them. I use Windows 8.1 Professional and I have it available. VHDs and BitLocker are not always available depending on the version of Windows you are using. If you need help with that, you can head over to the aforementioned TrueCrypt home page and see how that’s done. I’ll be starting from the point that you already know how to make a VHD (or VHDX), and enable BitLocker on that virtual drive. We’ll use some PowerShell and a Scheduled Task in conjunction with our VHDX to bring it to life. ![]() ![]() This VHD (or VHDX) will serve as our analogy to a TrueCrypt encrypted container. Interestingly enough on the TrueCrypt home page (at least for now) is the exact instructions for creating a new BitLocker encrypted VHD. I set out to see if I could get BitLocker to perform this same functionality. One of the nice things about TrueCrypt was the fact that it could, at login, have an interface where you could enter a password and mount an encrypted file as a volume accessible via a drive letter on your computer. My main problem with BitLocker, like many things in the Microsoft world, the phrase “some assembly required” is definitely applicable. But even still, if you’ve already got a copy of Windows, then you might as well use all of it! And BitLocker is there and at least supported. I say mostly, because it comes with the OS, which costs money. You could secure information with high confidence, and, it’s probably the reason Microsoft’s BitLocker is mostly free. It was a way to access important technology without it being behind a pay wall. This was a staple of the internet, something we all took for granted. I have to admit I was truly shocked when TrueCrypt went offline.
0 Comments
Leave a Reply. |