Hyper-V:Install: Difference between revisions

From Wiki³
(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...")
 
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{DISPLAYTITLE:{{TitleIcon|hyperv=true}} Hyper-V Server 2016: Installation}}<metadesc>How to setup Hyper-V Server 2016 on baremetal.</metadesc>
{{DISPLAYTITLE:{{TitleIcon|hyperv=true}} Windows Server 2016 Core: Hyper-V Installation}}<metadesc>How to setup Hyper-V on Windows Server 2016 Core.</metadesc>
<div id="tocalign">__TOC__</div>
<div id="tocalign">__TOC__</div>
{{UnderConstruction}}
{{UnderConstruction}}
{{Back|Windows}}
{{Back|Windows}}
= {{Icon24|sitemap}} Introduction =
= {{Icon24|sitemap}} Introduction =
Microsoft 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.<ref>{{cite web|url=https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-server-2016|title=Microsoft Hyper-V Server 2016|publisher=Microsoft Docs}}</ref> Hyper-V Server has a Windows Server Core experience and as such doesn't have a graphical user interface (GUI).
The Server Core option is a minimal installation option that is available when you are deploying the Standard or Datacenter edition of Windows Server. Server Core includes most but not all server roles. Server Core has a smaller disk footprint, and therefore a smaller attack surface due to a smaller code base.<ref>{{cite web|url=https://docs.microsoft.com/en-us/windows-server/administration/server-core/what-is-server-core|title=What is Server Core?|publisher=Microsoft Docs}}</ref> Most notably, no Windows Explorer shell is installed. All configuration and maintenance is done entirely through command-line interface windows, or by connecting to the machine remotely using Microsoft Management Console (MMC), remote server administration tools, and PowerShell.<ref>{{cite web|url=https://en.wikipedia.org/wiki/Server_Core|title=Server Core|publisher=Wikipedia}}</ref>


Testing was done on my Dell PowerEdge R610, the following image was used:
Microsoft Hyper-V, codenamed Viridian and formerly known as Windows Server Virtualization, is a native hypervisor; it can create virtual machines on x86-64 systems running Windows.<ref>{{cite web|url=https://en.wikipedia.org/wiki/Hyper-V|title=Hyper-V|publisher=Wikipedia}}</ref>
{{Note|icon=false|1={{Icon|disc-blue}} en_microsoft_hyper-v_server_2016_x64_dvd_9347277.iso}}
 
Testing was done on my Dell PowerEdge R620, the following image was used:
{{Note|icon=false|1={{Icon|disc-blue}} en_windows_server_version_1803_x64_dvd_12063476.iso}}


= {{Icon24|sitemap}} Installation =
= {{Icon24|sitemap}} 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.
Insert the Server 2016 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.
{{Note|1=Hyper-V Server only requires ~32GB of hard drive space. Perform a "Custom" install, partitioning the {{mono|C:}} drive accordingly, then assign the rest to {{mono|D:}} for virtual machines.}}
{{Note|1=A Hyper-V Server only requires ~32GB of hard drive space. Perform a "Custom" install, partitioning the {{mono|C:}} drive accordingly, then assign the rest to {{mono|D:}} for virtual machines.}}
Upon reboot you will be prompted to set an {{mono|Administrator}} password, doing so will log into the machine finalizing the installation.
Upon reboot you will be prompted to set an {{mono|Administrator}} password, doing so will log into the machine finalizing the installation.


Line 21: Line 23:


Rename the computer.
Rename the computer.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Rename-Computer}} {{white|-NewName}} SKYE}}
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Rename-Computer}} {{white|-NewName}} {{cyanBold|"NATASHA"}}}}
Join the local workgroup.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Add-Computer}} {{white|-WorkGroupName}} {{cyanBold|"AH42"}}}}
List the current network adapters.
List the current network adapters.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Get-NetAdapter}} {{white|-Physical}}}}
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Get-NetAdapter}} {{white|-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.
The Dell R620 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.
First create the NIC team.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|New-NetLbfoTeam}} {{white|-Name}} {{blueBold|"Hyper-V Team"}} {{white|-TeamMembers}} {{blueBold|"Ethernet 2"}}, {{blueBold|"Ethernet 3"}}, {{blueBold|"Ethernet 4"}}}}
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|New-NetLbfoTeam}} {{white|-Name}} {{cyanBold|"Hyper-V Team"}} {{white|-TeamMembers}} {{cyanBold|"Ethernet 2"}}, {{cyanBold|"Ethernet 3"}}, {{cyanBold|"Ethernet 4"}}}}
Verify it created the team correctly.
Verify it created the team correctly.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Get-NetLbfoTeam}}}}
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Get-NetLbfoTeam}}}}
{{Note|1=If you need to specify a VLAN for the NIC team, use {{mono|Set-NetLbfoTeamNic -Team "Hyper-V Team" -VlanID 123}}.}}
{{Note|1=If you need to specify a VLAN for the NIC team, use {{mono|Set-NetLbfoTeamNic -Team "Hyper-V Team" -VlanID 123}}.}}
Rename the original adapters for consistency.
Rename the original adapters for consistency.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Rename-NetAdapter}} {{white|-Name}} {{blueBold|"Ethernet"}} {{white|-NewName}} {{blueBold|"Management"}}}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Rename-NetAdapter}} {{white|-Name}} {{cyanBold|"Ethernet"}} {{white|-NewName}} {{cyanBold|"Management"}}}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Rename-NetAdapter}} {{white|-Name}} {{blueBold|"Ethernet 2"}} {{white|-NewName}} {{blueBold|"Ethernet Team 1"}}}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Rename-NetAdapter}} {{white|-Name}} {{cyanBold|"Ethernet 2"}} {{white|-NewName}} {{cyanBold|"Ethernet Team 1"}}}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Rename-NetAdapter}} {{white|-Name}} {{blueBold|"Ethernet 3"}} {{white|-NewName}} {{blueBold|"Ethernet Team 2"}}}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Rename-NetAdapter}} {{white|-Name}} {{cyanBold|"Ethernet 3"}} {{white|-NewName}} {{cyanBold|"Ethernet Team 2"}}}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Rename-NetAdapter}} {{white|-Name}} {{blueBold|"Ethernet 4"}} {{white|-NewName}} {{blueBold|"Ethernet Team 3"}}}}
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Rename-NetAdapter}} {{white|-Name}} {{cyanBold|"Ethernet 4"}} {{white|-NewName}} {{cyanBold|"Ethernet Team 3"}}}}
=== Static IP ===
=== 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.
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.
Remove DHCP from both adapters.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-NetIPInterface}} {{white|-InterfaceAlias}} {{blueBold|"Management"}} {{white|-Dhcp}} Disabled}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-NetIPInterface}} {{white|-InterfaceAlias}} {{cyanBold|"Management"}} {{white|-Dhcp}} Disabled}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-NetIPInterface}} {{white|-InterfaceAlias}} {{blueBold|"Hyper-V Team"}} {{white|-Dhcp}} Disabled}}
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-NetIPInterface}} {{white|-InterfaceAlias}} {{cyanBold|"Hyper-V Team"}} {{white|-Dhcp}} Disabled}}
Remove the current IP addresses from both adapters (use {{mono|A}} to choose Yes to All when removing).
Remove the current IP addresses from both adapters (use {{mono|A}} to choose Yes to All when removing).
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Get-NetAdapter}} {{white|-InterfaceAlias}} {{blueBold|"Management"}} {{!}} {{yellowBold|Remove-NetIPAddress}}}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Get-NetAdapter}} {{white|-InterfaceAlias}} {{cyanBold|"Management"}} {{!}} {{yellowBold|Remove-NetIPAddress}}}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Get-NetAdapter}} {{white|-InterfaceAlias}} {{blueBold|"Hyper-V Team"}} {{!}} {{yellowBold|Remove-NetIPAddress}}}}
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Get-NetAdapter}} {{white|-InterfaceAlias}} {{cyanBold|"Hyper-V Team"}} {{!}} {{yellowBold|Remove-NetIPAddress}}}}
Put both of the network adapters on Private networks.
{{console|prompt=false|powershell=true|1=PS C:\> {{greenBold|$Profile1}} {{=}} {{yellowBold|Get-NetConnectionProfile}} {{white|-InterfaceAlias}} {{cyanBold|"Management"}}}}
{{margin}}
{{console|prompt=false|powershell=true|1=PS C:\> {{greenBold|$Profile2}} {{=}} {{yellowBold|Get-NetConnectionProfile}} {{white|-InterfaceAlias}} {{cyanBold|"Hyper-V Team"}}}}
{{margin}}
{{console|prompt=false|powershell=true|1=PS C:\> {{greenBold|$Profile1}}.NetworkCategory {{=}} {{cyanBold|"Private"}}}}
{{margin}}
{{console|prompt=false|powershell=true|1=PS C:\> {{greenBold|$Profile2}}.NetworkCategory {{=}} {{cyanBold|"Private"}}}}
{{margin}}
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-NetConnectionProfile}} {{white|-InputObject}} {{greenBold|$Profile1}}}}
{{margin}}
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-NetConnectionProfile}} {{white|-InputObject}} {{greenBold|$Profile2}}}}
Set the IP information for both adapters.
Set the IP information for both adapters.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|New-NetIPAddress}} {{white|-InterfaceAlias}} {{blueBold|"Management"}} {{white|-IPAddress}} 10.0.42.10 {{white|-AddressFamily}} IPv4 {{white|-PrefixLength}} 24 {{white|-DefaultGateway}} 10.0.42.1}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|New-NetIPAddress}} {{white|-InterfaceAlias}} {{cyanBold|"Management"}} {{white|-IPAddress}} 10.0.42.10 {{white|-AddressFamily}} IPv4 {{white|-PrefixLength}} 24 {{white|-DefaultGateway}} 10.0.42.1}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|New-NetIPAddress}} {{white|-InterfaceAlias}} {{blueBold|"Hyper-V Team"}} {{white|-IPAddress}} 10.0.42.11 {{white|-AddressFamily}} IPv4 {{white|-PrefixLength}} 24 {{white|-DefaultGateway}} 10.0.42.1}}
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|New-NetIPAddress}} {{white|-InterfaceAlias}} {{cyanBold|"Hyper-V Team"}} {{white|-IPAddress}} 10.0.42.11 {{white|-AddressFamily}} IPv4 {{white|-PrefixLength}} 24 {{white|-DefaultGateway}} 10.0.42.1}}
Also add DNS servers for both.
Also add DNS servers for both.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-DnsClientServerAddress}} {{white|-InterfaceAlias}} {{blueBold|"Management"}} {{white|-ServerAddress}} 10.0.42.1}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-DnsClientServerAddress}} {{white|-InterfaceAlias}} {{cyanBold|"Management"}} {{white|-ServerAddress}} 10.0.42.1}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-DnsClientServerAddress}} {{white|-InterfaceAlias}} {{blueBold|"Hyper-V Team"}} {{white|-ServerAddress}} 10.0.42.1}}
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-DnsClientServerAddress}} {{white|-InterfaceAlias}} {{cyanBold|"Hyper-V Team"}} {{white|-ServerAddress}} 10.0.42.1}}


