Preparing Domain Group Policy Settings for Windows Miracast over Wi-Fi Direct or Over-Infrastructure

Windows 10/8.1 client systems

• Uncheck Prevent connections to infrastructure networks
• Check Allow everyone to create all user profiles
• Uncheck Don't allow Wi-Fi Direct groups

Winodws 7 client systems

• All settings mentioned above
• Uncheck Don't allow hosted networks

Settings highlighted in green are required for all versions of Windows, settings highlighted in blue are only required for Windows 7.

Make sure the new group policy setting is applied to the client systems by opening an administrator command prompt and entering gpupdate /force .

If the Windows Defender Firewall is enabled through Group Policy and under Windows Firewall Properties for the Public profile, and if the Settings have been Customized such that Apply Local Firewall rules is set to No then Domain PCs will not be able to connect to the ScreenBeam unless a firewall exception is created at the Group Policy level.

Peer-to-peer Miracast always uses the Public Profile.

Over-Infrastructure Miracast will use the Network Profile assigned to the Wi-Fi network, which could be Domain, Private, or Public.

The simplest method is to create a Firewall rule in Group Policy to allow all ports/protocols/Public Profile for %systemroot%\system32\WUDFHost.exe

Turn off multicast name resolution must be set to Disabled or Not Configured.  Miracast over Infrastructure is not compatible with multicast name resolution Enabled.

Note: Miracast over Infrastructure is not supported on the ScreenBeam 750.

>