As I found out today, Hyper-V Server 2012 R2
(the FREE version!) does support Bitlocker! Hooray!

Here is how to set it up:

1. You have to install the Bitlocker feature.

2. If you don’t have a TPM you will need to allow the use of Bitlocker without a TPM via GP. Either in your domain or via the local group policy snapin on the machine in question. To do that edit the following group policy key to “Enabled”.
Since we are on the Hyper-V Core machine, you have to setup remote management first, and make use of the MMC -> Group Policy Object editor.

Make sure to check “Alllow BitLocker without a compatible TPM


3. Encrypting a drive with Bitlocker requires that a system administrator provides Bitlocker with one or more security protectors to protect the drive. I will be using a password, however one can also use a USB key and other methods to lock and unlock the Bitlocker volume.

You should be prompted to enter you self defined password twice and you should receive a randomly generated recovery key printed on the screen. You should copy this down immediately so it’s not lost as it will be the only way to recover the volume if the user password is forgotten.

HINT: To have the recovery key automatically saved to a USB thumb drive add the following to the end of the command:

Where X: should be the drive letter of the USB thumb drive.

Once the protectors have been put in place we can start the encryption of the volume with the following command:

After the command is executed you will be prompted to restart your computer to complete the Bitlocker drive test. The test checks that you are able to log in to your system with Bitlocker enabled. Once the computer has restarted and you have made it back into Windows Bitlocker should start encrypting the drive.

You can keep an eye on the status of the encryption process with the following command:


Since managing it remotely in anon domain environment is a pain in the neck and I’ll have to setup quite a few servers in the next couple of weeks, here a quick ‘how to’ mange Hyper-V Server 2016 remotely.


1. Run

2. Configure Remote Management + ping (Opt. 4 -> Opt. 4 -> Opt. 1)
3. Enabled Remote Desktop (Opt. 7 -> e -> Opt. 2)
4. Run this command to allow RDP through the server’s firewall:

5. Launch Powershell and execute this command:


1. Add an entry to the hostfile as you can not add a Hyper-V server via IP

2. Run -> dcomcnfg, right-click on ‘My Computer’ -> Properties -> COM Security Tab -> Access Permissions -> Edit Limits -> Anonymous Logon -> Allow ‘Local & Remote’ Access


4. Install the RSAT Tools for your Operating system. Open the Server Manager and add the Hyper-V host as a server.

5. You should get a permission error, run the following command:

Now you should be able to remote manage / create / edit your Hyper-V Server.


Alright so one of our customer’s shared drive broke, we were able to restore it and such, however the needed rights were gone. I found a cool nifty tool called “SubInACL” to help me out. The default install is in

The syntax for SubInCAL is like so:

So in my case I used:

The <access>parameter follows this list:

F : Full Control
R : Generic Read
W : Generic Write
X : Generic eXecute
L : Read controL
Q : Query Service Configuration
S : Query Service Status
E : Enumerate Dependent Services
C : Service Change Configuration
T : Start Service
O : Stop Service
P : Pause/Continue Service
I : Interrogate Service
U : Service User-Defined Control Commands

To get all the sub-directories you can use the switch ‘/subdirectories

Such an easy command saved the day!