== {{Icon|notebook}} Remote Management ==
== {{Icon|notebook}} Remote Management ==
Line 56: Line 72:


Enable WinRM.
Enable WinRM.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Enable-PSRemoting}} {{white|-SkipNetworkProfileCheck}} {{white|-Force}}}}
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Enable-PSRemoting}} {{white|-Force}}}}
Enable remote authentication acceptance.
Enable remote authentication acceptance.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Enable-WSManCredSSP}} {{white|-Role}} server}}
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Enable-WSManCredSSP}} {{white|-Role}} server}}
Enable firewall rules for remote management.
Enable firewall rules for remote management.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-NetFirewallRule}} {{white|-DisplayGroup}} {{blueBold|'Windows Management Instrumentation (WMI)'}} {{white|-Enabled}} true {{white|-PassThru}}}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-NetFirewallRule}} {{white|-DisplayGroup}} {{cyanBold|'Windows Management Instrumentation (WMI)'}} {{white|-Enabled}} true {{white|-PassThru}}}}<br/>
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-NetFirewallRule}} {{white|-DisplayGroup}} {{blueBold|'Remote Event Log Management'}} {{white|-Enabled}} true {{white|-PassThru}}}}
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-NetFirewallRule}} {{white|-DisplayGroup}} {{cyanBold|'Remote Event Log Management'}} {{white|-Enabled}} true {{white|-PassThru}}}}


