How can I enable "Miracast over Infrastructure" for non-Surface Hub Windows 10 PCs?

I was very excited to discover an article explaining how I can now use Miracast over a Windows LAN. The technology is called Miracast over Infrastructure. For those unaware, Miracast is the protocol used by the Windows 10 "Project to a second screen" and "Projecting to this PC" functionality.

Only laptops (over wireless, with specific hardware), have had access to this feature up until now which is obviously quite frustrating when this functionality would be very useful over the LAN with regular workstations.

The problem is the article only seems to discuss this functionality in the context of the Surface Hub.

My questions:

• Is the Surface Hub running some custom software for this?
• Can that software be installed on a regular Windows 10, version 1703 PC ?
• What services need to be running to support Miracast over Infrastructure?

I came here looking for the same answer. Turns out that the answer is that you still need an active Wireless-adapter to establish the Miracast session.

Since this question was posted, the Microsoft documentation linked in the question has been updated with, among others, the following updates:

On Windows 10 PCs, the Projecting to this PC feature must be enabled in System Settings, and the device must have a Wi-Fi interface enabled in order to respond to discovery requests that only occur through the Wi-Fi adapter.

Along with an FAQ-section that reads:

Why do I still need Wi-Fi to use Miracast over infrastructure?

Discovery requests to identify Miracast receivers can only occur through the Wi-Fi adapter. Once the receivers have been identified, Windows 10 can then attempt the connection to the network.

I'm assuming Microsoft updated the article, because they now specifically mention Windows PC and Windows Phone alongside the Surface Hub in that article. Just make sure you're running version 1703 (or later) on both ends. As far as your specific scenario of miracasting between 2 "regular" Windows 10 1703 or above workstations is concerned, this portion of the article should help:

A Surface Hub or Windows PC can act as a Miracast over Infrastructure receiver. A Windows PC or phone can act as a Miracast over Infrastructure source. As a Miracast receiver, the Surface Hub or device must be connected to your enterprise network via either Ethernet or a secure Wi-Fi connection (e.g. using either WPA2-PSK or WPA2-Enterprise security). If the Surface Hub or device is connected to an open Wi-Fi connection, Miracast over Infrastructure will disable itself. As a Miracast source, the Windows PC or phone must be connected to the same enterprise network via Ethernet or a secure Wi-Fi connection.

Based on the Microsoft article and some Googling around to find real-world use cases, I can answer your questions as follows:

• No
• Not required
• I'm not sure what specific services 1703 updated/added, but the protocol is called "[MS-MICE]: Miracast over Infrastructure Connection Establishment Protocol", and builds upon the following existing technologies:

• Datagram Transport Layer Security (DTLS) [RFC6347]
• Domain Name System (DNS) [IANA-DNS] [RFC1034] [RFC2181]
• Multicast DNS (mDNS)[RFC6762]
• Real-Time Streaming Protocol (RTSP) [RFC2326]
• Transmission Control Protocol (TCP) [RFC793]
• Wi-Fi Display Protocol [WF-DTS1.1]
• Wi-Fi Peer-to-Peer (P2P) Protocol [WF-P2P1.2]
• Wi-Fi Simple Configuration (WSC) Protocol [WF-WSC2.0.2]

Hope this helps!