#Microsoft miracast windows 10 windows 10#
Then we took an on-premise domain joined Windows 10 Enterprise device that receives GPO settings and firewall policies and tested on that. We found that on that device the temporary virtual network adapter for the WiFi direct connection is considered to be Private by default, so projection works.
#Microsoft miracast windows 10 pro#
We compared this behavior to what we see on a brand new out of the box Lenovo ThinkPad T470 device that runs the OEM Windows 10 Pro version and has received no GPO settings, Security Baseline or Device Configuration Profiles. This whole situation is unwanted and, quite frankly, unlogical behaviour from Windows 10 as the connection between the Windows 10 device and the Surface Hub is a WiFi direct connection and as such should automatically be considered a Private network. As soon as the error that "Something went wrong with the projection" is shown, the temporary virtual network adapter is deleted/hidden and we can't change the network category anymore. The culprit here is that the change in network category can only be executed while the temporary virtual network adapter is visible. Then we manually changed the network category for the temporary virtual network adapter on the Windows 10 Enterprise Autopilot enrolled Intune MDM managed device using the PowerShell cmdline: "Set-NetConnectionProfile -Name DIRECT-%SurfaceHubName%xxxx -NetworkCategory Private"Īfter changing the network category we were able to project to the Surface Hub. However we receive an error that "Something went wrong with the projection".ĭuring our research we found that the Surface Hub creates a temporary virtual network adapter with a name like "DIRECT-%SurfaceHubName%xxxx".This virtual network adapter is wrongly considered to be a Public network, resulting in the MiraCast session to end prematurely. When we try to connect to a Surface Hub device from a Lenovo ThinkPad T470 test device using the MiraCast WiFi Direct connection we are able to scan and find the Surface Hub, pair with the device using the provided PIN and start the Projection Session. These devices run Windows 10 build 1809 (or higher) and are hardened with the MS Security Baseline v1903. We are currently in the midst of a migration project to migrate on-premise domain joined Windows 7 devices to Azure AD joined Windows 10 devices via Intune MDM Autopilot.
0 kommentar(er)
