Tag: User Configuration

This policy setting allows you to show or hide the Command bar. If you enable this policy setting the Command bar is hidden and the user cannot choose to show it. If you disable this policy setting the Command bar is shown and the user cannot choose to hide it. If you do not configure this policy setting the Command bar is shown by default and the user can choose to hide it.

Prevents users from determining which buttons appear on the Microsoft Internet Explorer and File Explorer standard toolbars. The buttons appearing on the toolbar can be customized by the “Customize” option. This is present under the Toolbars submenu of the View menu in Internet Explorer 6 and under the Toolbars submenu of the Tools menu in the Command bar in subsequent versions of Internet Explorer. If you enable this policy the Customize option will be removed from the menu. If you disable this policy or do not configure it users can customize which buttons appear on the Internet Explorer and File Explorer toolbars. This policy can be used in coordination with the “Disable customizing browser toolbars” policy which prevents users from determining which toolbars are displayed in Internet Explorer and File Explorer.

Prevents users from determining which toolbars are displayed in Microsoft Internet Explorer and File Explorer. If you enable this policy the list of toolbars which users can display by clicking the View menu and then pointing to the Toolbars command will appear dimmed. If you disable this policy or do not configure it users can determine which toolbars are displayed in File Explorer and Internet Explorer. This policy can be used in coordination with the “Disable customizing browser toolbar buttons” policy which prevents users from adding or removing toolbars from Internet Explorer.

This policy setting allows you to manage whether the user can access Developer Tools in Internet Explorer. If you enable this policy setting the user cannot access Developer Tools. If you disable or do not configure this policy setting the user can access Developer Tools.

This policy setting allows you to turn off the toolbar upgrade tool. The toolbar upgrade tool determines whether incompatible toolbars or Browser Helper Objects are installed when Internet Explorer starts. If the tool detects an incompatible toolbar the user is prompted to update or disable the toolbar. Specific toolbars or Browser Helper Objects that are enabled or disabled via policy settings do not undergo this check. If you enable this policy setting the toolbar upgrade tool does not check for incompatible toolbars. The user is not prompted and incompatible toolbars run unless previously disabled through policy settings or user choice. If you disable or do not configure this policy setting the toolbar upgrade tool checks for incompatible toolbars. The user can enable or disable incompatible toolbars. Toolbars that are enabled or disabled via policy settings do not undergo these checks.

This policy setting allows Internet Explorer to be started automatically to complete the signup process after the branding is complete for Internet service providers (ISPs) through the Internet Explorer Administration Kit (IEAK). If you enable this policy setting Internet Explorer is started automatically to complete the signup process after the branding is complete for ISPs (IEAK). The user cannot change this behavior. If you disable this policy setting Internet Explorer is not started automatically to complete the signup process after the branding is complete for ISPs (IEAK). The user cannot change this behavior. If you do not configure this policy setting the user can decide whether to start Internet Explorer automatically to complete the signup process after the branding is complete for ISPs (IEAK).

This policy setting allows you to change the default limit of WebSocket connections per server. The default limit is 6; you can select a value from 2 through 128. If you enable this policy setting Internet Explorer uses the WebSocket connection limit that you set with this policy setting. If you disable or do not configure this policy setting Internet Explorer uses the default limit of 6 WebSocket connections per server.

This policy setting allows you to manage whether documents can request data across third-party domains embedded in the page. If you enable this policy setting documents cannot request data across third-party domains embedded in the page. If you disable or do not configure this policy setting documents can request data across third-party domains embedded in the page.

This policy setting allows you to change the default connection limit for HTTP 1. 0 from 6 connections per host to a limit of your choice (from 2 through 128). If you disable or do not configure this policy setting Internet Explorer will use the default connection limit for HTTP 1. 0 (6 connections per host). In versions of Internet Explorer prior to Internet Explorer 8 the default connection limit for HTTP 1. 0 was 4.