Installing Hyper-V. Hyper-V on Windows: a guide to creating and configuring virtual machines Installing hyper v server on windows 7

Hello friends, in today’s article we will connect a Hyper-V virtual machine to our Windows 8 and install the Windows 7 and Windows 8 operating systems on it, and also answer all the questions asked by users. By the way, you can transfer your entire physical computer to Hyper-V! Several system administrators I know work only on Hyper-V and have even forgotten what a normal operating system is. At the very beginning we publish several of your letters.

Installing Hyper-V

If you have Windows 8 Pro or Windows 8 Enterprise (corporate) installed on your computer, then you can use the Hyper-V virtualization system or, in simple words, use the virtual machine built into the Windows 8 operating system. It is very easy to use and I have no doubt that you will understand it.

For Hyper-V to work, your processor must support virtualization technology. Before work, be sure to enable the following options in the computer BIOS:

"Intel Virtualization Technology" for Intel processors or "AMD Virtualization" for AMD processors.

I warn you that Hyper-V is primarily designed and intended for IT professionals and is used on servers.

When working in Hyper-V, you will not be able to use a flash drive, sound card, and WiFi; in this regard, it is preferable to use VirtualBox. But I still think that those who read this article know why they need it.

For its operation, the Hyper-V virtual machine makes small requirements:

Windows 8 Pro must be 64 bit.

Availability of at least 4GB of RAM.

Hyper-V connection

Opening Control Panel

and choose Programs

Programs and components. Turn Windows features on or off

Find the Hyper-V partition and mark it with a checkmark and click OK.

There will be a short search for the required files and a reboot.

After the reboot, go to the Metro interface and left-click on the arrow, then select Hyper-V Manager,

The Hyper-V Setup Wizard appears. Click on the name of our computer, then Create And Virtual machine.

Hyper-V Settings

1) Getting started. This wizard will help you create a virtual machine, click Next.

2) Specify a location. We assign a name to the virtual machine in Latin, for example Windows 7. We indicate the location of the files of the Hyper-V virtual machine, since I don’t have space on drive C:, I will check the Save virtual machine in another location checkbox and click browse, then specify the drive D: and Next.

3) Specify the generation. I want to install Windows 7 so I will select Generation 1.

4) Allocate memory. My computer has 8GB of RAM, which means I can safely allocate 2GB of RAM for a virtual machine. Check the box “Use dynamic memory for this virtual machine” and Next.

5) Network setup. We skip this parameter (we’ll set up an Internet connection later) and click Next.

6) Connect the virtual hard disk. Mark the item Create a virtual hard disk. So in the second paragraph Specify location, we indicated the location of the virtual machine files on the D: drive, then by default the virtual machine will offer us to locate the virtual hard disk on the D:\Windows 7\Virtual Hard Disks\ drive.

Friends, the item Size 127 GB does not mean that 127 GB will immediately be “squeezed out” on your D: drive.

Note: A virtual hard disk can be created at the very beginning, that is, before you create a virtual machine, and in this case you can choose which virtual hard disk to create, for example:

Dynamic(grows in volume gradually, according to accumulated data, at first it takes up several megabytes).

Fixed size(immediately requires allocation for the required space; if you create a 120 GB disk, that means you must allocate exactly that much space to it).A fixed-size hard drive is considered to have higher performance.

See the end of the article for more details.

7) Installation parameters. Check the box Install the operating system later. Further.

8) Done

How to set up Internet in Hyper-V

Now let's set up the network. In the main Hyper-V window, click on the Virtual Switch Manager button.

In the window that appears, select what type of virtual switch you want to create. I will select the type - External network. WITH create a virtual switch.

Choose an arbitrary name for the virtual switch. The Wi-Fi network adapter on my computer is from Atheros, so I’ll choose that name. Apply.

Choose Options

A window will open, on the left side of which you can see two sections with different parameters; if you select the parameter you need with the left mouse, then on the right side of the window you can configure it.

Network adapter. In the right part of the window, select our Virtual Switch "Atheros", Apply And OK.

Installation on Hyper-V operating system

