Cannot create teaming after inplace upgrade from 2012 to 2016

Question

Hello after an in place upgrade of windows server 2012R2 to 2016 everything works except the network teaming configuration

When trying to create a new team I receive Two errors :

1. When trying to create a team with the same name like before the upgrade I get an error stating the teaming name is in use
2. When trying to create a team with a different name the teaming is created but all interfaces under it are in “fault” status and cannot be used

The teaming itself stayed disabled.
There is no visible teaming configuration inplace on powershell or the GUI

Methods I tried with no success:

1. Tried rebooting several times
2. Tried removing the network interfaces from device manager and reinstall the drives
3. Tried to used Broadcom network utility to examine the network cards there is no leftover teaming present
4. Tried using the powershell commands
5. Tried removing and adding hyperV role again

I found a technet article claiming that some registry entries need to be erased and a folder needs to be deleted

https://social.technet.microsoft.com/Forums/security/en-US/e2cc0c20-2f73-46d5-9db3-96af0d028f2c/windows-2012-network-teaming-broken-quothost-unmanageablequot?forum=winserverPN

net stop winmgmt
rename the folder 'Repository' underneath %windir%\system32\wbem
restart the system
winmgmt /resetrepository
gpupdate /force
disable all the network adapters
remove HKLM\SYSTEM\CurrentControlSet\Control\Network\Config
enable all the network adapters
enable nic teaming

But I can’t get the winmgmt service to stop
Seems like to many network services are using this service

I would appreciate any help on this subject

Thanks

Answer 1

Hello the issue was resolved by simply using the HyperV embedded teaming option

Instead of the native teaming that is using the OS embedded teaming is creating teaming on the virtual switch level therefore no need for special drivers.

This was introduced in windows Server 2016
We have tested it for both a vm vIrtual switch and a management virtual switch containing cluster and live migration networks.

Answer 2

An in-place upgrade is never recommended. I'd check here and with manufacturer about support for the hardware.
https://www.windowsservercatalog.com/

Also check the manufacturer for the latest firmware, ROM bios, chipset and driver support packs.

--please don't forget to Accept as answer if the reply is helpful--

Answer 3

Hi,

Thanks for posting in Q&A platform.

Please kindly check if the following article is helpful to you.

Troubleshooting NIC Teaming

If there is no progress, I would suggest you contact Microsoft Customer Services and Support to get an efficient solution:

https://support.microsoft.com/en-us/help/4051701/global-customer-service-phone-numbers

Have a nice day!

Best Regards,
Sunny

----------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.