Be Your Own VPS: Part 3 – Remotely Configure the Hyper-V Server


Written by:

Greetings internet people, and thanks for
tuning in. I am Alaska Crypto Guy and this video is part
of my Be Your Own VPS series. In the previous video, we completed the local
configuration of our Hyper-V server from the command line and PowerShell on the server. Today, we will remotely connect to and complete
the configuration of that server from another Windows 10 computer. Before you begin, please check this video’s
description and make sure you have completed all steps listed in the “Before You Begin”
section, or else you may encounter problems. Boot your Windows 10 computer and log into
it with the same user account and password you entered on the server. In order to remotely manage another Server
in Windows 10, you need to install the Remote Server Administration Tools or RSAT. RSAT is available as a free download from
Microsoft for builds prior to 1809, but as of the October 2018 Update it is included
as a set of “Features on Demand” which may easily be installed. If you have not yet upgraded to the October
2018 build of Windows 10, then you will need to download RSAT from the Microsoft web site
and install it. If you have already upgraded, then installation
will be different. Search for “Manage Optional Features”
in the Start Menu and open it from the search results. Then click the “Add a Feature” option
and click “RSAT: Server Manager” to install the Server Manager app. This will take a few moments to download and
install. After installation completes, exit out of
all windows. Search the Start Menu for “Server Manager”
and you’ll notice the Desktop App come up in the search results. Because we will be using Server Manager frequently,
let’s Pin it to the Start Menu. Before we will be able to add the server to
Server Manager, we must enter a couple more commands into PowerShell. Launch a PowerShell prompt as Administrator
by right clicking the Start Menu and selecting the same. Then enter the following commands into the
prompt exactly as displayed. These commands tell your Windows 10 computer
to trust the Hyper-V Server despite the fact that they are not both members of the same
Windows Domain. Choose YES to accept both requests after executing
the first command. You should see “WinRM firewall exception
enabled” if everything worked properly. If it did not, it is probably because one
of your network adapters is set to Public mode and needs to be changed to Private before
you can enable WinRM Quickconfig. You can see more on troubleshooting this problem
in the description. The second command adds the server to the
list of Trusted Hosts. I find it beneficial to include both the server
Name and the IP address in the list. Adding the IP address can be useful in case
you have any DNS issues and make it possible for you to connect to the server when you
might otherwise not be able to. When the command is successful you will see
the server added to your list of TrustedHosts. You may then exit out of PowerShell. Next, we will add the server to Server Manager
and create a Data share to store our virtual machines. Click to launch the Server Manager app from
the Start Menu. Click to dismiss the nag message Microsoft
decided to include in Server Manager. You will notice that this Server Manager does
not have any servers listed. To add ours, Right-Click on “All Servers”
and choose “Add Servers”. Then open the DNS tab, and enter your server’s
name. Mine is Hyper-VPS, and click the “Search”
icon. Your server should show up in the list. Click once to add it, then click the “add”
triangle to the right to select the server and then click “OK” to add it and the
Server Manager will begin to inventory the server to determine which roles and features
are installed on it. If you have not already prepared a data volume
on your server, click on Disks to see a list of hard drives which were detected on your
server. On this server we have a 2 terabyte hard drive
and a 240 gigabyte solid-state hard drive. Your virtual machines will perform much better
if you can store them on solid-state hard drives, but since 240 gigabytes is not enough
room to store many virtual machines, I will create my data store on the larger hard drive. Right-click on your preferred hard drive and
choose “New Volume.” This will open the New Volume Wizard which
will walk you through the configuration of the new volume and will end with you selecting
a Drive letter to mount the new volume to. Give the volume a meaningful name; I prefer
Data, and click “Next” and “Create” to create the volume. This will take a few moments. When the volume is created, I find it easiest
to share the folder from the command line of the server itself rather than the Shares
section of the Server Manager. Open a Remote Desktop Connection from the
Start Menu and use it to connect to your server by name or IP address. Enter your credentials and click “Yes”
to ignore certificate errors and connect to the server anyway. This message occurs because we are using a
self-signed certificate instead of one we bought from somebody. It is not a problem. The command prompt on your Hyper-V Server
will be set in your user’s home directory. Switch over to the drive letter of the new
volume you created by typing its drive letter followed by a colon. Then press ENTER. If you type “dir” and press ENTER you’ll
see that the volume is empty. Now let’s create some folders. The command “md” can be used to make directories. First create a folder named “Hyper-V”. Then create a folder named “Hyper-V Backups”. Lastly, create a folder named “Install ISOs”. Quotation marks are required around the folder
name only if the folder name has a “space” character in it. Type “dir” and press ENTER again to confirm
that the folders were created correctly. If they are, we will now share the entire
volume. Enter the command which is displayed on the
screen. This command specifies the name of the share,
it’s location, and access permissions. We are sharing the Data volume with your new
administrator account and giving you full and exclusive permission over the volume. You may then close the Remote Desktop Connection
to the server and return to Server Manager. Your newly created network share will now
show up in the “shares” section after you refresh the server settings. You may now close Server Manager. It is now a good time to map the Data share
to a drive letter on your computer so click to open This PC and then select “Map network
drive” from the “Computer” tab of This PC. Select a drive letter which you would like
to map the Data share to, and then type the path to the data share you just created, make
sure the Reconnect at sign-in option is checked, and click “Finish” to complete the process. You can now easily navigate the Data share
as though they were folders on your own computer. Because it will not be long until we are ready
to create our first virtual machines, I’m going to copy some ISOs from my source folder
into the “Install ISOs” folder of the Hyper-V Server. If you do not have any ISOs, go ahead and
download Ubuntu 16.04 Desktop edition and put the ISO in that folder because we’ll
use it to create a virtual machine in a later video. While those are copying, I’m going to go
ahead and install the Hyper-V Manager. As you start typing “Hyper-V” into the
Start Menu, Windows will figure out that you want to install it, so choose “Turn Windows
features on or off” and wait for it to load. Then select “Hyper-V” from the list of
features and install it. The Platform is not required because this
is not a Hyper-V Server, so we will only need to install the Hyper-V Management Tools. Wait for the install to complete, then pin
Hyper-V Manager to the Start Menu as well. Adding the server to Hyper-V Manager is very
similar to when we added it to Server Manager. Right click Hyper-V Manager and select “Connect
to Server…” then type the name of your server and press OK. If you’ve done everything correctly, the
server will be added to the list on the left side of the manager. There are only a couple of configurations
left before this server is ready to go. Start by entering “Hyper-V Settings” from
the Actions menu. By default, Windows Server wants to store
the virtual machines on the same partition as the operating system, which is not a good
idea. Let’s go ahead and Browse to the Hyper-V
folder that we created on the Data share, and then, put them in the sub-folder named
Virtual Hard Drives. If you didn’t create the sub folder earlier,
it is not a problem. Just select the Hyper-V folder and then choose
“select folder.” Then on the server settings page, type in
the name of the sub folder and select apply. Apply will create the folder if it does not
already exist. Next, choose “Virtual Machines” and browse
to the Hyper-V folder to store your Guest Operating systems’ configuration files there. That’s all we need to do with the Hyper-V
Settings. Lastly, in order for our virtual machines
to communicate with the internet, we need to create a Virtual Switch which will allow
our virtual machines to share one or more network adapters with the server operating
system. Choose “Virtual Switch Manager” from Actions
and create a new External virtual switch. You can rename the virtual switch but you
do not need to. Click OK and then YES to allow the reconfiguration. It will take a moment, and when it is done,
you have completed the necessary remote configuration of your server. It is now ready for you to create some virtual
machines and start putting them to good use. Close out of Hyper-V Manager for now; you
have reached the end of this video. In the next video, we will create our very
first virtual machine and begin its installation. If you have stuck with me through these first
several videos, this is where it will begin to pay off and you will see that magic that
you can accomplish with a virtualization server. Until then, as always, remember: Don’t be
afraid to push buttons. You never know what might happen if you do!

4 Replies to “Be Your Own VPS: Part 3 – Remotely Configure the Hyper-V Server”

  1. Yazuki says:

    I have 1 RAm and 270 Of Graphis is it enough ?

  2. Richard Smith says:

    HI, i have followed everything buy i cant get it working it keeps saying online verify winrm 3.0 is installed on the server manager window

  3. Juanma Otero says:

    Perfect, after a "little" work get finished configuration. I have had problems connecting with RSAT. Reinstalling a few times Hyper-V solves the problem. And without installing the updates. Sometimes the system shows updates, sometimes not. So when all is ready i will try again with the updates. Let´s start part 4.

  4. Juanma Otero says:

    What RAID system are you using? Thanks

Leave a Reply

Your email address will not be published. Required fields are marked *