Now the actual question is how to install the operating system in a virtual machine. To install a Hyper-V virtual machine, you need to boot it from the Windows 7 installation disk located in the drive or for these purposes you need to use an ISO image with Windows.

, then on the right side of the window using the buttons Up And Down We set the virtual machine boot to what we need:

CD- boot from installation disk or ISO image.

Choose Controller 1 IDE and click on the plus sign, then DVD drive, if you want to boot the virtual machine from the DVD drive, check the item Physical CD and DVD drive: then insert the Windows 7 installation disk into the drive.

Also, to boot a virtual machine and install an ISO image with Windows 7, you can use Windows 7, in this case you need to check the File image item and click the Browse button, in the explorer that opens you need to select the image with Windows 7 and click Open. Apply and OK.

Click Start and the virtual machine starts. Hyper-V is loading from the Windows 7 ISO image. Double-click with the left mouse on the thumbnail of the Hyper-V virtual machine window,

A window will open in which you and I will work. Press any key, otherwise booting from the Windows 7 installation disk will not occur. At the top of the window there are virtual machine settings buttons.

The usual Windows 7 installer dialog box. Next, you can install the Windows 7 operating system on the virtual machine. The whole process is described in detail in our article.

So you and I connected a Hyper-V virtual machine to our operating system and installed Windows 8 on it, the Internet is present on the virtual machine. You can install Windows 8 on it in exactly the same way.

How to create a virtual hard disk in Hyper-V

Friends, a virtual hard disk in Hyper-V can be created not only during the process of creating a virtual machine.

In the main window of the virtual machine, select Create -> HDD

Selecting the disc format. You can choose a new hard drive format, but please note that it is not supported by earlier operating systems before Windows 8

Select the disk type. You can create a fixed partition disk, which is considered higher performance

We indicate the location of the virtual hard disk, if you have little free space on the C: drive, then place the virtual hard disk on the D: drive. Click on the Browse button and select drive D:

Disk setup. If we create not a dynamic expandable virtual disk, but a virtual disk of a fixed partition, then we must specify the exact size of the disk; if we specify the size of 127 GB, then this is exactly how much our virtual disk will occupy on the D: drive. Make sure you have enough free space on your D: drive.

note per parameter Copy the contents of the specified physical disk, you can use it if you want to transfer your physical computer along with all the settings to a virtual machine!

The virtual hard disk has been created. When creating a new virtual machine in step Connect a virtual hard disk we can check the box Use an existing virtual hard disk, then click Browse and specify the location of the virtual disk -D:\New virtual hard disk.vhdx

Blue screen when creatingvirtual switch in Hyper-V

Friends, several times I had to deal with the fact that in the new Windows 8.1 operating system in the Hyper-V virtual machine, when creating a virtual switch, the operating system went to a blue screen with the error:

The problem seems to be caused by the following file: fwpkclnt.sys UNEXPECTED_KERNEL_MODE_TRAP *** STOP: 0x0000007f.

I tried to solve the problem in various ways: by reinstalling the virtual machine, restoring system files, removing the antivirus and firewall, updating drivers for all computer components, including the network card. Unfortunately, only changing the network adapter helped.

When creating instructions for installation and configuration hypervisor, the hypervisor itself, installed on real hardware, was tested. I was helped to configure it and the control computer by a cmd script that I wrote in 2014 and was accidentally discovered in the depths of my file dump after its general cleaning.
The script was slightly tweaked and tested again. The only thing I couldn’t achieve was executing the color restoration command in the cmd console at the end of the script, which can be restored manually in the console properties.
I got the idea for writing a script on the website ru.intel.com and, unfortunately, the link to that page no longer exists.
This cmd script automatically configures the hypervisor and the control computer for remote control hyper v server 2012 using remote control tools, in particular using hyper-v manager, on Windows 7, Windows 8 and Windows 8.1

Detailed and straightforward instructions for installing and initially configuring the hypervisor are written on this page: installation and configuration of hyper - v server 2012 bare metal

We have:
Computer(hardware) with installed and updated hyper-v 2012
Guest OS(vmware) with installed, Russian-language OS windows 7x64, windows 8x64, windows 8.1x64

