Tag: Computer Configuration
Do not allow color changes
This policy setting controls the ability to change the color of window frames. If you enable this policy setting you prevent users from changing the default window frame color. If you disable or do not configure this policy setting you allow users to change the default window frame color. Note: This policy setting can be used in conjunction with the “Specify a default color for window frames” policy setting to enforce a specific color for window frames that cannot be changed by users.
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.
Use solid color for Start background
This policy setting controls the Start background visuals. If you enable this policy setting the Start background will use a solid color. If you disable or do not configure this policy setting the Start background will use the default visuals. Note: If this policy setting is enabled users can continue to select a color in Start Personalization. However setting the accent will have no effect.
Turn off multicast name resolution
Specifies that link local multicast name resolution (LLMNR) is disabled on client computers. LLMNR is a secondary name resolution protocol. With LLMNR queries are sent using multicast over a local network link on a single subnet from a client computer to another client computer on the same subnet that also has LLMNR enabled. LLMNR does not require a DNS server or DNS client configuration and provides name resolution in scenarios in which conventional DNS name resolution is not possible. If you enable this policy setting LLMNR will be disabled on all available network adapters on the client computer. If you disable this policy setting or you do not configure this policy setting LLMNR will be enabled on all available network adapters.
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.
Primary DNS suffix devolution level
Specifies if the devolution level that DNS clients will use if they perform primary DNS suffix devolution during the name resolution process. With devolution a DNS client creates queries by appending a single-label unqualified domain name with the parent suffix of the primary DNS suffix name and the parent of that suffix and so on stopping if the name is successfully resolved or at a level determined by devolution settings. Devolution can be used when a user or application submits a query for a single-label domain name. The DNS client appends DNS suffixes to the single-label unqualified domain name based on the state of the Append primary and connection specific DNS suffixes radio button and Append parent suffixes of the primary DNS suffix check box on the DNS tab in Advanced TCP/IP Settings for the Internet Protocol (TCP/IP) Properties dialog box. Devolution is not enabled if a global suffix search list is configured using Group Policy. If a global suffix search list is not configured and the Append primary and connection specific DNS suffixes radio button is selected the DNS client appends the following names to a single-label name when it sends DNS queries:The primary DNS suffix as specified on the Computer Name tab of the System control panel. Each connection-specific DNS suffix assigned either through DHCP or specified in the DNS suffix for this connection box on the DNS tab in the Advanced TCP/IP Settings dialog box for each connection. For example when a user submits a query for a single-label name such as “example” the DNS client attaches a suffix such as “microsoft. com” resulting in the query “example. microsoft. com” before sending the query to a DNS server. If a DNS suffix search list is not specified the DNS client attaches the primary DNS suffix to a single-label name. If this query fails the connection-specific DNS suffix is attached for a new query. If none of these queries are resolved the client devolves the primary DNS suffix of the computer (drops the leftmost label of the primary DNS suffix) attaches this devolved primary DNS suffix to the single-label name and submits this new query to a DNS server. For example if the primary DNS suffix ooo. aaa. microsoft. com is attached to the non-dot-terminated single-label name “example” and the DNS query for example. ooo. aaa. microsoft. com fails the DNS client devolves the primary DNS suffix (drops the leftmost label) till the specified devolution level and submits a query for example. aaa. microsoft. com. If this query fails the primary DNS suffix is devolved further if it is under specified devolution level and the query example. microsoft. com is submitted. If this query fails devolution continues if it is under specified devolution level and the query example. microsoft. com is submitted corresponding to a devolution level of two. The primary DNS suffix cannot be devolved beyond a devolution level of two. The devolution level can be configured using this policy setting. The default devolution level is two. If you enable this policy setting and DNS devolution is also enabled DNS clients use the DNS devolution level that you specify. If this policy setting is disabled or if this policy setting is not configured DNS clients use the default devolution level of two provided that DNS devolution is enabled.
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.