Hyper-V:Install: Difference between revisions
(Created page with "{{DISPLAYTITLE:{{TitleIcon|hyperv=true}} Hyper-V Server 2016: Installation}}<metadesc>How to setup Hyper-V Server 2016 on baremetal.</metadesc> <div id="tocalign">__TOC__</div...") |
|||
| Line 68: | Line 68: | ||
Finally reboot the machine to commit the machine name and IP changes. | Finally reboot the machine to commit the machine name and IP changes. | ||
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Restart-Computer}}}} | {{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Restart-Computer}}}} | ||
= {{Icon24|sitemap}} Dell OpenManage System Administrator = | |||
If you are running this on a Dell server, you might also want to install OMSA. At this point you should be able to access the administrative shares for windows. | |||
Copy the OMSA installer onto the Hyper-V Server using the admin shares (eg. {{mono|\\SKYE\d$}}). | |||
Run the EXE from the command prompt or PowerShell to extract to {{mono|C:\OpenManage}}. | |||
Run the pre-requisite checker. | |||
{{console|prompt=false|powershell=true|1=PS C:\> C:\OpenManage\windows\PreReqChecker\RunPreReqChecker.exe /s}} | |||
Provided no errors are seen, install OMSA. | |||
{{console|prompt=false|powershell=true|1=PS C:\> msiexec /i C:\OpenManage\windows\SystemsManagementx64\SysMgmtx64.msi}} | |||
During the installation it might be beneficial to choose {{mono|Custom}} and then add the Remote Manager. | |||
Once installed a firewall rule will be needed to access OMSA from another computer. | |||
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|New-NetFirewallRule}} {{white|-Name}} Dell_OMSA {{white|-DisplayName}} {{blueBold|"Dell OMSA"}} {{white|-Description}} {{blueBold|"Dell OMSA Web Management"}} {{white|-Protocol}} TCP {{white|-Enabled}} True {{white|-Profile}} Any {{white|-Action}} Allow {{white|-LocalPort}} 1311}} | |||
= {{Icon24|book-brown}} References = | = {{Icon24|book-brown}} References = | ||
<references/> | <references/> | ||
[[Category:Windows]] | [[Category:Windows]] | ||
Revision as of 12:10, 7 July 2018
 | UNDER CONSTRUCTION: The document is currently being modified! |
Back to Category:Windows
Introduction
IntroductionMicrosoft Hyper-V Server 2016 is a stand-alone product that contains only the Windows hypervisor, a Windows Server driver model, and virtualization components. The Windows hypervisor technology in Microsoft Hyper-V Server 2016 is the same as what's in the Hyper-V role on Windows Server 2016.[1] Hyper-V Server has a Windows Server Core experience and as such doesn't have a graphical user interface (GUI).
Testing was done on my Dell PowerEdge R610, the following image was used:
 en_microsoft_hyper-v_server_2016_x64_dvd_9347277.iso |
Installation
Insert the Hyper-V Server boot media into the machine and reboot (or power on) the machine, booting from the inserted media. Follow the instructions on the screen to install and reboot.
 | Hyper-V Server only requires ~32GB of hard drive space. Perform a "Custom" install, partitioning the C: drive accordingly, then assign the rest to D: for virtual machines. |
