Installing hyper v management on windows 7. Automatic startup and shutdown of virtual machines on the Microsoft Hyper-V platform

Twitter

In 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 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.

This article shows the steps you can take to create a virtual machine in Hyper-V Manager on Windows 10

Microsoft Hyper-V technology is an embedded hardware virtualization system that provides guest systems with direct access (without the participation of intermediate virtual drivers that slow down the work) to computer devices (disk, memory, processor).

The operating system inherited the Hyper-V component from previous versions, Windows 8 and. On Windows 10, Hyper-V is only available in 64-bit Pro and Enterprise editions. The system requirements for enabling Hyper-V are detailed in the article ➯

In Windows 10, the Hyper-V hypervisor, in addition to guest operating systems of the Windows family, now supports some Linux distributions, in particular, the popular Ubuntu.

You can install new distributions of operating systems on a virtual machine for testing, and also use it as a server.

CONTENT:
1

How to start Hyper-V Manager

There are several ways to start Hyper-V Manager

➁ You can use the search, to do this, click on the search icon on the taskbar or press the key combination + S, in the window that appears, enter hyper-v in the search field. In the search results, select Hyper-V Manager, or right-click and select Home screen or Pin to taskbar(if you will be using Hyper-V Manager frequently).

➂ You can also start Hyper-V Manager, you can from the list of programs in the Start menu in the folder "Administration Tools"

➃ You can also create a shortcut to launch Hyper-V Manager, for this right-click on the desktop and in the context menu that appears, select New> Shortcut, then in the "Create shortcut" window in the field Specify the location of the object: enter virtmgmt.msc and click Next

In the next window, in the field Enter shortcut name type for example Hyper-V Manager and click Finish, which will create a shortcut on the desktop with which you can start Hyper-V Manager

How to create a virtual switch

Configuring network access in Hyper-V Manager is configured separately. To do this, in the Hyper-V manager on the left in the list, select the item with the name of your computer, and in the right part of the window, select Virtual Switch Manager ...

In the virtual switch creation wizard that opens, you need to select the type of network. Depending on what kind of access you plan to provide to virtual machines, you can choose one of three types of virtual network:

● External - This type uses the network card or Wi-Fi adapter of the physical computer and connects the virtual machine to the same network as the physical computer. Accordingly, this type of network provides for a virtual machine to access the Internet.

● Internal — This type provides a network between the physical computer and Hyper-V virtual machines, but does not allow them to access the Internet.

● Private - this type allows you to create a network between Hyper-V virtual machines, but this network will not have a physical computer, nor will there be an Internet connection.

In this case, the virtual machine needs access to the Internet, so we select the first type - external network and click Create virtual switch

In the properties window of the virtual switch, give it a name, it can be any name, in this example, Virtual Network. If your computer has both a Wi-Fi adapter and a network card, select in the External network item the one of the network adapters that is used to access the Internet. In this case, a Wi-Fi adapter is used. After making the settings, click the OK button

The virtual network adapter has been created. You can see the result of adding a virtual switch to Hyper-V on a physical machine in the "Network Connections" window. As a result, a network bridge and a virtual adapter were created.

How to create a virtual machine
in Hyper-V Manager

To create a virtual machine in Hyper-V Manager, right-click on the computer name and select New> Virtual Machine ...

In the first window of the virtual machine creation wizard, click the Next>

In the next window, we give the virtual machine a name, you can also change its location (the standard location for virtual machines is the folder C: \ ProgramData \ Microsoft \ Windows \ Hyper-V) on the disk of the physical computer, specifying the desired disk partition and the desired folder using the Browse ... button, click the Next>

The next step is to select the generation of the virtual machine. Select the required generation of the virtual machine (in this case, generation 2) and click Next>

Generation 1 are virtual machines that support 32-bit and 64-bit Windows systems. Generation 1 is backward compatible with Hyper-V

Generation 2 is a new format virtual machine with UEFI-based firmware. These virtual machines support a number of new features and can provide small performance gains. On virtual machines of generation 2, only 64-bit versions of Windows 8.1 and 10, as well as server Windows Server 2012, Server 2012 R2 and Server 2016 are installed as guest OS

Next, in the memory allocation window, we leave the preset parameters if the physical computer has no more than 4 GB of RAM. If the RAM is more than 4 GB, you can increase the amount allocated when the virtual machine starts. Select the amount of memory you want and click Next>

In the Network Settings window, in the Connection drop-down list: select the previously created virtual switch and click Next>

In the "Connect virtual hard disk" window, specify the desired location on the disk, the name of the virtual hard disk file, and set the size that will be sufficient for your purposes and click Next>. In this case, the default parameters are left.

The next step is to specify the path to the Windows distribution. Second generation virtual machines do not boot from a physical CD / DVD drive. The sources for downloading the distribution of the guest operating system can only be the network and the ISO image. In this case, it is an ISO image. Click Next>

Then, in the Completing the New Virtual Machine Wizard window, click Finish

Connecting and starting a virtual machine

After creating a virtual machine, it will appear in the list of virtual machines in Hyper-V Manager. Now the virtual machine needs to be connected. To do this, right-click on the virtual machine and select Connect from the context menu. The Connect command is also present on the right side of the Hyper-V Manager window. To connect, you can also double-click the left mouse button on the preview window of the selected virtual machine.

In the connection window that opens, click the green Start button

The normal Windows 10 installation process will then begin as it would on a physical computer.

As soon as copying the installation files starts, you can close the window for connecting to the virtual machine.

Closing the connection window will free up some of the physical computer's resources for other tasks, while the virtual machine will continue to run in the background. Its performance will be displayed in Hyper-V Manager. You can connect to a virtual machine as needed to perform actions in it.

