The policy we were using to configure our wireless for our production network was an " XP" policy. Windows Settings > Security Settings > Wireless Network (IEEE 802.11) Policies Gpupdate each time until I could connect to the wireless display. One by one I removed every policy object and ran a Were applied to the WORKSTATIONS OU as well as a duplicated Default Domain Policy. I created an new OU just for the devices i wanted to connect to the miracast, blocked inheritance then added ALL policy objects that I had two Surfaces with the EXACT issue, as well as several other WIDI enabled machines that are joined to the domain. I think I found the ACTUAL fix, or at least an alternative fix.
Any ideas on why it doesn't work after being domain joined? And yes all drivers are up to date, all Windows updates have been applied, it's been rebooted plenty of times. We checked Group Policy and we can't find anything that would prevent it from working (our GPO runs on ServerĢ008 FWIW). So, I rejoined it to the Domain, and lo and behold, the Add A Wireless Display option disappeared, and it wouldn't even find the device. When it came back up on the WORKGROUP, I had a "Add a Wireless Display" option, and it worked! It beamed to my Miracast Receiver I had to disconnect it from the domain, so I logged in as local admin, joined a test workgroup, then rebooted. Just the options for PC Screen Only, Duplicate, Extend, Second Screen When pulling the charm bar and clicking Devices->Project, it didn't give me an option to connect to a wireless display. We originally couldn't get it to work at all. We purchased a NetGear PTV3000 to utilize theīuilt in Miracast. We are implementing a new office display system and want to be able to mirror the Surface screens to TVs. We've got 6 Surface Pro 2 Tablets within our enterprise that we've been using for the executive team.
0 kommentar(er)