The conditions are simple:
- Run the script on the control computer with administrator rights
- The firewall must be enabled on the management computer
- The control computer must have the Russian-language Windows 7x64, Windows 8x64 or Windows 8.1x64 installed (I haven’t tried it on x86 systems, but it might work on them)
- UAC and antivirus must be temporarily disabled on the control computer so as not to block installation scripts
- Remote server administration tools must be installed on the control computer, in particular rsat hyper-v
- The network must be running on the hypervisor and the control computer
- The hypervisor and the control computer must be in the same workgroup
- Newly created hypervisor and computer accounts, and passwords for them, must be the same

Even simpler:
On the computer: firewall enabled + script run as admin + Russian Windows 7x64, 8x64 or 8.1x64 + disable UAC and antivirus + rsat hyper - v installed
On a computer + hypervisor: one working group workgroup+ the same admin account Ivanov and password GUGlplay307

If you do not have remote server administration tools installed, download them from the links below:
For Windows 7x64: https://www.microsoft.com/ru-RU/download/details.aspx?id=7887
For Windows 8x64: https://www.microsoft.com/ru-ru/download/details.aspx?id=28972
For Windows 8.1x64: https://www.microsoft.com/ru-ru/download/details.aspx?id=39296

Download the archive with the script config_server_client_hyper-v_2012.zip on the page pantry In chapter scripts and programs: script for automatic configuration of the hypervisor and control computer
Before unpacking the archive, you must unlock it by right-clicking on it and selecting properties.

Archive contents:
Windows7x64 and Windows8x64 folders for different OS versions
Each folder contains files:
- firewall_hyperv_client_rus.cmd and hvremote.wsf for configuring the control computer
Each folder contains a folder:
- shared disk containing files: firewall_hyperv_server_rus.cmd (configures the hypervisor)
hvremote.wsf (configures the hypervisor), INSTALL.CAB (contains the total commander program, downloaded from the offsite)
Corefig folder containing powershell scripts (hypervisor management)

First, let's configure the hypervisor (some examples and descriptions of settings)

If you have Windows 7x64 installed (this is also true for Windows 8x64), then on the control computer:
- copy the file firewall_hyperv_client_rus.cmd from the root of the Windows7x64 folder to your desktop
- to drive "C", copy the file hvremote.wsf from the root of the Windows7x64 folder
In case of using "balls":
- share any folder (I shared the disk)
- copy the contents of the Shared disk folder, which is located in the Windows7x64 folder, into the “share”, except for the text file attention.txt
If using a flash drive:
- copy the firewall_hyperv_server_rus.cmd file to the USB flash drive, located in the Shared disk folder, which is located in the Windows7x64 folder
the rest, except for the files attention.txt and firewall_hyperv_server_rus.cmd, is copied to the “share”

If everything is copied to the “share”, then on the command line of the hypervisor we write (indicate your data):
net use R: \\192.168.1.3\E/user:control_computer\account_name password && cd /d R C:\ && cd /d C:\ && firewall_hyperv_server_rus.cmd Here we: connect the shared drive “E” as drive “R” && go to drive "R" && && go to drive "C" &&

If it happens that you have the “share” somewhere there, and the flash drive is here, then we stick it into the hypervisor and write in the command line of the hypervisor:
diskpart
list volume We display a list of disk volumes, among which our flash drive is located (screenshot below)

Cd/d I:\ && xcopy firewall_hyperv_server_rus.cmd C:\ && cd /d C:\ && firewall_hyperv_server_rus.cmd Enter your details. Go to disk "I" (our flash drive) && copy the file firewall_hyperv_server_rus.cmd to drive “C” of the hypervisor && go to drive "C" && run the file firewall_hyperv_server_rus.cmd

Each command is separated from the other by symbols && , saying: “if the previous command completed successfully, then execute the next one” and therefore, if something went wrong, execute them one by one.

During the execution of scripts, windows will appear asking you to specify the network settings of the hypervisor, control computer and account details. Follow these simple instructions exactly as they are written.
A little about passwords for hypervisor accounts. Its requirements are high, and you only need to specify it once... Don’t bother, just enter something similar: GUGLplayer307