During the creation of instructions for installation and configuration hypervisor, the hypervisor itself, installed on real hardware, was tested. A cmd script, written by me in 2014, and accidentally discovered in the bowels of my file storage after its general cleaning, helped me to configure it and the control computer.
The script has been slightly tweaked and tested again. The only thing that I could not achieve was the execution of the command to restore the color 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 site 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 dispatcher hyper - v, on Windows 7, Windows 8 and Windows 8.1

Detailed and without "water" instructions for installing and initial configuring the hypervisor are written on this page: installing and configuring hyper - v server 2012 bare metal

We have:
Computer(hardware) with hyper installed and updated - 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 host computer
- The control computer must have a Russian-language system Windows 7x64, Windows 8x64 or Windows 8.1x64 installed (I have not tried it on x86 systems, but it will probably 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 work on the hypervisor and the control computer
- The hypervisor and the control computer must be in the same workgroup
- Newly created accounts of the hypervisor and the computer, and passwords to them, must be the same

Even easier:
On a computer: firewall enabled + running script from admin + Russian Windows 7x64, 8x64 or 8.1x64 + cut down UAC and antivirus + installed rsat hyper - v
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, then 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/en-us/download/details.aspx?id=39296

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

Archive content:
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 the settings)

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

If everything is copied to the "ball", then in the command line of the hypervisor write (specify your data):
net use R: \\192.168.1.3\E/ user: host_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 disk "R" && && go to drive "C" &&

If it so happens that you have a "ball" somewhere, and a flash drive is here, then we put it in the hypervisor and write in the command line of the hypervisor:
diskpart
list volume Display a list of disk volumes, including our flash drive (screenshot below)

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

Each team is separated from the other by symbols && , stating: "if the previous command was executed successfully, then we execute the next one" and therefore, if something went wrong, execute them one by one.

During the execution of the scripts, windows will appear asking you to specify the network settings of the hypervisor, the controlling computer and account details. Follow these simple instructions as written there.
A little about passwords for the hypervisor account. Its requirements are high, but you only need to specify it once ... Don't bother, just drive in something similar: GUGlplayer307

After executing all the commands, the script will "ask" to restart the hypervisor, restart it.
Further, to open the total commander, you need to go to the "tc" directory and run the program cd c: \ tc && totalcmd.exe
To run the corefig utility, 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)

Run the script firewall_hyperv_client_rus.cmd on behalf of the administrator, which is located on the desktop of the controlling computer and follow the instructions.

In short:
The script includes hyper-v remote controls
Temporarily activates the built-in "administrator" account (windows 8x64 and higher) to execute commands on its behalf
Configures the hosts file
Creates another script and copies it along the path c: \ users \ public
Adds a key to the registry with a link to the newly created script
Creates a new administrator account for hypervisor management
Checks an account by displaying information about it
Removes executed lines of code from its body and creates a new script to run it later
Reboots the computer to log in again with a new account
Configures a "Component Service"
Adds a hypervisor to the list of trusted hosts to allow connections to it and tests the configuration
Adds required rules to windows firewall
Tests access to the hypervisor
Configures the host computer for remote hypervisor management
Deactivates the built-in "administrator" account (windows 8x64 and higher), removes scripts from the computer and the link from the registry

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

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

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

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

Using graphical interfaces such as Hyper-V Manager or System Center Virtual Machine Manager (SCVMM) makes managing Hyper-V quick and easy. However, there are many situations in which you can perform operations much faster if you have the ability to use the command line or scripts. In this article, we'll take a look at Powershell's capabilities for managing Microsoft Hyper-V.

Install Powershell

First, we need to install Powershell.

To install Powershell on Windows 2008, go to Server Manager, further into Features... Click on Add Features... Check it out Windows Powershell and press Next.

Then press Install.

To start Powershell go to Start -All Programs -Windows Powershell.

At this point, the long awaited dark blue Windows Powershell window will open:

Now we need to download the Hyper-V Powershell library.

Download and install Hyper-V Powershell Library

The developer of the Powershell control library for Hyper-V 1397 is James O'Neill and his library is simply invaluable when you have to manage Hyper-V from the command line. Follow the link above and download the file Hyperv.zip... Unpack the archive into some directory, for example C: \ temp.

Now start PowerShell, go to the directory with unpacked scripts, disable PowerShell security with the command:

Set-ExecutionPolicy unrestricted

... c: \ temp \ hyperv.ps1

You will then receive a security warning and you must select “ R”To run the script. After that you should see the message “ VM Functions Loaded”And a list of loaded commands.

Administering Hyper-V with PowerShell

Along with the library comes a help file that describes more than 100 commands included in the library. And remember that each of these 100 commands has a large number of parameters. Consideration of all commands and their parameters will not fit in a dozen of similar articles, so we will consider the most basic commands and their application.

Let's take a look at the following 5 commands and how they are used:

Gives a summary of all guest virtual machines on your Hyper-V server.

Start-VM, Stop-VM, Suspend-VM, and Shutdown-VM- the purpose of these commands is pretty obvious. The parameter is the name of the virtual machine.

The easiest way to create a new virtual machine

- a list of all virtual machines on the server and the amount of memory it consumes

The command shows all snapshots taken on your Hyper-V server. To manage snapshots, you can additionally use the commands Update-VMsnapshot, New-VMsnapshot, Apply-VMsnapshot, Get-VMsnapshotTree, and Choose-VMsnapshot.

Not a bad laptop site, I liked the acer most of all: reviews of acer laptops, all models, low prices.