This stems from MSKB 3109099.
I have a bunch of servers (16 currently enough so I don't want to do this manually) that are using the Microsoft NIC teaming in Server 2012R2. They already have the referenced hotfix installed (Actually, they have KB2919355 installed, which apparently supersedes/includes the hotfix in 3109099 since my servers say the hotfix isn't applicable to them).
In order to enable the behavior I want, I need to add a 32-bit DWORD ('LacpTimeout' with a value of 0) to a key that is variable (GUID) across all the machines.
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMsLbfoProviderParametersNdisAdapters<GUID>
<GUID> is different on every machine, and some machines may have more than one (if they have multiple NIC teams). I want to add this DWORD to all of them.
Is there some way to do this using GPO / GPP?
I have a bunch of servers (16 currently enough so I don't want to do this manually) that are using the Microsoft NIC teaming in Server 2012R2. They already have the referenced hotfix installed (Actually, they have KB2919355 installed, which apparently supersedes/includes the hotfix in 3109099 since my servers say the hotfix isn't applicable to them).
In order to enable the behavior I want, I need to add a 32-bit DWORD ('LacpTimeout' with a value of 0) to a key that is variable (GUID) across all the machines.
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMsLbfoProviderParametersNdisAdapters<GUID>
<GUID> is different on every machine, and some machines may have more than one (if they have multiple NIC teams). I want to add this DWORD to all of them.
Is there some way to do this using GPO / GPP?
Configuring NIC teaming within Server 2016 is dead simple – but let’s go through the process anyways. The first step is actually enabling the NIC teaming functionality in Windows – as shown below this is done, as is most other tasks within Windows Server now, through the Server Manager by simply clicking the link next to the NIC Teaming label on the server properties page. Tagged: catalyst, cisco, LACP, NIC Teaming, Windows Server 2012. 2 comments I wanted to increase throughput to our file server based on Windows Server 2012, as it was getting hit pretty hard at peak hours.