--- title: Policy CSP - WirelessDisplay description: Use the Policy CSP - WirelessDisplay setting to turn off the Wireless Display multicast DNS service advertisement from a Wireless Display receiver. ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows author: dansimp ms.localizationpriority: medium ms.date: 09/27/2019 ms.reviewer: manager: dansimp --- # Policy CSP - WirelessDisplay
## WirelessDisplay policies
WirelessDisplay/AllowMdnsAdvertisement
WirelessDisplay/AllowMdnsDiscovery
WirelessDisplay/AllowMovementDetectionOnInfrastructure
WirelessDisplay/AllowProjectionFromPC
WirelessDisplay/AllowProjectionFromPCOverInfrastructure
WirelessDisplay/AllowProjectionToPC
WirelessDisplay/AllowProjectionToPCOverInfrastructure
WirelessDisplay/AllowUserInputFromWirelessDisplayReceiver
WirelessDisplay/RequirePinForPairing

**WirelessDisplay/AllowMdnsAdvertisement** The table below shows the applicability of Windows: |Edition|Windows 10|Windows 11| |--- |--- |--- | |Home|No|No| |Pro|Yes|Yes| |Windows SE|No|Yes| |Business|Yes|Yes| |Enterprise|Yes|Yes| |Education|Yes|Yes|
[Scope](./policy-configuration-service-provider.md#policy-scope): > [!div class = "checklist"] > * Device
This policy setting allows you to turn off the Wireless Display multicast DNS service advertisement from a Wireless Display receiver. If the network administrator is concerned about network congestion, they may set this policy to 0, disabling mDNS advertisement. The following list shows the supported values: - 0 - Don't allow - 1 - Allow
**WirelessDisplay/AllowMdnsDiscovery** The table below shows the applicability of Windows: |Edition|Windows 10|Windows 11| |--- |--- |--- | |Home|No|No| |Pro|Yes|Yes| |Windows SE|No|Yes| |Business|Yes|Yes| |Enterprise|Yes|Yes| |Education|Yes|Yes|
[Scope](./policy-configuration-service-provider.md#policy-scope): > [!div class = "checklist"] > * Device
This policy setting allows you to turn off discovering the display service advertised over multicast DNS by a Wireless Display receiver. If the network administrator is concerned about network congestion, they may set this policy to 0, disabling mDNS discovery. The following list shows the supported values: - 0 - Don't allow - 1 - Allow
**WirelessDisplay/AllowMovementDetectionOnInfrastructure** The table below shows the applicability of Windows: |Edition|Windows 10|Windows 11| |--- |--- |--- | |Home|No|No| |Pro|Yes|Yes| |Windows SE|No|Yes| |Business|Yes|Yes| |Enterprise|Yes|Yes| |Education|Yes|Yes|
[Scope](./policy-configuration-service-provider.md#policy-scope): > [!div class = "checklist"] > * Device
This policy setting allows you to disable the infrastructure movement detection feature. If you set it to 0, your PC may stay connected and continue to project if you walk away from a Wireless Display receiver to which you're projecting over infrastructure. If you set it to 1, your PC will detect that you've moved and will automatically disconnect your infrastructure Wireless Display session. The default value is 1. The following list shows the supported values: - 0 - Don't allow - 1 (Default) - Allow
**WirelessDisplay/AllowProjectionFromPC** The table below shows the applicability of Windows: |Edition|Windows 10|Windows 11| |--- |--- |--- | |Home|No|No| |Pro|Yes|Yes| |Windows SE|No|Yes| |Business|Yes|Yes| |Enterprise|Yes|Yes| |Education|Yes|Yes|
[Scope](./policy-configuration-service-provider.md#policy-scope): > [!div class = "checklist"] > * Device
This policy allows you to turn off projection from a PC. The following list shows the supported values: - 0 - your PC can't discover or project to other devices. - 1 - your PC can discover and project to other devices
**WirelessDisplay/AllowProjectionFromPCOverInfrastructure** The table below shows the applicability of Windows: |Edition|Windows 10|Windows 11| |--- |--- |--- | |Home|No|No| |Pro|Yes|Yes| |Windows SE|No|Yes| |Business|Yes|Yes| |Enterprise|Yes|Yes| |Education|Yes|Yes|
[Scope](./policy-configuration-service-provider.md#policy-scope): > [!div class = "checklist"] > * Device
This policy allows you to turn off projection from a PC over infrastructure. The following list shows the supported values: - 0 - your PC can't discover or project to other infrastructure devices, although it's possible to discover and project over WiFi Direct. - 1 - your PC can discover and project to other devices over infrastructure.
**WirelessDisplay/AllowProjectionToPC** The table below shows the applicability of Windows: |Edition|Windows 10|Windows 11| |--- |--- |--- | |Home|No|No| |Pro|Yes|Yes| |Windows SE|No|Yes| |Business|Yes|Yes| |Enterprise|Yes|Yes| |Education|Yes|Yes|
[Scope](./policy-configuration-service-provider.md#policy-scope): > [!div class = "checklist"] > * Device
Allow or disallow turning off the projection to a PC. If you set it to 0 (zero), your PC isn't discoverable and you can't project to it. If you set it to 1, your PC is discoverable and you can project to it above the lock screen. The user has an option to turn it always on or always off except for manual launch. In PCs that support Miracast, after the policy is applied you can verify the setting from the user interface in **Settings** > **System** > **Projecting to this PC**. Supported value type is integer. ADMX Info: - GP Friendly name: *Don't allow this PC to be projected to* - GP name: *AllowProjectionToPC* - GP path: *Windows Components/Connect* - GP ADMX file name: *WirelessDisplay.admx* The following list shows the supported values: - 0 - projection to PC isn't allowed. Always off and the user can't enable it. - 1 (default) - projection to PC is allowed. Enabled only above the lock screen.
**WirelessDisplay/AllowProjectionToPCOverInfrastructure** The table below shows the applicability of Windows: |Edition|Windows 10|Windows 11| |--- |--- |--- | |Home|No|No| |Pro|Yes|Yes| |Windows SE|No|Yes| |Business|Yes|Yes| |Enterprise|Yes|Yes| |Education|Yes|Yes|
[Scope](./policy-configuration-service-provider.md#policy-scope): > [!div class = "checklist"] > * Device
This policy setting allows you to turn off projection to a PC over infrastructure. The following list shows the supported values: - 0 - your PC isn't discoverable and other devices can't project to it over infrastructure, although it's possible to project to it over WiFi Direct. - 1 - your PC is discoverable and other devices can project to it over infrastructure.
**WirelessDisplay/AllowUserInputFromWirelessDisplayReceiver** The table below shows the applicability of Windows: |Edition|Windows 10|Windows 11| |--- |--- |--- | |Home|No|No| |Pro|Yes|Yes| |Windows SE|No|Yes| |Business|Yes|Yes| |Enterprise|Yes|Yes| |Education|Yes|Yes|
[Scope](./policy-configuration-service-provider.md#policy-scope): > [!div class = "checklist"] > * Device
Setting this policy controls whether or not the wireless display can send input—keyboard, mouse, pen, and touch input if the display supports it—back to the source device. The following list shows the supported values: - 0 - Wireless display input disabled. - 1 (default) - Wireless display input enabled.
**WirelessDisplay/RequirePinForPairing** The table below shows the applicability of Windows: |Edition|Windows 10|Windows 11| |--- |--- |--- | |Home|No|No| |Pro|Yes|Yes| |Windows SE|No|Yes| |Business|Yes|Yes| |Enterprise|Yes|Yes| |Education|Yes|Yes|
[Scope](./policy-configuration-service-provider.md#policy-scope): > [!div class = "checklist"] > * Device
Allow or disallow requirement for a PIN for pairing. If you turn on this policy, the pairing ceremony for new devices will always require a PIN. If you turn off this policy or don't configure it, a PIN isn't required for pairing. In PCs that support Miracast, after the policy is applied you can verify the setting from the user interface in **Settings** > **System** > **Projecting to this PC**. Supported value type is integer. ADMX Info: - GP Friendly name: *Require pin for pairing* - GP name: *RequirePinForPairing* - GP path: *Windows Components/Connect* - GP ADMX file name: *WirelessDisplay.admx* The following list shows the supported values: - 0 (default) - PIN isn't required. - 1 - PIN is required.
CSP Article: ## Related topics [Policy configuration service provider](policy-configuration-service-provider.md)