Set PNRP cloud to resolve only

This policy setting limits a node to resolving but not publishing names in a specific Peer Name Resolution Protocol (PNRP) cloud. This policy setting forces computers to act as clients in peer-to-peer (P2P) scenarios. For example a client computer can detect other computers to initiate chat sessions but other computers cannot detect that client and initiate sessions with it. If you enable this policy setting this computer cannot register PNRP names and cannot help other computers perform PNRP lookups. If you disable or do not configure this policy setting this computer can publish PNRP names and help other computers perform PNRP lookups.

Turn off PNRP cloud creation

This policy setting enables or disables PNRP cloud creation. PNRP is a distributed name resolution protocol allowing Internet hosts to publish peer names with a corresponding Internet Protocol version 6 (IPv6) address. Other hosts can then resolve the name retrieve the corresponding address and establish peer-to-peer (P2P) connections. The PNRP cloud is a group of connected PNRP nodes in which connections exist between peers so that a node in the PNRP cloud can resolve names published by other nodes. PNRP creates a global cloud if the computer has a global IPv6 address but creates a site-local cloud if the computer has a site-local address. If you enable this policy setting PNRP does not create a cloud and applications cannot use this cloud to publish or resolve names regardless of whether the computer has an IPv6 address that matches the cloud scope. If you disable or do not configure this policy setting all PNRP clouds are turned on by default and PNRP creates a cloud if the computer has an IPv6 address compatible with the cloud’s scope.

Turn off Multicast Bootstrap

This setting disables PNRP protocol from advertising the computer or from searching other computers on the local subnet in the global cloud. The Peer Name Resolution Protocol (PNRP) allows for distributed resolution of a name to an IPV6 address and port number. One of the ways in which PNRP bootstraps itself is by using multicast on the same subnet. That is PNRP publishes itself on the local subnet so that other computers can find it when needed. If you enable this setting PNRP will not use multicast for bootstrapping. Specifying this registry key will break scenarios where there is no seed server for bootstrap (such as ad hoc networking scenarios). If you disable this setting PNRP will use multicast for bootstrapping on the same subnet. If this setting is not configured the protocol will revert to using a public registry key to determine whether it will publish the computer or will use multicast to search for other computers on the local subnet. The multicast protocol used for bootstrapping is SSDP (Simple Service Discovery Protocol). The SSDP service must be enabled (which it is by default) for this policy to have effect.

Turn off Microsoft Peer-to-Peer Networking Services

This setting turns off Microsoft Peer-to-Peer Networking Services in its entirety and will cause all dependent applications to stop working. Peer-to-Peer protocols allow for applications in the areas of RTC collaboration content distribution and distributed processing. If you enable this setting peer-to-peer protocols will be turned off. If you disable this setting or do not configure it the peer-to-peer protocols will be turned on.

Turn off Multicast Bootstrap

This setting disables PNRP protocol from advertising the computer or from searching other computers on the local subnet in the link local cloud. The Peer Name Resolution Protocol (PNRP) allows for distributed resolution of a name to an IPV6 address and port number. One of the ways in which PNRP bootstraps itself is by using multicast on the same subnet. That is PNRP publishes itself on the local subnet so that other computers can find it when needed. If you enable this setting PNRP will not use multicast for bootstrapping. Specifying this registry key will break scenarios where there is no seed server for bootstrap (such as ad hoc networking scenarios). If you disable this setting PNRP will use multicast for bootstrapping on the same subnet. If this setting is not configured the protocol will revert to using a public registry key to determine whether it will publish the computer or will use multicast to search for other computers on the local subnet. The multicast protocol used for bootstrapping is SSDP (Simple Service Discovery Protocol). The SSDP service must enabled (which it is by default) for this policy to have effect.

Set the Seed Server

This setting sets the seed server for the global cloud to a specified node in the enterprise. The Peer Name Resolution Protocol (PNRP) allows for distributed resolution of a name to an IPv6 address and port number. The protocol in some cases requires a seed server from which to get bootstrapped. Any node running peer to peer can be used as a seed server. No configuration is needed for the seed server itself. This setting provides the added flexibility of allowing your users to use their peer-to-peer applications at home as well. Here are the four ways in which you can use this setting to control the seed server used in your corporation. 1. In order to use the global well known seed server on the Internet only; enable the setting leave the seed server list empty leave the checkbox unchecked. 2. In order to use a corporate seed server only enable the setting; insert the fully qualified domain name or IPv6 address of the corporate seed server; and check the checkbox. Using the corporate seed server only will prevent your mobile users from being able to use their peer to peer applications at home. 3. In order to use a corporate seed server and the global seed server enable the setting; insert the fully qualified domain name or IPv6 address of the corporate seed server leave the checkbox unchecked. This is the setting which will allow your mobile users to use peer to peer applications at both work and home seamlessly. 4. In order to not use any seed server enable the setting; do not insert a seed server name; and check the check box. If this setting is disabled or not configured the protocol will revert to using a public registry key to determine the seed server to bootstrap from.

Allow the Network Access Protection client to support the 802.1x Enforcement Client component

This policy setting allows the Network Access Protection (NAP) client to support the Windows XP version of the 802. 1x Enforcement Client component. If you enable this policy setting NAP allows the Windows XP version of the 802. 1x Wireless Enforcement Client to participate. If you disable or do not configure this policy setting the Windows XP version of the 802. 1x Wireless Enforcement Client cannot participate in NAP.

Turn off printing over HTTP

This policy setting specifies whether to allow printing over HTTP from this client. Printing over HTTP allows a client to print to printers on the intranet as well as the Internet. Note: This policy setting affects the client side of Internet printing only. It does not prevent this computer from acting as an Internet Printing server and making its shared printers available via HTTP. If you enable this policy setting it prevents this client from printing to Internet printers over HTTP. If you disable or do not configure this policy setting users can choose to print to Internet printers over HTTP. Also see the “Web-based printing” policy setting in Computer Configuration/Administrative Templates/Printers.

Turn off downloading of print drivers over HTTP

This policy setting specifies whether to allow this client to download print driver packages over HTTP. To set up HTTP printing non-inbox drivers need to be downloaded over HTTP. Note: This policy setting does not prevent the client from printing to printers on the Intranet or the Internet over HTTP. It only prohibits downloading drivers that are not already installed locally. If you enable this policy setting print drivers cannot be downloaded over HTTP. If you disable or do not configure this policy setting users can download print drivers over HTTP.

Restrict Internet communication

This policy setting specifies whether Windows can access the Internet to accomplish tasks that require Internet resources. If you enable this setting all of the the policy settings listed in the “Internet Communication settings” section are set such that their respective features cannot access the Internet. If you disable this policy setting all of the the policy settings listed in the “Internet Communication settings” section are set such that their respective features can access the Internet. If you do not configure this policy setting all of the the policy settings in the “Internet Communication settings” section are set to not configured.