Management hyper v. Installing and configuring hyper-v server for those who see it for the first time
Good afternoon. Thanks to my site, I constantly poke around in the operating system and, of course, over time I began to look for a way so that I could write instructions, but at the same time make less changes to the operating system of my work computer ... The solution came to an elementary one - a virtual machine. It is an emulation of all (or almost all) of the working operating system that runs on your operating system. I tried VirtualBox, VMware Workstation and Hyper-V ... VirtualBox is free and not as user-friendly as the other two. VMware Workstation is great in all respects, but it comes at a premium. Hyper-V is a completely balanced virtual machine that migrated from server operating systems to Windows 8 and simply needs to be turned on for access. Therefore, the choice fell on the latter: simple, free and tasteful. By the way, I have Windows 10 Professional licensed, but I got it for free thanks to the Windows Insider program (six months of suffering with bugs and a license in my pocket)).
I will probably warn you right away that when you enable Hyper-V components, you will not be able to use other virtual machines. So, let's begin:
Right-click on the corner "Start" and select "Programs and Features".
In the left pane, select "Turn Windows features on or off"
Now open the "Start" menu → "All Programs" → look for the "Administration Tools" directory and find "Hyper-V Manager" in it.
By launching it, we will see the virtual machine management console, I already have one created machine that hosts a music bot for my TeamSpeak server. But now we are creating another car to show how this is done. But first, let's immediately create a "Virtual Network" so that our VM has the Internet. To do this, click on the computer name in the left column, and in the right, select "Virtual Switch Manager".
I am adding this paragraph two months after writing the article. This is because, below I described an easier way to connect a virtual machine to the Internet, but I myself use a slightly different one. The difference in them is that in the method described here, the VM gets the main access, and the computer works after it and this is not correct, but it is easier to configure. If you use a computer not only for running virtual machines, select "Internal" → "Create virtual switch" and put a tick on the "Allow identification" item. Internet access is configured using.
On the left, select "Create a virtual network switch", on the right "External" and click "Create a virtual switch".
Enter a name for the network, in the "External network" section, select your network adapter and click OK.
Now we create a virtual machine. Click "Create" - "Virtual Machine".
Opens " New virtual machine wizard“, On the first window, just click“ Next ”.
We indicate the name for the future virtual machine. If you wish, you can also change the storage location of the virtual machine, I changed the location in the settings so as not to clog up the SSD and all virtual machines are stored on one of the hard drives. Click "Next".
Everything is simple here, we read what is written, if you have a motherboard without UEFI support or you are going to install a 32-bit system, then we select the first item, if the conditions for using the second generation coincide with your capabilities, we choose the second generation. I want to install 32bit Ubuntu for one of the following articles, so I choose the first generation of Hyper-V. Click further.
The amount of virtual memory. In the case of Windows, preferably 2-3 GB for 32-bit systems and 3-4 GB for 64-bit systems. More for a virtual machine does not make sense, and less can affect the operation of the system. You can also use "Dynamic memory", in this case the VM will be allocated as much memory as it needs.
We select the volume of the hard disk of the future machine and the storage location for its file. Under the needs, for Win 8-10 you need at least 25GB. I am taking Ubuntu with a large margin.
Continuing the series of articles on virtualization, today we will talk about configuring a network in Hyper-V. We will focus on theory, namely, we will analyze how virtual networks are arranged and how they interact with real ones. Because, as practice shows, many administrators, in the absence of simple and understandable materials on this issue, are forced to master the network setup in Hyper-V by the "scientific poke" method.
On the one hand, there is nothing difficult in configuring networks for virtual machines, on the other hand, many are beginning to get confused in all these adapters, having difficulty understanding where is the real one, where is the virtual one, and how they differ from each other. Let's try to be clear.
Responsible for configuring networks in Hyper-V Virtual Switch Manager, if we open it, we will see the following picture:
Private network
A private network differs from an internal network in that a virtual switch can only be connected to virtual machines and isolated from the host.
This type of networks can also be used for educational and research purposes, as well as for creating isolated sections of the network, for example, the DMZ.
In this case, communication between the external and private networks will be through one of the virtual machines, which must be connected to both networks.
As you can see, Hyper-V gives the administrator a very flexible and powerful tool that allows you to create and manage very complex network configurations.
Back in Windows 8, the Hyper-V virtualization technology appeared, previously available only in Microsoft server operating systems. This solution looks better than the Windows Virtual PC that was included with Windows 7. Today I will tell you how to create a virtual machine in Windows using Hyper-V, as well as configure the Internet, local network and file sharing in it.
In addition to Coreinfo, you can use a proprietary Intel utility (AMD has a similar one).
You can also look at the virtualization technology support table on your processor manufacturer's website: Intel | AMD.
Enabling the Hyper-V component
Hyper-V is an operating system component that is initially disabled. Advanced users can enable it with a single PowerShell command:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
If you prefer a graphical interface, press Win + R, type OptionalFeatures and press Enter.
In the window that opens, check the Hyper-V box.
One way or another, the component will become available after a system reboot. Among the problems with the installation in Windows 8 RP, a cyclic reboot was noticed so far due to the fault of the USB 3.0 controller drivers, which on some systems was solved by disabling USB 3.0 in the BIOS.
Creating and configuring a virtual machine
Press Win + R, enter virtmgmt.msc and press Enter to open Hyper-V Manager. From the menu Actions choose Create – Virtual machine.
The wizard for creating a virtual machine is extremely simple, but I will note some points for those who like detailed instructions with pictures. I will skip the network configuration step now, since I will analyze this issue in more detail.
The default location for virtual machines is folder ProgramData, but it can be changed.
If you already have a virtual disk in VHD format, you can connect it. By the way, I did just that, using the disc I created earlier for the Virtual Box.
When you specify an existing VHD, the wizard will skip the step that specifies the media for installing the system.
However, you can specify the ISO path later by opening the virtual machine settings in the main Hyper-V Manager window.
Launching a virtual machine and installing Windows on it
Here, too, everything is simple, but a little unusual for those who have not previously encountered Hyper-V.
In Hyper-V Manager:
- to start the virtual machine click "Start"
- to interact with it, click "Connect" or double-click the thumbnail of the machine
When the Windows bootable ISO image is specified in the machine parameters, you will see the familiar Press any key to boot ... On the screen, you can do it yourself, but if you need step-by-step installation instructions, they are available on OSZone for Windows 7 and Windows 8.
If the operating system on the physical machine is newer than the one installed on the virtual machine, it is recommended to update the integration components (thanks, Artem). To do this, connect to the virtual machine in the Hyper-V manager, press Ctrl + I and run setup.exe.
Setting up Internet access and local network
The instructions in this section are only necessary if you are not satisfied with the Default Switch that appeared in Windows 10 1709, which cannot be deleted or renamed. When using the Default Switch, when the host connects to VPN, the virtual machine also uses the VPN. This is one of the main differences from an external switch, the creation of which I will describe later.
On the menu Actions choose Configuring virtual switches... A window will open in which you can create a switch of one of three types. To enable your virtual machine to access the Internet, create external switch.
Now you need to set the name of the switch and select the network adapter if you have more than one. I use a wireless network at home, so I chose a Wi-Fi adapter.
It remains only to specify the created switch in the parameters of the virtual machine's network connection.
Now, with Windows installed, you will have an Internet connection and a local network between the physical and virtual machines.
In the picture above, you can see:
- on the left - the result of adding a virtual switch to Hyper-V on a physical machine, i.e. network bridge and virtual adapter
- on the right - Internet access and connection to a local network in a virtual machine
As you can see, setting up the Internet and local network is not so much difficult as it is unusual for users of Microsoft client operating systems.
Sharing files between physical and virtual machines
As you work with a virtual machine, you regularly need to copy files to it from a physical one, or vice versa. I will describe several ways to solve this problem.
Shared network folders
This method works in all editions of Windows 10. Since we have a local area network, we can use shared folders to exchange files. In fact, the instructions below boil down to the basics of creating shared folders.
Access from virtual machine to physical
A picture is worth a thousand words, as the Americans say.
The figure shows the explorer of the virtual machine (VIRTUAL-PC), from where the physical machine (VADIK-PC) is accessed. Once you enter your account credentials, you will have access to its profile.
You might want to make a shared folder located on a physical machine outside of your profile. To do this, it is enough to use standard sharing tools, but I will explain this process using the example of accessing an arbitrary folder of a virtual machine.
Access from physical machine to virtual
Let's say there is a folder at the root of the virtual machine disk Shared... Right click on it and select General access – Individual people(or Specific users in Windows 7).
Now you can open a shared folder over the network in Explorer, including by entering an address in the address bar like \\ ComputerName \ FolderName.
Remote Desktop Connection of a Virtual Work Machine
In Hyper-V, copy-and-paste file sharing is not possible between a physical machine and a virtual machine. You can only paste the text copied on the physical machine using the Ctrl + V keyboard shortcut. However, once the virtual machine has started, you can connect to it using RDP instead of opening it from Hyper-V Manager. This method works in Pro and higher editions.
Actions on the virtual machine
First, you need to enable remote desktop connections on the virtual machine in the system properties. Press Win + R and run:
RUNDLL32.EXE shell32.dll, Control_RunDLL sysdm.cpl, 5
Then enable the connection as shown in the figure.
It remains only to find out the IP address of the virtual machine with the command ipconfig
Actions on a physical machine
Press Win + R and enter mstsc and expand the login options.
In the window that opens:
- Enter the IP address of the virtual machine (required).
- Specify the name of the user whose account will be logged in.
- Turn on remembering credentials.
- Save the connection parameters.
You can also set on the Display tab a resolution lower than that used by the physical machine.
Now you can exchange files between physical and virtual machines using the usual keyboard shortcuts Ctrl + C and Ctrl + V.
Finally, I would like to virtualize a few of Denis Diaghilev's recommendations for working with Hyper-V.
Use RDP to connect to virtual machines.
This will not only allow you to exchange files between the physical and virtual machine by copy and paste, but it will also save system resources that vmconnect consumes when connecting to a virtual machine in Hyper-V Manager or from the command line.
If you plan to regularly use RDP to connect to various virtual machines, pin the program to the taskbar. Then the list of cars will be saved in the jump list.
Be careful with pictures
With Hyper-V, you can take snapshots of a virtual machine using differential disk technology. However, the logic of the snapshots is practically the opposite of what a person expects from it, who has never stepped on a rake.
Alexander Kosivchenko (MVP for virtualization) in detail, albeit somewhat chaotic, described the principle of operation of Hyper-V snapshots on Habré.
Use virtual machine import if needed
The import will be more interesting for IT professionals, but I happened to use this function by accident. After creating the virtual machine, I renamed the drive letter on which it was stored, after which the Hyper-V manager lost it.
Looking around in the snap, I saw the import option and instantly rebuilt the machine.
Moreover, I did not even suspect that the actions I performed became possible only due to the appearance of a new feature in Hyper-V :)
Hyper-V vs. Virtualbox
As I dealt with Hyper-V, I involuntarily compared Microsoft's client operating system solution to Oracle VirtualBox.
From the point of view of typical tasks of home users (testing the installation of the system, getting to know it, checking the operation of applications), these solutions practically do not differ from each other. But VirtualBox can be used in Windows 10 home editions, while Hyper-V is not available there.
VirtualBox does not have such stringent hardware requirements, and its graphics capabilities are even broader, since there is support for 3D hardware acceleration (although I have never used it).
As for the graphical interface, this is purely a matter of taste. Probably, the hypervisor that came from the server OS looks more ascetic, but the parameters and settings of virtual machines are generally very similar.
The presence of Hyper-V on Windows will primarily delight IT pros who are accustomed to this technology. For home users, this is a good opportunity to take advantage of the built-in system tools and expand their horizons by joining Microsoft server technologies.
Survey
I got acquainted with virtual machines in 2004 when I started doing Windows autoinstallation. Since then, they have become an integral part of my daily work, including testing system settings, programs, etc.
In comments tell us which virtualization solution you are using and for what purpose!
I would like to thank Denis Diaghilev for his help in preparing this material. One of the benefits of the MVP program is getting to know the best Microsoft technology experts. This means that privately you can get competent advice on any issue;)
Denis also kindly offered his help in conducting the discussion. Therefore, if you have any technical questions about this article, you can count on qualified answers.
I want to specifically emphasize that
Today we will learn about how to install and configure the hyper-v server hypervisor from Microsoft, as well as about some pitfalls and ways to avoid them.
The reason for writing this article was the material of this post. This post is more like a cheat sheet if you have already worked with this hypervisor. A beginner will have to deal with a bunch of nuances and dig up a lot of forums in search of answers to non-standard questions.
For beginners, the article will describe in as much detail all the actions and their meaning as possible, so that they have the opportunity to start experimenting and come up with something of their own. For the more savvy, the article is divided into logical blocks and sub-blocks so that you can quickly find the information you need.
Description
MS hyper-v server is a stripped-down version of MS server 2008 R2 in Core mode (i.e., in fact, there is no graphical interface) with the hyper-v role installed and nothing more. According to Wikipedia, hyper-v server is distributed free of charge, which, coupled with convenient management and integration with MS products, makes it a very attractive hypervisor. In addition, it has fairly high performance indicators, which means that the resources of the host machine will be spent on the operation of the services we need.
Installation
Before starting the installation, you must ensure that your processor supports Intel VT-x or AMD-V hardware virtualization technologies.
First, you need to download the hyper-v server 2008 R2 distribution kit from the Microsoft website (you do not need to register). Next, burn the image to a DVD or make an installation flash drive. Insert the disk / flash drive and boot from it.
Hyper-v server - choosing the language of the installation wizard
The installation window prompts us to select the language of the operating system. We choose English, further in the article it will be explained why exactly it.
Hyper-v server - select OS language and keyboard layout
We chose English as the language, and it is better to choose Russian as the time format, so that later you do not have to worry about setting up in the command line.
Hyper-v server - choosing the type of installation
We select the full installation (Custom).
Hyper-v server - configuring hard disk parameters
At this stage, the wizard offers to configure the parameters of the hard disk partitions. It is best to create 2 logical drives. The first is to install the hypervisor itself, 15 GB is enough for it. The second is for storing containers of virtual machines (VM). Thus, it will be much more convenient to manage, import and migrate VMs.
We press "Next" and we can rest for a while. During the installation process, the computer will restart several times.
Customization
Basic setup and remote access
After rebooting, the hyper-v server will prompt us to set an administrator password. Since, by default, in group policy ms windows 2008 server r2 there is a requirement for password complexity, you will have to come up with a password with a length of 6 characters or more, which must contain an uppercase letter and a special character or number (for example, "Password1").
As you can see in the screenshots below, the control console is in Russian, although English was selected during the installation, most likely this is from the fact that the Russian distribution kit was downloaded from the official Microsoft website. This will not negatively affect the operation and configuration of the server. If your console is in English, you can do it by analogy, all the settings will be easy to understand.
Hyper-v server - management interface
After loading the working environment, the OS offers us 2 control consoles. Standard command console cmd and console with pre-installed options. First of all, we need to set a static IP address and configure remote server management. In the control console, select item 8.
Hyper-v server - network adapters
The list will list the network adapters. Select the desired one and enter its index. Next, select "1 - set the ip-address of the network adapter". We enter "S" - which means a static ip-address. For example, let's set the parameters:
IP address - 192.168.1.100 subnet mask - 255.255.255.0 default gateway 192.168.1.1 After applying the parameters, we will return to the submenu, where the previously made settings will be listed. If everything is correct, we return to the main menu. Now let's set up remote access. We select item 7, then turn on the remote desktop by entering the English "E". When asked about limiting connections from rdp clients of older versions, select "2" - connect from any clients.
In the main menu, select item 9, and set the current date and time on the server.
Server network name and workgroup
Now let's set up a working group. For the hyper-v server to work, we will not include it in the domain, which somewhat complicates the configuration, but for experiments this is an ideal option. When testing and validating various configurations, it is best to isolate the test machines from the target network.
We select item 1, then "join the working group" by entering "W". Next, set the name of the working group, for example "test". It is very important that the name of the workgroup on the hyper-v server and the PC from which we plan to manage it match. After that we return to the main menu.
It is advisable to set the network name of the server, select item 2 and enter the name, for example "hyper-srv". To apply the parameters, you need to reboot, we agree with the OS proposal.
Further, all settings (such as computer name, workgroup, users, ip-address, etc.) will be used as those described during the installation process. If you have specified your parameters, do not forget to use them.
After rebooting, we can connect to the server using the remote desktop client. Select start -> execute, enter: mstsc In the first field, set the ip-address (in my case 192.168.1.100), connect. The server will request authorization data, enter the username "hyper-srv \ Administrator" and the password "Password1".
So, we are connected, now you need to configure additional remote control parameters. We go to point 4. Now, in order, select sub-points 1, 2 and wait for the end of the setting. After completion, the OS will ask you to reboot again. After completing these settings, we will be able to connect to the server using the mmc console and hyper-v server manager from the Remote Server Administration Tools (RSAT) package. This will be described in more detail later in the text.
Installing RSAT and hyper-v manager
For comfortable remote server management (creating / deleting / importing / configuring VMs, adding / removing equipment, managing users / group policies, etc.), we need to install RSAT on our PC. We will install it on windows 7. First of all, download it from here. In this package, we need the component "Hyper-v Dispatcher" for the mmc console - this is actually the main tool for managing future VMs.
Subsequent settings will need to be made both on the server (SRV for short) and on our control PC (CC).
Configuring users
The first step is to create a user on whose behalf we will manage. Usernames and passwords must match for UK and SRV!
On the SRV - in the control console, select item 3 (adding a local administrator). Set the name "admin" and the password for it "Qwerty1". Let's check if it was added successfully, in the cmd console, enter: net user admin This command will show us that it belongs to the “Administrators” and “Users” groups.
On the UK - launch the cmd console on behalf of the administrator and enter the command: net user admin Qwerty1 / add add it to the administrators group: net localgroup Administrators admin / add for the English version enter: net localgroup Administrators admin / add Check the results again with: net user admin
There is an excellent utility “HVRemote” written by one of the Microsoft employees for configuring users and security groups.
Download the utility and copy the "HVremote.wsf" file to the server. Remember at the very beginning, it was mentioned that you need to select English for the OS? So, for the "HVremote.wsf" script to work correctly, it is necessary that security groups and users are named in English.
A small digression: as it was written earlier, there is no graphical interface in the hyper-v server. This is not entirely true, Microsoft simply cut everything related to Explorer to the maximum, but this does not prevent us from launching applications with graphical windows. For example, you can copy the "total commander" program to the server disk and run it from the console.
Hyper-v server - launching applications
Let's continue on to SRV - open the cmd console, go to the folder with the "HVremote.wsf" file (in the article, the file is saved to the root of the C drive :). We execute the command: cscript hvremote.wsf / add: domain \ account where domain is the name of your server (domain), account is the name of the account to manage. In our case, the command will look like this: cscript hvremote.wsf / add: hyper-srv \ admin
Hyper-v server - script execution
As a result, you should get something like the screenshot. The script added the user to the required groups and assigned him rights.
On the UC side, you need to execute the following commands cscript hvremote.wsf / anondcom: grant cscript hvremote.wsf / mmc: enable
For the Remote Computer Management Console snap-ins to work, you must create exception rules in the server firewall. The first step is to create a rule that allows you to manage logical drives:
Netsh advfirewall firewall set rule group = "Remote Volume Management" new enable = yes If you get an error like "Group cannot be specified with other identification conditions" - try retyping the command manually instead of copying / pasting. Successful command execution result: Updated 3 rule (s). Ok. Next, let's enable remote control of the firewall netsh advfirewall firewall set rule group = "Windows Firewall Remote Management" new enable = yes The result of a successful command execution: Updated 2 rule (s). Ok. Allow access for any console snap-ins mmc netsh advfirewall firewall set rule group = "Remote Administration" new enable = yes Result of successful command execution: Updated 3 rule (s). Ok. Let us use "Windows Management Instrumentation (WMI)" with the following command netsh advfirewall firewall set rule group = "windows management instrumentation (wmi)" new enable = yes Result of successful command execution: Updated 4 rule (s). Ok. Allow the icmp protocol: netsh firewall set icmpsetting 8 Allow access to shared files and folders: netsh firewall set service type = fileandprint scope = subnet If for some reason you cannot connect to the server, try disabling the firewall with the command netsh firewall set opmode disable You may need to create additional access rules.
Now we can use the mmc snap-ins to manage the server (managing services, users, policies, etc.) and most importantly the hyper-v manager. Let's open it up: launch the mmc console -> file -> add or remove snap-in -> hyper-v manager. We select the Action menu -> connect to the server -> another computer. Enter the network name of your server (hyper-srv) in the field and connect.
Hyper-v server - VM control manager
That's all, we have successfully installed and configured our hyper-v server. Now you can safely deploy virtual machines and various services.
Wikipedia - Hyper-v server Useful Console CommandsIn our previous articles, we looked at installing the free Hyper-V hypervisor as one of the Windows Server roles. One of the disadvantages of this method is the need for a license for the server OC, which in some cases can lead to additional costs, at the same time there is a standalone product Hyper-V Server, which allows you to use the hypervisor of the same name without any restrictions, completely free of charge. However, it is more complicated in installation and initial configuration, which will become the subject of our today's article.
First of all, let's clarify the terms. Hyper-V is a free hypervisor from Microsoft that runs on the Windows platform. Initially, only server versions were supported, but starting with Windows 8 (Pro edition or higher) it can also be used on desktop operating systems. Although Microsoft does not explicitly designate hypervisor editions, newer OS generations contain new versions of Hyper-V. Since the degree of integration of Hyper-V into the OS is quite large, you cannot update the hypervisor version separately from the OS version.
If you focus on the version of the configuration of virtual machines, then we can talk about eight generations of Hyper-V, version 8.0 contains Server 2016 and Windows 10 (1607). The most common Windows Server 2012 R2 (and Windows 8.1) have the fifth generation of the hypervisor.
Thus, if we want to use the latest version of the hypervisor, then we need the latest version of the OS. And since Windows licenses do not allow for later OS releases, free Hyper-V might not be all that free. Similar difficulties arise when virtualizing existing environments covered by licenses for earlier versions of Windows or virtualizing UNIX systems. Especially for such cases, Microsoft has released a special product - Hyper-V Server.
Hyper-V Server is a special edition based on Windows Server Core with heavily trimmed features that only provide hypervisor functionality and maintenance. However, contrary to popular belief, there is no difference between Hyper-V Server and Hyper-V as a Windows Server role. They are one and the same product.
When they talk about Hyper-V Server and Windows Server Core, they first of all try to focus on saving resources due to the lack of a GUI, but this opinion is erroneous. When creating these products, the issue of saving resources was the last thing, and it’s silly to talk about any "lack of resources" on the hypervisor.
The main goal of creating Windows Server Core and Hyper-V Server is to reduce the number of running services and system components, which can reduce the attack surface (fewer services - fewer vulnerabilities) and significantly reduce system maintenance costs, for example, fewer reboots when updating the system and less time to install updates. Therefore, it is worth considering the implementation of Hyper-V Server, even if you are not experiencing difficulties with licensing.
Installing and Initial Configuration of Hyper-V Server
The installation image can be obtained from the official website, after registration, if you still did not have a Microsoft account. The installation process is no different from installing other versions of Windows and should be straightforward.
Upon completion, we are greeted by an extremely laconic interface with two open windows: a command line and a text configuration utility.
If you closed the latter, then to call this utility again, simply run the command:
But if you close all windows, including the command prompt window, you may suddenly find yourself in front of a black screen with no system controls at all. In this case, click Ctrl + Shift + Esc(this combination also works via RDP) and using the called task manager, start the process you need, for example, the command line.
Let's move on to setting up. The first step is to configure the network, specify the server name, its membership in the desired workgroup or domain, and enable Remote Desktop. Also, if you want your server to respond to the ping command, then you should go to the item 4) Setting up remote control and choosing the option 3) Configuring the server response to the ping message explicitly allow this action.
Then specify the server update options and install all currently available updates. There is one "surprise" associated with manual installation: the symbols specified in the utility do not work, and in order to download and install all available updates, you need to enter a small Russian letter when prompted T.
After completing the configuration and installing updates, the server should be rebooted. A completely natural question may arise here: what to do next? How do you manage it? To manage the Hyper-V Server, you will need another computer with the Hyper-V management tools installed, and the server itself can be configured from the MMC. To do this, we will create the necessary permissive rules in the firewall. To do this, start PowerShell and sequentially execute the following commands:
Powershell
Enable-NetFirewallRule -DisplayGroup "Windows Remote Control"
Enable-NetFirewallRule -DisplayGroup "Remote Event Log Management"
Enable-NetFirewallRule -DisplayGroup "Remote Volume Management"
Enable-NetFirewallRule -DisplayGroup "Remote Desktop Control"
At this point, the server configuration should be considered complete, you can check the connection to it using RDP and, if everything went well, proceed to the client station configuration.
Configuring the Client to Work with Hyper-V Server
To manage Hyper-V Server, you will need a PC with OS at least Windows Server 2012R2 or Windows 8.1 Pro or Enterprise edition, we will consider further configuration using the example of client OS. Home and 32-bit versions of the OS will not work, as they do not have the ability to install Hyper-V Manager.
Since network discovery and sharing of files and printers on the server is disabled, you need to add a type A record for it on the DNS server, linking the server name and its IP address, or add the corresponding line to the file hosts, in our case it looks like this:
192.168.18.145 HV-CORE-2012R2
If your server is in a workgroup, then you should add the connection parameters to it, otherwise the client will try to connect from under the current user.
Cmdkey / add: ServerName / user: UserName / pass: password
where ServerName- Hyper-V server name, UserName- the name of the Hyper-V server administrator, and password- his password.
If you are using Windows 10, then additionally run the command line (or PowerShell console) as administrator and run the commands there:
Winrm quickconfig
winrm set winrm / config / client "@ (TrustedHosts =" ServerName ")"
where ServerName is the name of the Hyper-V server.
Then run the snap dcomcnfg, via Win + R or from the command line, and expand the tree Component Services - Computers - My Computer... Then, by right-clicking the mouse, select Properties and go to the bookmark COM Security - Access Rights - Change Restrictions and in the window that opens, set for the user ANONYMOUS LOGIN rights Remote access.
After completing these settings, you can start the MMC console Computer management and by right-clicking on the root item of the same name, select Connecting to another computer and provide the name of the Hyper-V server.
Then you can manage the remote server using the familiar set of tools. For most everyday tooling tasks Computer management quite enough, especially considering that most of the settings are done only once.
To use a snap Disk management you will need to start the service first Virtual disk, it can be done right here via snap Services.
The only unavailable rig will be Device Manager, you can customize its operation, but there is no practical sense in this, since it will still work in the "read-only" mode. In addition, in fact, this does not pose a problem: the database of Windows Server drivers is quite extensive and if you have shown reasonable foresight when choosing your hardware, then you will not have to address the issue of drivers at all.
Otherwise, you should turn to the command line tools for working with drivers: 1.6. Hardware Installation and Driver Management (Local)
Finally we come to the most important thing. Let's go to the classic Control Panel - Programs and Features - Turn Windows features on or off and install Hyper-V Management Tools.
After that, you will have at your disposal the familiar Hyper-V management tool that allows you to fully manage the hypervisor. There are no peculiarities in working with Hyper-V server, so we will not dwell on this issue in more detail.
In order to transfer files to the hypervisor, for example, an image for installation, you can use standard shares, say by typing in the address bar of the explorer:
\\ ServerName \ C $
you will be taken to the C: drive of the server.
For example, we created a new virtual machine and installed a fresh version of Debian there, without experiencing any difficulties either when working with the hypervisor or with the virtual machine itself.
As you can see, despite the somewhat more complicated installation and configuration process, Hyper-V Server is a convenient and reliable tool that can also be used completely free of charge.