When it comes to deploying Hyper-V servers, there are two main options: install the standalone Hyper-V hypervisor or add the Hyper-V feature to a supported Windows Server 2008 R2 server. I’m going to take the separation approach as I venture into Hyper-V and use the standalone Hyper-V hypervisor instead of the full installation of Windows Server 2008 R2 and adding the Hyper-V role.
The Hyper-V standalone install is a single-purpose, standalone distribution. It loosely resembles Windows Server Core, and can be plugged into all of the management frameworks, including Group Policy, PowerShell, Hyper-V Manager, System Center Virtual Machine Manager (SCVMM), and Remote Management.
The Hyper-V Manager tool is the simplest way to manage a Hyper-V host, and it can be added to any server system. To add Hyper-V Manager, open Server Manager and navigate to the Features section (Figure A).
Figure A

Click the image to enlarge.
Once the feature is installed, Hyper-V Manager will be available in the Administrative Tools area of the Start Menu. From there, the first step is to connect to a remote server. Figure B shows Hyper-V Manager connected to two Hyper-V servers. Figure B
Click the image to enlarge.
Before you can create virtual machines on the Hyper-V hosts enumerated in Hyper-V Manager, the host networking will need to be configured. Hyper-V supports three types of networks: External, Internal, and Private. These networks loosely equate to bridged, NAT, and host-only network modes from other hypervisors, respectively. The network for the host is created as shown in Figure C. This environment does not have a VLAN tag in use, but the Configuration tab is available.

No comments:
Post a Comment