After executing all the commands, the script will “ask” to restart the hypervisor, so reboot.
In the future, to open total commander, you need to go to the "tc" directory and run the program cd c:\tc && totalcmd.exe
To run the corefig utility, you need to go to the "corefig" directory and use cscript run the utility cd c:\corefig && cscript start_corefig.wsf
or cd c:\corefig && powershell .\corefig.ps1

Now let's configure the control computer (some examples and descriptions of settings)

We run the firewall_hyperv_client_rus.cmd script as an administrator, which is located on the desktop of the control computer and follow the instructions.

Briefly:
The script includes hyper-v remote control tools
Temporarily activates the built-in "administrator" account (Windows 8x64 and higher) to run commands as it
Configures the hosts file
Creates another script and copies it to the path c:\users\public
Adds a key to the registry with a link to the newly created script
Creates a new administrator account to manage the hypervisor
Verifies an account by displaying information about it
Removes executed lines of code from its body and creates a new script to run later
Reboots the computer for subsequent login with a new account
Configures the "component service"
Adds the hypervisor to the list of trusted hosts to allow connections to it and tests the configuration
Adds the necessary rules to the windows firewall
Tests access to the hypervisor
Configures the management computer for remote management of the hypervisor
Deactivates the built-in "administrator" account (Windows 8x64 and higher), removes scripts from the computer and a link from the registry

In order to avoid errors, I note that after rebooting, do not forget to change the keyboard layout from Russian to English.
Don't forget that after reboot windows 8x64, you will need to provide a password abc in the black window that appears on the desktop after you log in and click enter. The password is not displayed when you enter it.
mmc, for Windows 7x64 OS.

The two screenshots below show: the hyper-v manager connected to the hypervisor and the necessary snap-ins added to the console mmc, for Windows 8x64 OS.

That's all. Next time we let's set it up network using the hyper-v manager, create virtual machines and connect them, install and configure the domain and other servers and services.

Today we will learn about how to install and configure the hyper-v server hypervisor from Microsoft, as well as some pitfalls and ways to avoid them.

The reason for writing this article was the material of this post. This post is more suitable as a cheat sheet if you have already worked with this hypervisor. A beginner will have to deal with a lot of nuances and dig through a lot of forums in search of answers to non-standard questions.

For beginners, the article will outline in as much detail as possible all the actions and their meaning, 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 subblocks so that you can quickly find the necessary information.

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 the resources of the host machine will be spent on running the services we need.

Installation

