Event banner
Event details
26 Comments
Thank you for joining us this week for the Windows Server Summit! Q&A is now closed, but all sessions are available on demand so you can watch and learn when it is convenient for you. We hope you enjoyed the event.
- Does Network ATC work on a standalone server (not a cluster node)? From the session Network HUD is Arc extension. Does that mean you have to have an Azure subscription to use this feature?
- Param_Mahajan
Microsoft
Network ATC will work on standalone servers. We are still collecting feedback from customers through public preview to understand which standalone scenarios best suit Network ATC. If you have any feedback or scenarios in mind for Network ATC on standalone servers, please reach out to us at: edgenetfeedback@microsoft.com. As for Network HUD, you will need an azure subscription to use Network HUD.- Thank you Param for clarifying!
you have to enable SR-IOV and VF in the UEFI on the NICs on the host prior creating the vSwitch (with NetworkATC)
- Lately I have seen a security recommendation to disable LLDP on LinkedIn. This was about hardening for Windows Client and Server. As a heads-up that this might be counterproductive and might encounter new support cases because of this move.
- AnirbanPaulHi Karl, can you provide more information about where you see this recommendation? Network HUD relies on LLDP to get information from the physical switches. So, for Network HUD to function effectively, LLDP is a requirement. This is documented for Azure Stack HCI here: https://learn.microsoft.com/en-us/azure-stack/hci/concepts/physical-network-requirements?tabs=overview%2C23H2reqs#network-switch-requirements. We will have similar documentation for Windows Server 2025.
- I would need to dig where I have seen it from linkedin but when I read about that, believe this was about an Intune Policy, I saw dark clouds, if other would adapt that as a general recommendation across fleets. Hope you see my point.
- the demo about PCIe limitation and PowerShell is really worth, thanks for bringing this up! Is it also included in NetworkATC your FAQ?
- Param_MahajanAt the moment it is linked to the Network HUD blog. We will look into adding this to the FAQ page as well!
- a backlink on Network ATC should be good enough if not already. You can be all proud with upcoming package. Great work!
- do you plan anything for brownfield where customers coming from LFBO and not SET to make it easier with transition. Since LFBO is still very visible in GUI and muscle memory still in Windows Server 2019 customers using it instead of more hidden / not so obvious SET switch. Therewas once a PS to convert LFBO to SET but it is no longer working.
- Param_MahajanCurrently 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!
- do you plan to "acknowledge" issues (for a time) like outdated drivers? Currently it is like only 6 months driver. 2 / 3 years sounds a bit much given the lifetime of 5 years in LTSC mainstream support.
- AnirbanPaulGreat feedback, Karl. I agree that 6 months was too low and setting it to 2/3 years is also not accurate. We are trying to work with NIC vendors to come up with a generic process to identify outdated drivers. Since this is not standard across vendors, it may take some time to get to the perfect solution.
- That's great! Much appreciate your team efforts. The Network HUD is really a gamechanger! In future you might find time and consider a WAC extension where we could see all messages and things of HUD in the navigation pane of a Cluster or Node, just like NetworkATC. This would be super cool!
- the improvements are amazing! Happy times for Windows Server 2025 customers, and hopefully soon Azure Stack HCI customers. too. Thank you so much!
- Microsoft and its abbreviations... What stands ATC for?
- AnirbanPaulATC is not an acronym. It is a proper noun. This was conceived on the concept of an Air Traffic Control system to manage and direct traffic.
- Can we look forward into more controls of NetworkATC in WAC extension? I am thinking about: - IP assignment and other for compute / management? - change / viewing Global or network overrides in WAC There is still some concurrency of Cluster Max number of LiveMigration in NetATC vs CLuster option in Windows Admin Center which defaults to 1, even though NetATC is set to four. I have once posted about it here. https://techcommunity.microsoft.com/t5/azure-stack/azure-stack-hci-keeps-setting-livemigration-to-1-here-is-why/m-p/3850965
- Param_MahajanHey Karl, we are working on bringing additional Network ATC functionality to the WAC Day-100 UX experience. We will consider your feedback and reach out to you for additional questions and validation if needed. As for the concurrency with Cluster option in WAC, I will check on this offline and follow up with you.
