Windows 10: Hyper V, LACP, Teamed Adapters and no DHCP

I just created a vSwitch in Hyper-V attached to a LACP teamed adapter. Teaming was done via the Server Manager. Server version is 2012 R2. See configuration below.








I moved the all the VM's to the new vSwitch "LACP" above. Server applications and data shares are contactable and working. DHCP Server installed on the domain controller is not, although data shares etc on the DC are fine. Moving the DC VM back to the original vSwitch "Phys NIC 1" above, containing a single non-teamed adapter it works fine. Move the DC back to the teamed vSwitch, and DHCP once again does not work. I also just found that my Windows Deployment Server will not deploy images if on the "LACP" vSwitch, but on the orginal vSwitch all is fine.



Does anyone have any idea why this would be happening / where I have gone wrong?


The teamed adapters are connected to a HP 1920 series enterprise switch. See config images below.,








:)

 

Hyper-V on windows 10 Pro [solved]

Hi,

I have a problem setting up Hyper-V on windows 10 professional. I tryed many steps including: using powershell to enable hyper-v features, using advanced program setup dialog and using DISM. The hyper-v software is installed, but cant run any contrainer,
saying virtualization should be enabled. It is enabled in the BIOS and process viewer shows it as Virtualization: Enabled. I have success with virtualbox and vmware on this computer, but not with hyper-V. I tryed fully uninstall virtualbox, vmware, hyper-v,
reboot then install hyper-v and still no success.

Tech support says there maybe hardware incompabilities, but dont refer any software/docs to resolve this issue.

Please help run hyper-V

Processor: Intel Core i3-4170 CPU @3.70GHz

Haswell Socket 1150 LGA

Mainboard: ASUSTeK COMPUTER INC. H81M-K

BIOS: American Megatrends INC. version 3602 Date 03/26/2018

PS D:\projects\bp> systeminfo

OS Name: Microsoft Windows 10 Pro

OS Version: 10.0.17134 N/A Build 17134

OS Manufacturer: Microsoft Corporation

OS Configuration: Standalone Workstation

OS Build Type: Multiprocessor Free

Registered Owner: Certified Windows

Registered Organization:

Product ID: 00331-10000-00001-AA766

Original Install Date: 05.05.2018, 6:10:44

System Boot Time: 11.11.2018, 5:58:05

System Manufacturer: ASUS

System Model: All Series

System Type: x64-based PC

Processor(s): 1 Processor(s) Installed.

[01]: Intel64 Family 6 Model 60 Stepping 3 GenuineIntel ~3700 Mhz

BIOS Version: American Megatrends Inc. 3602, 26.03.2018

Windows Directory: C:\WINDOWS

System Directory: C:\WINDOWS\system32

Boot Device: \Device\HarddiskVolume1

Input Locale: en-us;English (United States)

Total Physical Memory: 16 254 MB

Available Physical Memory: 10 807 MB

Virtual Memory: Max Size: 31 102 MB

Virtual Memory: Available: 23 590 MB

Virtual Memory: In Use: 7 512 MB

Page File Location(s): C:\pagefile.sys

D:\pagefile.sys

Domain: RFGHFGH

Logon Server: \\FUCKINGCOMPUTER

Hotfix(s): 7 Hotfix(s) Installed.

[01]: KB4100347

[02]: KB4338853

[03]: KB4343669

[04]: KB4456655

[05]: KB4457146

[06]: KB4462930

[07]: KB4462933

Network Card(s): 10 NIC(s) Installed.

[01]: Hyper-V Virtual Ethernet Adapter

Connection Name: vEthernet (Коммутатор по у)

DHCP Enabled: Yes

DHCP Server: 255.255.255.255

IP address(es)

[01]: 172.28.36.145

[02]: fe80::1d84:a10d:e30b:c0d8

[02]: Realtek PCIe GbE Family Controller

Connection Name: sknt

DHCP Enabled: Yes

DHCP Server: 192.168.0.1

IP address(es)

[01]: 192.168.0.100

[02]: fe80::8c5a:60bd:5502:7f42

[03]: Hyper-V Virtual Ethernet Adapter

Connection Name: vEthernet (DockerNAT)

DHCP Enabled: No

IP address(es)

[01]: 10.0.75.1

[04]: VirtualBox Host-Only Ethernet Adapter

Connection Name: VirtualBox Host-Only Network #5

DHCP Enabled: No

IP address(es)

[01]: 192.168.56.1

[02]: fe80::9920:c9e3:1a62:9b31

[05]: Hyper-V Virtual Ethernet Adapter

Connection Name: vEthernet (HvsiIcs)

Status: Hardware not present

[06]: VirtualBox Host-Only Ethernet Adapter

Connection Name: VirtualBox Host-Only Network #6

DHCP Enabled: No

IP address(es)

[01]: 192.168.99.1

[02]: fe80::71f8:8c5d:6572:3503

[07]: Hyper-V Virtual Ethernet Adapter

Connection Name: vEthernet (nat)

DHCP Enabled: Yes

DHCP Server: 255.255.255.255

IP address(es)

[01]: 172.23.224.1

[02]: fe80::1861:2221:6f05:f364

[08]: Hyper-V Virtual Ethernet Adapter

Connection Name: vEthernet (2b5253f75d3dcd1)

DHCP Enabled: Yes

DHCP Server: 255.255.255.255

IP address(es)

[01]: 172.31.240.1

[02]: fe80::7039:6490:4ea0:2010

[09]: Hyper-V Virtual Ethernet Adapter

Connection Name: vEthernet (5c881ef6de6c653)

DHCP Enabled: Yes

DHCP Server: 255.255.255.255

IP address(es)

[01]: 192.168.176.1

[02]: fe80::1131:3644:1c71:7890

[10]: Hyper-V Virtual Ethernet Adapter

Connection Name: vEthernet (e9aabfd7feea2be)

DHCP Enabled: Yes

DHCP Server: 255.255.255.255

IP address(es)

[01]: 172.18.16.1

[02]: fe80::a569:9954:e3b2:6f0d

Hyper-V Requirements: VM Monitor Mode Extensions: Yes

Virtualization Enabled In Firmware: Yes

Second Level Address Translation: Yes

Data Execution Prevention Available: Yes

 

Hyper V deativication

Hi Geoffrey,

Hyper-V lets you run an operating system or computer system as a virtual machine on Windows. Before proceeding in disabling
Hyper-V, please create a backup of your files for security purposes.

To disable Hyper-V, please follow the steps below:

• On the Cortana search box, type Turn Windows Features on or off and press
  Enter.
• Look for the Hyper-V folder.
• Uncheck the tick-box next to the main Hyper-V folder and click
  OK.
• Restart your PC.

Should you have further questions, please let us know.

 

Windows 10 Pro Hyper-V Ethernet Adapter Driver Corrupted

On my windows 10 pro OS the Hyper-V Ethernet adapter has disappeared form the network adapters listing and in device manager, the Hyper-V Ethernet Adapter is showing error, cannot start message, corrupted driver. Tried updating the driver, but windows
reports the driver install is corrupted. How do I repair the driver? Tom J