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.
shin0933
Jan 16, 2025Brass Contributor
Hi Dom, we had to create a firewall rule that allowed the executable that Miracast uses to make this work for us. We have miracast working on Win11 AADJ devices managed by Intune.
- Dom_CoteJan 16, 2025Brass Contributor
I got that advice from support as well. Didn't work for us. Which suggests that it may not be firewall-related.
Security Center / Secure Score's network hardening recommendations go far beyond "just" firewall policies, which is a good thing I imagine.
Whatever is doing this disrupts a few external apps from accessing managed devices directly. For example, we can normally use the NFC on our smartphones to read our government ID cards to sign in to government sites. But the smartphone app also fails to connect to managed PCs. So we need to use a USB NFC reader instead.
Oddly, other apps such as a USB sharing software Virtualhere works just fine.
Ah well - thanks anyways.