JamesKehr Hi James, It's not in the interests for a platform vendor to supply the tool to test their platform, particularly if that tool is platform or os specific. It has to be broadly accepted as reliable, open & transparent to code changes, and vendor independent. Iperf 2 goes back like 15 years or so in our use cases covering at least ten kernel versions and multiple platforms, including things like set top boxes. We have to cover most every platform that uses a Wi-Fi chip which includes Windows but much more.
A suggestion is to inform MSFT engineers to support a tool like iperf 2 vs roll their own, at least for external users. Internal tools are a different matter. External, industry standard, tools really need to have a priority on vendor neutrality and industry acceptance. Your blog is a bit misguided in that context, suggesting not to use iperf 3 for a vendor specific tool isn't a good approach by my opinion. Better is to use an industry standard tool like iperf 2 which is based on the original iperf code started in around 2004 or so and actively maintained 20+ years later.
Microsoft