Tag: Computer Configuration
Detect application install failures
This setting exists only for backward compatibility and is not valid for this version of Windows. To configure the Program Compatibility Assistant use the ‘Turn off Program Compatibility Assistant’ setting under Computer Configuration -> Administrative Templates -> Windows Components -> Application Compatibility.
Detect compatibility issues for applications and drivers
This policy setting configures the Program Compatibility Assistant (PCA) to diagnose failures with application and driver compatibility. If you enable this policy setting the PCA is configured to detect failures during application installation failures during application runtime and drivers blocked due to compatibility issues. When failures are detected the PCA will provide options to run the application in a compatibility mode or get help online through a Microsoft website. If you disable this policy setting the PCA does not detect compatibility issues for applications and drivers. If you do not configure this policy setting the PCA is configured to detect failures during application installation failures during application runtime and drivers blocked due to compatibility issues. Note: This policy setting has no effect if the “Turn off Program Compatibility Assistant” policy setting is enabled. The Diagnostic Policy Service (DPS) and Program Compatibility Assistant Service must be running for the PCA to run. These services can be configured by using the Services snap-in to the Microsoft Management Console.
Make Family Safety control panel visible on a Domain
This policy setting allows you to configure the Family Safety feature. If you enable this policy setting the Family Safety control panel is visible on a domain joined computer. If you disable or do not configure this policy setting the Family Safety control panel is not visible on a domain joined computer.
Disable password strength validation for Peer Grouping
By default when a Peer Group is created that allows for password-authentication (or the password for such a Group is changed) Peer Grouping validates that the password meets the password complexity requirements for the local system. Thus it will not allow any passwords to be used for a Peer Group that are weaker than what would be allowed for a login password. This setting controls this validation behavior. If set to 1 then this validation will not be performed and any password will be allowed. If set to 0 the validation will be performed.
Set the Seed Server
This setting sets the seed server for the site local 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. This setting allows for setting the seed server to a specified node in an enterprise. To use this setting click Enable and then enter a semicolon-delimited list of DNS names or IPV6 addresses in the available field. If you enable this setting and you don’t enter any address no seed server will be used. If this setting is not configured the protocol will revert to using a public registry key to determine the seed server to bootstrap from.
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 site 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 be enabled (which it is by default) for this policy to have effect.
Set the Seed Server
This setting sets the seed server for the link local 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. This setting allows for setting the seed server to a specified node in an enterprise. To use this setting click Enable and then enter a semicolon-delimited list of IPV6 addresses in the available field. If you enable this setting and you don’t enter any address no seed server will be used. If this setting is not configured the protocol will revert to using a public registry key to determine the seed server to bootstrap from.
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.