Hyper-V is Windows Server Virtualization software. Since it’s free and effective, it’s not a bad choice.
First, check THIS LIST to see if you CAN enable virtualization in the BIOS to be compatible with Hyper-V.
The R200s (and others that come configured with non Xeon processors) may be tricky if you’re running something other than the Xeons. Some users say they can and others say they can’t and Dell specifically says you can’t.
Once you figure out if your server is capable, you’ll need to enable virtualization in the BIOS. This is going to be under options for the processor.
Once enabled, log back in and perform the following:
1. Start Server Manager by using Start | Administrative Tools | Server Manager.
2. From Server Manager, click Add Roles to launch the Add Roles wizard.
3. Choose the Hyper-V role (see screenshot below)
4. Follow the on-screen instructions of the wizard until the Create Virtual Networks page is reached.
5. To allow virtual machines to communicate on the network, at least one virtual network bound to one physical network adapter must be created. Virtual networks can also be created, modified, and deleted at any time using the Virtual Network Manager. It is considered a best practice to have at least one physical network adapter that does not have a virtual network associated with it to be used for host server management.
6. Continue through the rest of the pages of the wizard.
7. Restart the system when prompted at the end of the Add Roles wizard.
A Hyper-V Manager MMC console may be used either locally or remotely to manage the virtual environment on the server.