Checking

Virtualization

First check your CPU
can handle virtualization. This is the case of most processors today, but you will still have to activate it in your
BIOS.
How to activate will depend on which BIOS[VB1]you have but, in general, you will find the words "Intel Virtualization Technology"
(in case of an Intel processor).

SLAT

Your processor must also be able to manage the SLAT (Second Level Address Translation). To verify that your CPU
can handle this technology, Mark Russinovich helps us again.

This screen allows you to give a name and size to your datastore. If you have multiple volumes, you can also decide on which volume you want to create
your datastore.

Here, you can also choose whether or not you want to do "Thin
Provisioning".

Quick reminder on what
Thin Provisioning is:

It is possible to allocate storage on demand. The aim is to maximize the use of your storage. It therefore reserves only
what we actually use. The second underlying mechanism used by Thin Provisioning is called the over-subscription. This is a mechanism that allows a server to view more storage space than has been physically reserved.

Now, we can create the iSCSI target. Using the iSCSI Target service will give our future virtual machines the
illusion to that the disk is a local drive. The result will be a virtual disk stored on our Synology NAS.

Remember that the iSCSI
protocol encapsulates the SCSI protocol in TCP/IP packets.
The iSCSI protocol uses client-server architecture. In side A, we
have the client, also called "initiator", and in side B, we
have the server named "target". Usually, the target is actually
a storage device that has an iSCSI interface. This part is the one that the NAS emulates.

Create a "local" drive from a LUN created on the NAS

The title is not entirely accurate. What we will do here is use the functionality of the provision of a target through:

the server (our NAS) on which we have activated a target
that is mapped to our LUNs

iSCSI client also called "initiator". The advantage
is that, again, in Windows 8, it is native to the OS.

In other words, this will allow us to give the illusion that our Windows 8 has a new local disk but it is simply a LUN mounted
on the NAS. One benefit of this is a shared storage on RAID10 configured on the NAS.

You can accept the warning alerting you that the service is required to be started in order to benefit from the features of the
initiator. Clicking "Yes", you automatically configure the service to "Automatic startup". Nice.

Fill in the IP address of your NAS in the field
"Target". Then click on "Quick Connect ...".

If everything goes well, you will see your Target.

Some of the smart guys among you will notice that the IQN is the same as the one you see on the Synology as target. Good news.
Press "Done".

Ok, now you can see the connection in the active window. Click "Connect".

If you have followed me for the activation of the authentication with CHAP protocol, click on "Advanced", we
need to configure it.

It's very simple, you just need to check the "Enable CHAP log on" box, encode the name you
have chosen and the "Target Secret." This is actually the "secret" that the client and the server each possess. Indeed, the CHAP is basically sending a "challenge" that can be raised through the secret represented by the "password"
encoded previously on the NAS.

Click "OK".

And "OK".

"Voilà", our target is now connected. This is perfect, we will be able to detect our new drive in Windows.

Let's go back to the lower left corner of your screen and click on "Disk Management".

The disc should appear that way. If it is not
[VB1]online, you need to right click on your drive and click on "Online".

Then right click in the "Unallocated" zone and "New Simple Volume".

The rest is no more than a classic format disk in Windows.

And here are your efforts rewarded! You now have a new disk seen by your OS as a local drive.

Create a vSwitch

In order to connect our future virtual machines to a network, we will create a virtual switch on which the virtual machines will
connect.

From the Start menu, you can see the new tile "Hyper-V Manager". Click on this tile.

Here is the Manager interface. The name "NODE1" is the name of my Windows 8 computer.

Click "Virtual Switch Manager".

The type of switch depends on what you want to do with your virtual infrastructure. My goal here is to put my virtual infrastructure in my physical
LAN. My virtual machines will be accessible to the physical machine on my network. This is the Bridged Mode in VMWare. It is the External mode in Hyper-V.

This is not necessarily required and will depend on what you want to do.

The Switch "Internal" is the same as the Nat Mode in VMWare.
VMs see the physical node but do not have access to the network node.

Finally, the Private type switch can be used if you want a sub VMs network. This means that VMs can see other VMs but cannot see the node (your
physical machine) or the physical network.

A message warns you that you computer may lose its network connection. Do not worry - just click on Yes.

Simply enter a name, select your network card and "Ok".

The switch is created and by visiting the network center, you can see the change.

Create your first virtual machine

Let’s start the creation of a VM itself.

Click on your node and "New" > "Virtual Machine".

Name your VM. In my case, it will be a domain controller. We
will use our storage space created in step 3. Click "Browse ...".

Here we have created on the disk G:\ (which is the LUN on the NAS) the tree folder Lab>VMs. You are free to do what you want, then click "Select
Folder".

You can, at this stage, assign to the VM an .iso containing
the image you wish to install. This is where I point my ISO Windows Server 2012. You can also provide a .vfd (floppy disk) or install via the network (with a PXE server,
for example).

Click on "Finish".

Then, you have to start the VM with the start button in your Hyper-V Manager.