Many words were said about NFS (Network File System), but what exactly NFS can give us? In general, NFS used as the ISO library or just simple network file share with easy access from any Windows or Linux based machine. However, starts from NFS 3.0 protocol can give us the good performance and can be as the shared storage for ESXi or any Linux based Hypervisors. In this article, I will create the NFS share on the Windows Server 2016 and then mount NFS share on the ESXi 6.5 and will create the VM on it.

Nowadays, every company is doing its best to protect its data, which is pretty much its most valuable asset. As you know, data is vulnerable to unauthorized access and that’s when Microsoft BitLocker saves the day. BitLocker is the encryption technology from Microsoft, which makes possible to encrypt the Logical Volume on the transparent blade-based level (not physical disk). In this article, we will see how to encrypt Cluster Shared Volume (CSV) using Microsoft BitLocker to protect your data against unauthorized access.

In the previous article, we have created a free SMB3 file server. I decided to proceed with the testing of Microsoft Server Hyper-V 2016 free version possibilities. In this post, I will try to create Highly Available devices with VSAN from StarWind and then create a Microsoft Failover Cluster to make a Highly Available File Server. We are using 2 servers with Microsoft Hyper-V 2016 added into a domain (Hyper-V-1; Hyper-V-2). Client node with Windows Server 2016 (2016-client-test).

This series of articles will guide you through creating a free SMB 3.0 file server in Microsoft Windows Hyper-V 2016. Hyper-V 2016 is an absolutely free GUI-less version of Microsoft Windows Server for virtual machines. Hyper-V 2016 Server has been specifically developed and created only for virtual machines. According to Microsoft EULA, StarWind does not recommend repeating the steps below, because this process is a violation of the license agreement. The reason why we can create SMB File Share on Hyper-V 2016 is simple: all Windows servers require SMB 1/2/3 to work, and Hyper-V 2016 is not an exception. But it does not mean you should create any unsupported Microsoft services on GUI-less Hyper-V 2016.