Tag: Computer Configuration
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 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.
Enable file synchronization on costed networks
This policy setting determines whether offline files are synchronized in the background when it could result in extra charges on cell phone or broadband plans. If you enable this setting synchronization can occur in the background when the user’s network is roaming near or over the plan’s data limit. This may result in extra charges on cell phone or broadband plans. If this setting is disabled or not configured synchronization will not run in the background on network folders when the user’s network is roaming near or over the plan’s data limit. The network folder must also be in “slow-link” mode as specified by the “Configure slow-link mode” policy to avoid network usage.
Remove “Work offline” command
This policy setting removes the “Work offline” command from Explorer preventing users from manually changing whether Offline Files is in online mode or offline mode. If you enable this policy setting the “Work offline” command is not displayed in File Explorer. If you disable or do not configure this policy setting the “Work offline” command is displayed in File Explorer.
Enable file screens
This policy setting enables administrators to block certain file types from being created in the folders that have been made available offline. If you enable this policy setting a user will be unable to create files with the specified file extensions in any of the folders that have been made available offline. If you disable or do not configure this policy setting a user can create a file of any type in the folders that have been made available offline.
Enable Transparent Caching
This policy setting controls whether files read from file shares over a slow network are transparently cached in the Offline Files cache for future reads. When a user tries to access a file that has been transparently cached Windows reads from the cached copy after verifying its integrity. This improves end-user response times and decreases bandwidth consumption over WAN links. The cached files are temporary and are not available to the user when offline. The cached files are not kept in sync with the version on the server and the most current version from the server is always available for subsequent reads. This policy setting is triggered by the configured round trip network latency value. We recommend using this policy setting when the network connection to the server is slow. For example you can configure a value of 60 ms as the round trip latency of the network above which files should be transparently cached in the Offline Files cache. If the round trip latency of the network is less than 60ms reads to remote files will not be cached. If you enable this policy setting transparent caching is enabled and configurable. If you disable or do not configure this policy setting remote files will be not be transparently cached on client computers.
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.