The Surface Hub or device (Windows PC or phone) needs to be running Windows 10, version 1703.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 device that has been updated to Windows 10, version 1703, then you automatically have this new feature. If the name is not resolvable via either DNS method, Windows 10 will fall 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 10 will attempt to resolve the device's hostname via standard DNS, as well as via multicast DNS (mDNS). When the list of Miracast receivers is populated, Windows 10 will identify 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 as they did previously. It leverages an existing connection which both reduces the time to connect and provides a very stable stream.It works well with older wireless hardware that is not optimized for Miracast over Wi-Fi Direct.No changes to current wireless drivers or PC hardware are required.They use the same UX as for standard Miracast connections. Users do not 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 a number of benefits: This functionality is based on the Miracast over Infrastructure Connection Establishment Protocol (MS-MICE).
Beginning with Windows 10 version 1703, Microsoft extended the ability to send a Miracast stream over a local network rather than over a direct wireless link.
0 kommentar(er)