== {{Icon|notebook}} Housekeeping ==
== {{Icon|notebook}} Housekeeping ==
Line 68: Line 84:
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}} Hyper-V =
Return to PowerShell and use the following command to install Hyper-V and required pre-requisites.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Install-WindowsFeature}} {{white|-Name}} Hyper-V {{white|-IncludeManagementTools -Restart}}}}
== {{Icon|notebook}} Hyper-V Configuration ==
You should now be able to connect to the machine remotely from Hyper-V Manager.
Be sure to run through the Hyper-V Settings, I typically setup a VM and VHD directory (eg. {{mono|D:\VMs\}}, {{mono|D:\VHDs\}}) and then enable {{mono|Enhanced Session Mode Policy}}.
Next open {{mono|Virtual Switch Manager}} and create a new {{mono|External}} virtual switch bound to the {{mono|Microsoft Network Adapter Multiplexor Driver}}.
Make sure {{mono|Allow management operating system to share this network adapter}} is enabled.
== {{Icon|notebook}} Secure Boot ==
While the virtual machine is in the OFF state, run the following command on the physical Hyper-V host to disable secure boot.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-VMFirmware}} {{cyanBold|'VMNAME'}} {{white|-EnableSecureBoot}} off}}
== {{Icon|notebook}} Nested Virtualization ==
While the virtual machine is in the OFF state, run the following command on the physical Hyper-V host to enable nested virtualization.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Set-VMProcessor}} {{white|-VMName}} {{cyanBold|"VMNAME"}} {{white|-ExposeVirtualizationExtensions}} {{greenBold|$True}}}}
= {{Icon24|sitemap}} Dell OMSA =
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|\\NATASHA\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}} {{cyanBold|"Dell OMSA"}} {{white|-Description}} {{cyanBold|"Dell OMSA Web Management"}} {{white|-Protocol}} TCP {{white|-Enabled}} True {{white|-Profile}} Any {{white|-Action}} Allow {{white|-LocalPort}} 1311}}
= {{Icon24|sitemap}} NFS =
Install the NFS Server feature.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Install-WindowsFeature}} FS-NFS-Service {{white|-IncludeManagementTools}}}}
Create the shares.
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|New-NfsShare}} {{white|-Name}} {{cyanBold|'ftp'}} {{white|-Path}} {{cyanBold|'D:\NFS\FTP'}} {{white|-EnableUnmappedAccess}} {{greenBold|$True}} {{white|-Authentication}} sys}}
{{margin}}
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|New-NfsShare}} {{white|-Name}} {{cyanBold|'www'}} {{white|-Path}} {{cyanBold|'D:\NFS\WWW'}} {{white|-EnableUnmappedAccess}} {{greenBold|$True}} {{white|-Authentication}} sys}}
Set IP restrictions
{{console|prompt=false|powershell=true|1=PS C:\> {{yellowBold|Grant-NfsSharePermission}} {{white|-Name}} {{cyanBold|'www'}} {{white|-ClientName}} {{cyanBold|'10.0.42.30'}} {{white|-ClientType}} {{cyanBold|'Host'}} {{white|-Permission}} {{cyanBold|'readwrite'}} {{white|-AllowRootAccess}} {{greenBold|$True}}}}
= {{Icon24|sitemap}} Conclusion =
The server should now be completely setup for VMs.


