Hi Philliplyle,
If you looked at my original post (first one) - you would see the below key information when I was describing the issue.
"These issues first occurred after we have replaced our wireless infrastructure with IAP-315's and IAP-325's approximately two months ago.
We did not experience this issue using the HP Procurve equipment.
We have over 1100 devices connected at any time during the day concurrently across 80+ IAPs, where 98% of these all use the Intel 7260 AC wireless network card. None of these Intel-based clients display the issue. My thoughts would be that this confirms that there is nothing wrong with our wireless infrastructure."
In summary, the issue was identified by a level 3 TAC engineer and a firmware developer who works on the IAP code, we then implemented a workaround by disabling the RX-AMPDU feature (needs to be done from the IAP "controller" for the SSID) and it was resolved in a later update which was 6.5.4.2.
We ran this firmware for two weeks with the RX-ampdu feature turned back on, then I reported back that this is confirmed as a solution which is why it was marked as such for the IAP issue that affects IAP-315/IAP-325 models.
We were running about 60 SurfaceBook (1st Gen) and 1150 Dell, 100 HP laptops in that same testing period.
My suggestion would be to upgrade to the latest version of Windows, ensure all the Surface firmware + driver packs are installed, set up a device in the office, disable any power setting policies (MS recommend that you do not use GPO to manage power settings/plans on Surface devices), plug into power and then fire up a ping test to see if it drops out.
Once it drops out - do a loopback ping test to verify that the TCP/IP stack is still ok, then use another computer to ping the local IP of the IAP its attached too.
Then open a TAC case. :)
Cheers,
Aaron