Event banner
Event details
- Param_Mahajan
Microsoft
Currently we have no plans on rolling out support for brownfield migrations for customers coming from LBFO to SET. If you have customers who are looking for this support, please reach out to us. We would love to learn more details and consider it for upcoming releases.Will do! Currently they are on WS 2019 and I am seeing more and more customers with LFBO still that's what I am flagging.
It is hard to convince them using SET instead. When they would upgrade their Cluster to WS 2022 the setup will stop the show and flagging their LFBO with a hard block.Since NetworkATC and NetworkHUD merits starting with Windows Server 2025, I suppose the most "might" not continue with LFBO but nothing prevents admins that do not know to create LFBO on WS 2022 / 2025 once again. So what could happen is they delete the LFBO upgrade and create it new and consider this as an "obstacle" rather realizing the issue or limitations.
In forecast of these complications I posted this a while ago. I am aware this is not exaclty your scope, but I trust you can check that internally, so this might prevent admins using LFBO in WS 2022 or at least WS 2025 which would prevent the adoption of NetworkATC / HUD.
This is true for customers using Hyper-V + S2D and Hyper-V + SAN.
https://techcommunity.microsoft.com/t5/windows-server-insiders/feature-request-please-remove-nic-teaming-from-windows-server/td-p/3959275
I hope you consider this verbose heads-up useful. Thank you for your time and consideration!
