Good Morning,

We're having some issues with one of our Surface Pro 2 units we purchased out of a lot of 8. We have multiple Aerohive nodes setup in our office. In our conference room, the Surface has issues connecting to our main corporate SSID. Our "Guest" network connects to the AP that's right outside the conference room. However, when trying to connect to the main SSID, it's trying to connect to an AP on the other side of the office (that's closest to the user's office)! We have other Surface users that don't have this issue, and my laptop (lenovo with Windows 8.1) is connected to the main AP. I've deleted the profiles, removed the network and everything, and it still connects to the far AP, resulting in terrible signal, and dropped connections (1-2 bars at best if it connects). We can't find anything on our Aerohive units that would be causing this. Any ideas on the Windows side?

My only thoughts are that it has something to do with the Marvell Chip in the Surface. All our other computers (that don't have issues) have Intel chips in them.

• Edited by WDT Ops 18 hours 4 minutes ago