![bitlocker network unlock server 2016 bitlocker network unlock server 2016](https://1.bp.blogspot.com/-geK81YcoXMM/XjAQUutzVKI/AAAAAAAACzA/Yx8oq4UEH9MhGV1OJtNo7GnIOdmhNJmEACLcBGAsYHQ/s1600/ManageBitLocker6.jpg)
Last packet that contains the final intermediate key that combines with key from TPM and unlocks the OS volume and allows for the network boot.
#Bitlocker network unlock server 2016 Pc
Log, which unlocks the client PC correctly.įe80::5c29:1256:285c:7ba being the Windows Server 2016 on VirtualBoxįe80::ec4:7aff:fec9:bb42 being the client, highlighted message is the (Manualįor Bitlocker Network Unlock, says that DHCP has to be on different server anyway) One thing to note is that DHCPv4 service is running on separate Linux server and IP's are being distributed based on the MAC addresses, but that shouldn't be a problem in this case. It indeed arrives fine and I can sniff it with Wireshark. I also tried putting hub right before the test client PC, connect notebook to it and check if the last unlock packet from server actually gets to the client and doesn't get dropped somewhere on the way. I used Wireshark to log what's going on, on server side, and even on Wireshark it seems to look like everything is working correctly, I'm kinda stuck at this point. IPv4 logs zero errors and also logs info about getting NKP from client and sending it back to client properly, yet fails to unlock.
![bitlocker network unlock server 2016 bitlocker network unlock server 2016](https://www.rootusers.com/wp-content/uploads/2017/03/install-bitlocker-network-unlock-768x547.png)
Know what those mean) and then logs info about getting keys and sending them back to client in next step. I went trough WDS logs on the server, activated debug logging and with IPv6 it logs some errors (don't I'm running Windows Server 2016 in VirtualBox, the server is running AD,DNS,WDS services and I got Bitlocker Network Unlock configured, it works ok via link-local auto configuration IPv6, but for some reason it doesn't work when I disable IPv6 on the serverĮverything seems to look ok, yet via IPv4 client fails to unlock the OS drive and boot, I will get Bitlocker blue screen prompting me to enter PIN manually.