Tag: User Configuration

This policy setting allows you to manage ActiveX controls not marked as safe. If you enable this policy setting ActiveX controls are run loaded with parameters and scripted without setting object safety for untrusted data or scripts. This setting is not recommended except for secure and administered zones. This setting causes both unsafe and safe controls to be initialized and scripted ignoring the Script ActiveX controls marked safe for scripting option. If you enable this policy setting and select Prompt in the drop-down box users are queried whether to allow the control to be loaded with parameters or scripted. If you disable this policy setting ActiveX controls that cannot be made safe are not loaded with parameters or scripted. If you do not configure this policy setting ActiveX controls that cannot be made safe are not loaded with parameters or scripted.

This policy setting allows you to manage whether applets are exposed to scripts within the zone. If you enable this policy setting scripts can access applets automatically without user intervention. If you select Prompt in the drop-down box users are queried to choose whether to allow scripts to access applets. If you disable this policy setting scripts are prevented from accessing applets. If you do not configure this policy setting scripts can access applets automatically without user intervention.

This policy setting allows you to manage whether . NET Framework components that are signed with Authenticode can be executed from Internet Explorer. These components include managed controls referenced from an object tag and managed executables referenced from a link. If you enable this policy setting Internet Explorer will execute signed managed components. If you select Prompt in the drop-down box Internet Explorer will prompt the user to determine whether to execute signed managed components. If you disable this policy setting Internet Explorer will not execute signed managed components. If you do not configure this policy setting Internet Explorer will not execute signed managed components.

This policy setting allows you to set options for dragging content from one domain to a different domain when the source and destination are in different windows. If you enable this policy setting and click Enable users can drag content from one domain to a different domain when the source and destination are in different windows. Users cannot change this setting. If you enable this policy setting and click Disable users cannot drag content from one domain to a different domain when both the source and destination are in different windows. Users cannot change this setting. In Internet Explorer 10 if you disable this policy setting or do not configure it users cannot drag content from one domain to a different domain when the source and destination are in different windows. Users can change this setting in the Internet Options dialog. In Internet Explorer 9 and earlier versions if you disable this policy or do not configure it users can drag content from one domain to a different domain when the source and destination are in different windows. Users cannot change this setting.

This policy setting allows you to manage the opening of windows and frames and access of applications across different domains. If you enable this policy setting users can open windows and frames from othe domains and access applications from other domains. If you select Prompt in the drop-down box users are queried whether to allow windows and frames to access applications from other domains. If you disable this policy setting users cannot open windows and frames to access applications from different domains. If you do not configure this policy setting users can open windows and frames from othe domains and access applications from other domains.

This policy setting allows you to manage whether users are prompted to select a certificate when no certificate or only one certificate exists. If you enable this policy setting Internet Explorer does not prompt users with a “Client Authentication” message when they connect to a Web site that has no certificate or only one certificate. If you disable this policy setting Internet Explorer prompts users with a “Client Authentication” message when they connect to a Web site that has no certificate or only one certificate. If you do not configure this policy setting Internet Explorer prompts users with a Client Authentication message when they connect to a Web site that has no certificate or only one certificate.

This policy setting manages whether users will be automatically prompted for ActiveX control installations. If you enable this policy setting users will receive a prompt when a site instantiates an ActiveX control they do not have installed. If you disable this policy setting ActiveX control installations will be blocked using the Notification bar. Users can click on the Notification bar to allow the ActiveX control prompt. If you do not configure this policy setting ActiveX control installations will be blocked using the Notification bar. Users can click on the Notification bar to allow the ActiveX control prompt.

This policy setting determines whether users will be prompted for non user-initiated file downloads. Regardless of this setting users will receive file download dialogs for user-initiated downloads. If you enable this setting users will receive a file download dialog for automatic download attempts. If you disable or do not configure this setting file downloads that are not user-initiated will be blocked and users will see the Notification bar instead of the file download dialog. Users can then click the Notification bar to allow the file download prompt.

This policy setting allows you to manage permissions for Java applets. If you enable this policy setting you can choose options from the drop-down box. Custom to control permissions settings individually. Low Safety enables applets to perform all operations. Medium Safety enables applets to run in their sandbox (an area in memory outside of which the program cannot make calls) plus capabilities like scratch space (a safe and secure storage area on the client computer) and user-controlled file I/O. High Safety enables applets to run in their sandbox. Disable Java to prevent any applets from running. If you disable this policy setting Java applets cannot run. If you do not configure this policy setting Java applets are disabled.