


A Windows PC or phone can act as a Miracast over Infrastructure source. A Surface Hub or Windows PC can act as a Miracast over Infrastructure receiver.To take advantage of it in your environment, you need to ensure the following is true within your deployment:

If you have a Surface Hub or other Windows 10/11 device, then you automatically have this new feature. If the name isn't resolvable via either DNS method, Windows falls back to establishing the Miracast session using the standard Wi-Fi direct connection.įor more information on the connection negotiation sequence, see Miracast over Infrastructure Connection Establishment Protocol (MS-MICE) Enabling Miracast over Infrastructure When the user selects a Miracast receiver, Windows attempts to resolve the device's hostname via standard DNS, and via multicast DNS (mDNS). When the list of Miracast receivers is populated, Windows identifies that the receiver is capable of supporting a connection over the infrastructure. Users attempt to connect to a Miracast receiver through their Wi-Fi adapter.

They use the same UX as for standard Miracast connections. Users don't have to change how they connect to a Miracast receiver.Windows will only choose this route if the connection is over Ethernet or a secure Wi-Fi network.Windows automatically detects when sending the video stream over this path is applicable.Miracast over Infrastructure offers many benefits:
