search

gsuberland / lbfo_win10

Re-enable NIC teaming (LBFO) in Windows 10 using components from Windows Server.
34 stars 11 forks source link

I was re-imaging some machines.. #2

Closed Teravus closed 3 years ago

Teravus commented 3 years ago

I was reimaging some machines anyway.. so I tried the process on the blog post with 20H2. It turns out the process still works with one caveat. To get the service to show up in the network install box, you have to sign the driver yourself also, then pick 'have disk' and pick the driver. A self-signed authenticode cert is fine assuming you import your signing cert into the system. After that you can start the service from the command prompt and run the powershell commandlets .. and you end up with a team. Also, can confirm that you get a teamed adapter on a regular (non-vm) machine. The adapter 'works' for network access. I'd have to spend more time to deeply inspect the traffic from the interfaces to know if it is truly 'teaming'. These are slated for re-imaging, and I'm out of time.. but, wanted to let you know the process is still working on 20H2 with a wrinkle. *edit: change 'working' to 'teaming' for clarity.

Teravus commented 3 years ago

Closing because it isn't really an issue. Just some experiences with the process.

Teravus commented 3 years ago

One thing that I left out that is semi-important. If you want your team to come up on system reboot, you need to either start the service driver yourself, "sc start mslbfoprovider"

Or create a 'Task Scheduler' task, triggered on system start that can run "c:\windows\system32\sc.exe start mslbfoprovider".