= {{Icon24|book-brown}} References =
= {{Icon24|book-brown}} References =
<references/>
<references/>


[[Category:Windows]]
[[Category:Windows]]

Latest revision as of 01:08, 11 November 2018

IconUNDER CONSTRUCTION: The document is currently being modified!
Icon  Back to Category:Windows

Icon Introduction

The Server Core option is a minimal installation option that is available when you are deploying the Standard or Datacenter edition of Windows Server. Server Core includes most but not all server roles. Server Core has a smaller disk footprint, and therefore a smaller attack surface due to a smaller code base.[1] Most notably, no Windows Explorer shell is installed. All configuration and maintenance is done entirely through command-line interface windows, or by connecting to the machine remotely using Microsoft Management Console (MMC), remote server administration tools, and PowerShell.[2]

Microsoft Hyper-V, codenamed Viridian and formerly known as Windows Server Virtualization, is a native hypervisor; it can create virtual machines on x86-64 systems running Windows.[3]

Testing was done on my Dell PowerEdge R620, the following image was used:

Icon en_windows_server_version_1803_x64_dvd_12063476.iso

Icon Installation

Insert the Server 2016 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.

IconA 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

Icon Networking

Before Hyper-V itself can be setup, a strong networking backbone needs to be setup.

Rename the computer.

