Event banner
Windows Office Hours: January 16, 2025
Event Ended
Thursday, Jan 16, 2025, 08:00 AM PSTEvent details
Get answers to your questions about adopting Windows 11 and managing Windows devices across your organization. Find out how to proactively implement and monitor Zero Trust practices. Get tips on keep...
Pearl-Angeles
Updated Jan 08, 2025
Dom_Cote
Jan 16, 2025Brass Contributor
Configuring Windows device security according to Secure Score's best practice recommendations breaks casting / miracast. Supposedly, something in the network gets blocked (and there's a lot of it!) that stops miracast from connecting to managed devices.
I been totally unsuccessful in figuring out which network security setting causes this - and neither has M365 support been able to pin point this.
Can you provide some DETAILED documentation on which network prerequisites miracast needs to work?
Spoiler: Intel's documentation on it hasn't helped me either.
Sean_McLaren
Microsoft
Jan 16, 2025Without knowing exactly which policies got set and what was blocked, my suggestion would be to look at your policies that would block any of the protocols used and ensure the firewall settings are not blocking or dropping communication between devices. The Miracast spec here details the protocols used: https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-mice/9598ca72-d937-466c-95f6-70401bb10bdb . The driver requirements are also here, if you've had any driver updates, may be related to that as well. https://learn.microsoft.com/en-us/windows-hardware/design/device-experiences/wireless-projection-pc-manufacturers Hope that helps.
- Dom_CoteJan 16, 2025Brass Contributor
Yeah, that's exactly what's happening. Secure Score gives excellent and detailed recommendations on hardening a few network settings. But one or more of them also break miracast. We tested: It's not a driver issue, as the same deivces work fine without the network / firewall policies applied.
I'll take a look at the specs you shared, didn't have those yet. Thanks!