Author: admin
Do not allow Flip3D invocation
This policy setting allows you to configure the accessibility of the Flip 3D feature. Flip 3D allows the user to view items on the Windows desktop as they are being flipped through in three dimensions. If you enable this policy setting Flip 3D is inaccessible. If you disable or do not configure this policy setting Flip 3D is accessible if desktop composition is turned on. When Windows Flip 3D is activated with the Windows+Tab keys a visual version of the desktop is presented and items can be flipped through to select. Changing this policy setting requires a logoff for it to be applied.
Do not allow window animations
This policy setting controls the appearance of window animations such as those found when restoring minimizing and maximizing windows. If you enable this policy setting window animations are turned off. If you disable or do not configure this policy setting window animations are turned on. Changing this policy setting requires a logoff for it to be applied.
Do not allow window animations
This policy setting controls the appearance of window animations such as those found when restoring minimizing and maximizing windows. If you enable this policy setting window animations are turned off. If you disable or do not configure this policy setting window animations are turned on. Changing this policy setting requires a logoff for it to be applied.
IDN mapping
Specifies whether the DNS client should convert internationalized domain names (IDNs) to the Nameprep form a canonical Unicode representation of the string. If this policy setting is enabled IDNs are converted to the Nameprep form. If this policy setting is disabled or if this policy setting is not configured IDNs are not converted to the Nameprep form.
Turn off IDN encoding
Specifies whether the DNS client should convert internationalized domain names (IDNs) to Punycode when the computer is on non-domain networks with no WINS servers configured. If this policy setting is enabled IDNs are not converted to Punycode. If this policy setting is disabled or if this policy setting is not configured IDNs are converted to Punycode when the computer is on non-domain networks with no WINS servers configured.
Prefer link local responses over DNS when received over a network with higher precedence
Specifies that responses from link local name resolution protocols received over a network interface that is higher in the binding order are preferred over DNS responses from network interfaces lower in the binding order. Examples of link local name resolution protocols include link local multicast name resolution (LLMNR) and NetBIOS over TCP/IP (NetBT). If you enable this policy setting responses from link local protocols will be preferred over DNS responses if the local responses are from a network with a higher binding order. If you disable this policy setting or if you do not configure this policy setting then DNS responses from networks lower in the binding order will be preferred over responses from link local protocols received from networks higher in the binding order. Note: This policy setting is applicable only if the turn off smart multi-homed name resolution policy setting is disabled or not configured.
Allow NetBT queries for fully qualified domain names
Specifies that NetBIOS over TCP/IP (NetBT) queries are issued for fully qualified domain names. If you enable this policy setting NetBT queries will be issued for multi-label and fully qualified domain names such as “www. example. com” in addition to single-label names. If you disable this policy setting or if you do not configure this policy setting NetBT queries will only be issued for single-label names such as “example” and not for multi-label and fully qualified domain names.
Turn off smart protocol reordering
Specifies that the DNS client should prefer responses from link local name resolution protocols on non-domain networks over DNS responses when issuing queries for flat names. Examples of link local name resolution protocols include link local multicast name resolution (LLMNR) and NetBIOS over TCP/IP (NetBT). If you enable this policy setting the DNS client will prefer DNS responses followed by LLMNR followed by NetBT for all networks. If you disable this policy setting or if you do not configure this policy setting the DNS client will prefer link local responses for flat name queries on non-domain networks. Note: This policy setting is applicable only if the turn off smart multi-homed name resolution policy setting is disabled or not configured.
Turn off smart multi-homed name resolution
Specifies that a multi-homed DNS client should optimize name resolution across networks. The setting improves performance by issuing parallel DNS link local multicast name resolution (LLMNR) and NetBIOS over TCP/IP (NetBT) queries across all networks. In the event that multiple positive responses are received the network binding order is used to determine which response to accept. If you enable this policy setting the DNS client will not perform any optimizations. DNS queries will be issued across all networks first. LLMNR queries will be issued if the DNS queries fail followed by NetBT queries if LLMNR queries fail. If you disable this policy setting or if you do not configure this policy setting name resolution will be optimized when issuing DNS LLMNR and NetBT queries.
Allow DNS suffix appending to unqualified multi-label name queries
Specifies that computers may attach suffixes to an unqualified multi-label name before sending subsequent DNS queries if the original name query fails. A name containing dots but not dot-terminated is called an unqualified multi-label name for example “server. corp” is an unqualified multi-label name. The name “server. corp. contoso. com. ” is an example of a fully qualified name because it contains a terminating dot. For example if attaching suffixes is allowed an unqualified multi-label name query for “server. corp” will be queried by the DNS client first. If the query succeeds the response is returned to the client. If the query fails the unqualified multi-label name is appended with DNS suffixes. These suffixes can be derived from a combination of the local DNS client’s primary domain suffix a connection-specific domain suffix and a DNS suffix search list. If attaching suffixes is allowed and a DNS client with a primary domain suffix of “contoso. com” performs a query for “server. corp” the DNS client will send a query for “server. corp” first and then a query for “server. corp. contoso. com. ” second if the first query fails. If you enable this policy setting suffixes are allowed to be appended to an unqualified multi-label name if the original name query fails. If you disable this policy setting no suffixes are appended to unqualified multi-label name queries if the original name query fails. If you do not configure this policy setting computers will use their local DNS client settings to determine the query behavior for unqualified multi-label names.