PS C:\> Rename-Computer -NewName "NATASHA"

Join the local workgroup.

PS C:\> Add-Computer -WorkGroupName "AH42"

List the current network adapters.

PS C:\> Get-NetAdapter -Physical

The Dell R620 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
IconIf 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

Put both of the network adapters on Private networks.

PS C:\> $Profile1 = Get-NetConnectionProfile -InterfaceAlias "Management"
 
PS C:\> $Profile2 = Get-NetConnectionProfile -InterfaceAlias "Hyper-V Team"
 
PS C:\> $Profile1.NetworkCategory = "Private"
 
PS C:\> $Profile2.NetworkCategory = "Private"
 
PS C:\> Set-NetConnectionProfile -InputObject $Profile1
 
PS C:\> Set-NetConnectionProfile -InputObject $Profile2

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

Icon 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 -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

Icon 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

Icon Hyper-V

Return to PowerShell and use the following command to install Hyper-V and required pre-requisites.

PS C:\> Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart

Icon Hyper-V Configuration

You should now be able to connect to the machine remotely from Hyper-V Manager.

Be sure to run through the Hyper-V Settings, I typically setup a VM and VHD directory (eg. D:\VMs\, D:\VHDs\) and then enable Enhanced Session Mode Policy.

Next open Virtual Switch Manager and create a new External virtual switch bound to the Microsoft Network Adapter Multiplexor Driver.

Make sure Allow management operating system to share this network adapter is enabled.

Icon Secure Boot

While the virtual machine is in the OFF state, run the following command on the physical Hyper-V host to disable secure boot.

PS C:\> Set-VMFirmware 'VMNAME' -EnableSecureBoot off

Icon Nested Virtualization

While the virtual machine is in the OFF state, run the following command on the physical Hyper-V host to enable nested virtualization.

PS C:\> Set-VMProcessor -VMName "VMNAME" -ExposeVirtualizationExtensions $True

Icon Dell OMSA

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. \\NATASHA\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

Icon NFS

Install the NFS Server feature.

PS C:\> Install-WindowsFeature FS-NFS-Service -IncludeManagementTools

Create the shares.

PS C:\> New-NfsShare -Name 'ftp' -Path 'D:\NFS\FTP' -EnableUnmappedAccess $True -Authentication sys
 
PS C:\> New-NfsShare -Name 'www' -Path 'D:\NFS\WWW' -EnableUnmappedAccess $True -Authentication sys

Set IP restrictions

PS C:\> Grant-NfsSharePermission -Name 'www' -ClientName '10.0.42.30' -ClientType 'Host' -Permission 'readwrite' -AllowRootAccess $True

Icon Conclusion

The server should now be completely setup for VMs.

Icon References

  1. ^ "What is Server Core?". Microsoft Docs. https://docs.microsoft.com/en-us/windows-server/administration/server-core/what-is-server-core. 
  2. ^ "Server Core". Wikipedia. https://en.wikipedia.org/wiki/Server_Core. 
  3. ^ "Hyper-V". Wikipedia. https://en.wikipedia.org/wiki/Hyper-V. 
Retrieved from "https://kyau.net/w/index.php?title=Hyper-V:Install&oldid=4118"