Before you begin 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 from the Microsoft website (no 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 - selecting the installation wizard language

The installation window prompts us to select the operating system language. We choose English; later in the article we will explain why.

Hyper-v server - selecting OS language and keyboard layout

We chose English for the language, and it’s better to choose Russian for the time format, so that later we don’t have to worry about setting it up on the command line.

Hyper-v server - selecting installation type

Select the full installation (Custom).

Hyper-v server - setting hard disk parameters

At this stage, the wizard prompts you to configure the hard disk partition settings. It is best to create 2 logical drives. The first one is for installing the hypervisor itself; 15 GB is enough for it. The second is for storing virtual machine (VM) containers. Thus, it will be much more convenient to manage, import and migrate VMs.

Click “Next” and we can rest for a while. The computer will restart several times during the installation process.

Settings

Basic setup and remote access

After rebooting, hyper-v server will prompt us to set an administrator password. Since by default the ms windows 2008 server r2 group policy requires password complexity, you will have to come up with a password that is at least 6 characters long and must contain a capital letter and a special character or number (for example, “Password1”).

As you can see in the screenshots below, the management console is in Russian, although English was selected during installation, most likely this is because the Russian distribution was downloaded from the official Microsoft website. This will not negatively affect the operation and configuration of the server. If you have a console 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 cmd command console 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 network adapters will be listed. Select the one you need 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. Select item 7, then enable the remote desktop by entering the English “E”. When asked about limiting connections from older versions of rdp clients, 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. To operate the hyper-v server, we will not include it in the domain, which complicates the setup somewhat, but for experiments this is an ideal option. During tests and verification of various configurations, it is better to isolate the test machines from the target network.

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 this 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 settings, you need to reboot; we agree with the OS offer.

Further, all settings (such as computer name, workgroup, users, IP address, etc.) will be used as those described during the installation process. If you set your parameters, do not forget to use them.

After rebooting, we can connect to the server using the Remote Desktop Client. Select start -> run, 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 password “Password1”.

So, we have connected, now we need to configure additional remote control settings. We go to point 4. Now, in order, select sub-points 1, 2 and wait for the setup to complete. After completion, the OS will again ask you to reboot. Once these settings are completed, we will be able to connect to the server using the mmc console and the 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 “hyper-v Manager” component 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 (MC).

Setting up users

The first step is to create a user on whose behalf we will carry out control. Usernames and passwords must be the same for UK and SRV!

On the SRV - in the management console, select item 3 (adding a local administrator). Set the name “admin” and the password for it “Qwerty1”. Let's check whether it was successfully added, in the cmd console we enter: net user admin This command will show us that it is a member of the “Administrators” and “Users” groups.

On the management company - launch the cmd console as administrator and enter the command: net user admin Qwerty1 /add add him to the administrators group: net localgroup Administrators admin /add for the English version enter: net localgroup Administrators admin /add Check the results again using: net user admin

To configure users and security groups, there is a wonderful utility “HVRemote”, written by one of the Microsoft employees.

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 be named in English.

A small digression: as was written earlier, hyper-v server does not have a graphical interface. This is not entirely true, Microsoft simply cut out 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 SRV - open the cmd console, go to the folder with the file “HVremote.wsf” (in the article the file is saved to the root of the C: drive). 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 necessary groups and assigned him rights.

On the management side, you need to run the following commands cscript hvremote.wsf /anondcom:grant cscript hvremote.wsf /mmc:enable

For the remote computer management console snap-ins to work, you need to create exception rules in the server firewall. First of all, let's 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 rather than copying/pasting. Result of successful command execution: Updated 3 rule(s). Ok. Next, let's enable remote firewall management netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes Result of successful command execution: Updated 2 rule(s). Ok. Let's allow access for any mmc console snap-ins netsh advfirewall firewall set rule group="Remote Administration" new enable=yes Result of successful command execution: Updated 3 rule(s). Ok. Let's enable the use of “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. Let's enable the icmp protocol: netsh firewall set icmpsetting 8 Let's 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: launch the mmc console -> file -> add or remove snap-in -> hyper-v manager. Select the Action menu -> connect to 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 commands

Ever since Microsoft introduced a trial version of HYPER V to PC users in 2008, computer technology has come a long way. Meanwhile, no matter what innovations the modern world brings, this hardware virtualization system developed on the basis of a hypervisor cannot do without it even today. True, these days you can install both HYPER V SERVER and the HYPER V MANAGER component on Windows 7, which makes the task of using it somewhat easier when debugging the network.

However, practice shows that installing HYPER V often causes confusion, especially in cases where a beginner or a user who is not familiar with the features of such a Microsoft system and the basics of setting it up for working on the network takes on the task. In this case, it is simply impossible to leave unanswered the question of how to install and configure HYPERV MANAGER and HYPER V SERVER on a computer running Windows 7.

Option No. 1: Installing and debugging HYPER-V server

It's no secret that today the HYPER V SERVER system from Microsoft is presented in several assemblies, each of which has its own advantages and disadvantages. In particular, not so long ago, the release of windows server 2012 r2 hyper v became available to Internet users. However, the most popular option still remains the Microsoft HVS 2008 R2 version with the Core setting.

In addition to the HYPER-V base, it does not provide additional extensions, which, however, is not a minus, but a plus, considering that this ensures optimal consumption of hosting resources at the highest possible performance levels. The installation and debugging process consists of several stages.

Stage I – preparing the computer

At the preparatory stage you need to do 3 basic actions:

1. download and burn a bootable drive with the image of HYPER V SERVER 2008R2. As a basis, you can take the same free distribution from the Microsoft website. It will do just fine;
2. check whether the processor supports the hardware virtualization system;
3. set the parameters for starting the computer from an external drive.

Stage II – installing the system on Windows 7

Having completed the preparations, connect the flash drive / disk with the image of HYPER V SERVER 2008 R2 to the computer and boot from it. In the window that appears, select English as the working language, change the time format to Russian and click the Next button:

Next, click the Install now button, and then, after reading the license, confirm acceptance of the terms of the agreement for the use of Microsoft HVS 2008 R2. After this, select Custom (“Full”) as the installation option and proceed to the “Hard disk partitioning” step:

Here the principle of action is the same as when installing/reinstalling Windows: format the hard drive and then split it into 2 partitions. The first will be allocated for the placement of the hypervisor (memory capacity of at least 15 GB); the second is for containers of virtual machines on the network (5 GB of memory will be enough). Having completed the partitioning, click Next and wait until the data is copied and the computer restarts.

Stage III – determination of basic parameters

After completing the installation of HYPER V SERVER 2008R2 and rebooting, the program will prompt you to set a network administrator password. The default requirement is a 6-digit password with 1 capital letter and 1 number (special character). Having passed this step, two windows with consoles should appear on the screen - a standard command line and an options (control) console on a blue background:

At this point we will have to work with the HVS 2008 R2 options console:

To begin, select step 8, mark the required network adapter, and then enter the IP address, default gateway and subnet mask. After saving the settings, go to the main menu, select item 7, enter the English letter E for , and then the number “2” - connect without restrictions on clients. Next, we return to the main menu again, select item 9 and similarly configure the date and time for the server on the network.

Stage IV – debugging additional parameters

For HVS 2008 R2 to work correctly on the network, you must also specify a server name and configure a workgroup. To do this, select item 1 in the menu, enter the letter W and assign a name to the workgroup (it must match the name of the network administrator’s PC). Then select step 2, specify the network name of the server (for example, HVS-2008) and save the changes by restarting the system. Next, set other remote control parameters. To do this, connect remotely to the PC, select step 4 and alternately execute the commands from sub-items 1 and 2 until rebooting.

Now download the tool package RSAT, developed by Microsoft, and upload from it to Windows 7 the program data of the HYPER-V manager, designed for administering virtual machines. After this, all that remains is to set the parameters for users and install the necessary services on the PC.

Option No. 2: Preparing a HYPER-V manager

To connect to the network, instead of HVS 2008 R2, you can also use the HYPER-V manager. It is easier to install, although the base for it is limited only to the build of Windows 7 Professional and higher. Anyway, the procedure is as follows:

Back in Windows 8, Hyper-V virtualization technology appeared, previously available only in Microsoft server operating systems. This solution looks better than the Windows Virtual PC virtual machine included in Windows 7. Today I will tell you how to create a virtual machine in Windows using Hyper-V, and also set up the Internet, local network and file sharing in it.

In addition to Coreinfo, you can use Intel's proprietary utility (AMD has a similar one).

You can also look at the virtualization technology support table on your processor manufacturer's website: Intel | AMD.

Enable Hyper-V

Hyper-V is an operating system component that is initially disabled. Advanced users can enable it with one PowerShell command:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

If you prefer a GUI, press Win + R, enter OptionalFeatures and press Enter.

In the window that opens, select the Hyper-V checkbox.

One way or another, the component will become available after a system reboot. Among the problems with installation in Windows 8 RP, a cyclic reboot due to the fault of USB 3.0 controller drivers has been noticed so far, 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 select Create – Virtual machine.

The virtual machine creation wizard is extremely simple, but I will note some points for those who like detailed instructions with pictures. I will skip the network setup step now, since I will analyze this issue in more detail.

The standard location for virtual machines is a 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 disk I created earlier for Virtual Box.

When you specify an existing VHD, the wizard removes the step where you specify the media for installing the system.

However, you can specify the path to the ISO later by opening the virtual machine settings in the main Hyper-V Manager window.

Starting a virtual machine and installing Windows on it

Everything here is also 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 machine’s thumbnail

When the bootable Windows ISO image is specified in the machine settings, you will see the familiar Press any key to boot message on the screen... Then you can do it yourself, but if you need step-by-step installation instructions, they are 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 one, 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 unhappy with the Default Switch introduced in Windows 10 1709, which cannot be removed or renamed. When using Default Switch, if the host is connected to a 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 select Setting up 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.

All that remains is to specify the created switch in the network connection parameters of the virtual machine.

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 see:

• on the left is 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 the local network on the virtual machine

As you can see, setting up the Internet and local network is not so much complicated 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 from a physical one to it, 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 network at our disposal, we can use shared folders to share files. In fact, the instructions below boil down to the basics of creating shared folders.

Access from virtual machine to physical machine

A picture is worth a thousand words, as the Americans say.

The figure shows the virtual machine explorer (VIRTUAL-PC), from where the physical machine (VADIK-PC) is accessed. Once you enter your account credentials, access to your profile will be at your disposal.

You may want to create 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 access to an arbitrary virtual machine folder.

Access from physical machine to virtual machine

Let's say there is a folder in 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 the address of the form in the address bar \\computer-name\folder-name.

Connecting to a remote desktop of a virtual work machine

In Hyper-V, files cannot be exchanged between a physical and virtual machine by copying and pasting. You can only paste text copied on a physical machine using the keyboard shortcut Ctrl + V. However, once the virtual machine is running, you can connect to it via RDP instead of opening it from Hyper-V Manager. This method works in Pro editions and higher.

Actions on a 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 allow the connection as shown in the picture.

All that remains is 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 login options.

In the window that opens:

1. Enter the IP address of the virtual machine (required).
2. Enter the name of the user whose account you will be signing in to.
3. Enable login credentials to be remembered.
4. Save the connection settings.

You can also set the Display tab to a resolution lower than what is used on 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 recommendations from Denis Diaghilev for working with Hyper-V.

Use RDP to connect to virtual machines.

This will not only allow you to share files between the physical and virtual machine by copying and pasting, but will also save system resources that vmconnect consumes when connecting to the 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 transition list.

Be careful with your photos

With Hyper-V you can create snapshots of a virtual machine using differential disk technology. However, the logic of the images is almost the opposite of what a person who has never stepped on a rake would expect from it.

Alexander Kosivchenko (MVP for virtualization) described in detail, although somewhat chaotically, the principle of operation of Hyper-V snapshots on Habré.

Use virtual machine import if necessary

Import will be more interesting to IT specialists, but I happened to use this function by accident. After creating the virtual machine, I renamed the drive letter where it was stored, and then Hyper-V Manager lost it.

Looking around in the snap, I saw the import option and instantly restored the machine.

Moreover, I didn’t even suspect that the actions I performed became possible only due to the emergence of a new feature in Hyper-V :)

