WIFI works since Server 2012 and in selected 2008r2 flavours. Just enable it trough the server manager. BT is the only desktop feature still unavailable on servers. Installing the Toshiba stack is the fastest way to get it working (but you can manage to install the MS stack as well)
Wifi worked for me since the beginning. But the latest update made way easier the WMC installation, given for some odd reasons WMC relies on some WLAN libraries.
Hoping that someone may know the answer to this - otherwise, I suppose it is just a bunch of rambling on my part. Assuming that Windows Server 2016 RTM is going to be the same build that Win10 AU is signed-off as, I am wondering if partners/OEMs will get ahold of that build prior to the end of September (Ignite Conference)? Also, wondering if that end of September release date applies to VLSC as well? I was quite bummed out to see that this release is still another 2.5 months away . I am really hoping that we get our hands on it sooner.
LOL, any machine can BSOD, even a server, especially when running a pre-release OS that isn't fully tested/validated. So I dumped all 80GB of the TP4 VHD from the 2008R2 onto a portable drive and brought it home; built a VM on my 2012R2 server with it and started the upgrade. Where it was BSOD during first reboot on the machine at work, it got past that and is currently at the big circle at 10% and counting. I'll check it in the morning and see if it finished, if so dump it back to the portable drive and replace the VHD at work. I think *something* is screwy with the Hyper-V systems at work. Or it's a defect with Hyper-V on 2008R2.