Upon reboot you will be prompted to set an Administrator password, doing so will log into the machine finalizing the installation.
Use the command prompt provided to launch Windows PowerShell.
| C:\> powershell |
Networking
NetworkingBefore Hyper-V itself can be setup, a strong networking backbone needs to be setup.
Rename the computer.
| PS C:\> Rename-Computer -NewName SKYE |
List the current network adapters.
| PS C:\> Get-NetAdapter -Physical |
The Dell R610 comes with a built-in quad-port NIC, one will be assigned to management while the other three will be teamed together for VMs.
First create the NIC team.
| PS C:\> New-NetLbfoTeam -Name "Hyper-V Team" -TeamMembers "Ethernet 2", "Ethernet 3", "Ethernet 4" |
Verify it created the team correctly.
| PS C:\> Get-NetLbfoTeam |
| If you need to specify a VLAN for the NIC team, use Set-NetLbfoTeamNic -Team "Hyper-V Team" -VlanID 123. |
Rename the original adapters for consistency.
| PS C:\> Rename-NetAdapter -Name "Ethernet" -NewName "Management" |
| PS C:\> Rename-NetAdapter -Name "Ethernet 2" -NewName "Ethernet Team 1" |
| PS C:\> Rename-NetAdapter -Name "Ethernet 3" -NewName "Ethernet Team 2" |
| PS C:\> Rename-NetAdapter -Name "Ethernet 4" -NewName "Ethernet Team 3" |
Static IP
In order to setup a static IP address DHCP has to be disabled, the current IPs have to be removed, then new IPs can be assigned.
Remove DHCP from both adapters.
| PS C:\> Set-NetIPInterface -InterfaceAlias "Management" -Dhcp Disabled |
| PS C:\> Set-NetIPInterface -InterfaceAlias "Hyper-V Team" -Dhcp Disabled |
Remove the current IP addresses from both adapters (use A to choose Yes to All when removing).
| PS C:\> Get-NetAdapter -InterfaceAlias "Management" | Remove-NetIPAddress |
| PS C:\> Get-NetAdapter -InterfaceAlias "Hyper-V Team" | Remove-NetIPAddress |
Set the IP information for both adapters.
| PS C:\> New-NetIPAddress -InterfaceAlias "Management" -IPAddress 10.0.42.10 -AddressFamily IPv4 -PrefixLength 24 -DefaultGateway 10.0.42.1 |
| PS C:\> New-NetIPAddress -InterfaceAlias "Hyper-V Team" -IPAddress 10.0.42.11 -AddressFamily IPv4 -PrefixLength 24 -DefaultGateway 10.0.42.1 |
Also add DNS servers for both.
| PS C:\> Set-DnsClientServerAddress -InterfaceAlias "Management" -ServerAddress 10.0.42.1 |
| PS C:\> Set-DnsClientServerAddress -InterfaceAlias "Hyper-V Team" -ServerAddress 10.0.42.1 |
Remote Management
In order to use RSAT and Windows Admin Center remotely a few changes need to be made.
Enable WinRM.
| PS C:\> Enable-PSRemoting -SkipNetworkProfileCheck -Force |
Enable remote authentication acceptance.
| PS C:\> Enable-WSManCredSSP -Role server |
Enable firewall rules for remote management.
| PS C:\> Set-NetFirewallRule -DisplayGroup 'Windows Management Instrumentation (WMI)' -Enabled true -PassThru |
| PS C:\> Set-NetFirewallRule -DisplayGroup 'Remote Event Log Management' -Enabled true -PassThru |
Housekeeping
Remove Windows Defender.
| PS C:\> Uninstall-WindowsFeature -Name Windows-Defender |
Finally reboot the machine to commit the machine name and IP changes.
| PS C:\> Restart-Computer |
Dell OpenManage System Administrator
If you are running this on a Dell server, you might also want to install OMSA. At this point you should be able to access the administrative shares for windows.
Copy the OMSA installer onto the Hyper-V Server using the admin shares (eg. \\SKYE\d$).
Run the EXE from the command prompt or PowerShell to extract to C:\OpenManage.
Run the pre-requisite checker.
| PS C:\> C:\OpenManage\windows\PreReqChecker\RunPreReqChecker.exe /s |
Provided no errors are seen, install OMSA.
| PS C:\> msiexec /i C:\OpenManage\windows\SystemsManagementx64\SysMgmtx64.msi |
During the installation it might be beneficial to choose Custom and then add the Remote Manager.
Once installed a firewall rule will be needed to access OMSA from another computer.
| PS C:\> New-NetFirewallRule -Name Dell_OMSA -DisplayName "Dell OMSA" -Description "Dell OMSA Web Management" -Protocol TCP -Enabled True -Profile Any -Action Allow -LocalPort 1311 |
References