Hyper-V vs. VirtualBox

While understanding Hyper-V, I couldn’t help but compare Microsoft’s solution for the client operating system with Oracle VirtualBox.

From the point of view of typical tasks of home users (testing the system installation, familiarization with it, checking the operation of applications), these solutions are practically no different from each other. But VirtualBox can be used in Windows 10 Home editions, while Hyper-V is not available in them.

VirtualBox does not have such strict hardware requirements, and its graphics capabilities are even greater, since it supports 3D hardware acceleration (though I have never used it).

As for the graphical interface, this is purely a matter of taste. Probably, the hypervisor that came from server operating systems looks more ascetic, but the parameters and configuration of virtual machines are generally very similar.

The presence of Hyper-V in Windows will primarily please IT professionals accustomed to this technology. For home users, this is a good opportunity to take advantage of the system’s built-in tools and expand their horizons by becoming familiar with Microsoft server technologies.

Survey

I became acquainted with virtual machines in 2004, when I started doing Windows Auto Install. Since then they have become an integral part of my daily work, including testing system settings, programs, etc.

In comments Tell us what virtualization solution you use and for what purpose!

I would like to thank Denis Diaghilev for his assistance in preparing this material. One of the benefits of the MVP program is exposure to top Microsoft technology talent. This means that you can get competent advice on any issue privately;)

Denis also kindly offered his assistance in facilitating the discussion. Therefore, if you have any technical questions regarding this article, you can count on qualified answers.

I want to specifically emphasize that