Category: At least Internet Explorer 7.0
Allow scriptlets
This policy setting allows you to manage whether the user can run scriptlets. If you enable this policy setting the user can run scriptlets. If you disable this policy setting the user cannot run scriptlets. If you do not configure this policy setting the user can enable or disable scriptlets.
Allow scriptlets
This policy setting allows you to manage whether the user can run scriptlets. If you enable this policy setting the user can run scriptlets. If you disable this policy setting the user cannot run scriptlets. If you do not configure this policy setting the user can enable or disable scriptlets.
Turn off first-run prompt
This policy setting controls the first-run response that the user sees on a zone-by-zone basis. When the user encounters a new control that has not previously run in Internet Explorer he or she may be prompted to approve the control. This policy setting determines whether the user is prompted. If you enable this policy setting the first-run prompt is turned off in the corresponding zone. If you disable this policy setting the first-run prompt is turned on in the corresponding zone. If you do not configure this policy setting the first-run prompt is turned off by default.
Allow loading of XAML Browser Applications
This policy setting allows you to manage the loading of XAML Browser Applications (XBAPs). These are browser-hosted ClickOnce-deployed applications built via WinFX. These applications run in a security sandbox and take advantage of the Windows Presentation Foundation platform for the web. If you enable this policy setting and set the drop-down box to Enable XBAPs are automatically loaded inside Internet Explorer. The user cannot change this behavior. If you set the drop-down box to Prompt the user is prompted for loading XBAPs. If you disable this policy setting XBAPs are not loaded inside Internet Explorer. The user cannot change this behavior. If you do not configure this policy setting the user can decide whether to load XBAPs inside Internet Explorer.
Allow scripting of Internet Explorer WebBrowser controls
This policy setting determines whether a page can control embedded WebBrowser controls via script. If you enable this policy setting script access to the WebBrowser control is allowed. If you disable this policy setting script access to the WebBrowser control is not allowed. If you do not configure this policy setting the user can enable or disable script access to the WebBrowser control. By default script access to the WebBrowser control is allowed only in the Local Machine and Intranet zones.
Allow scripting of Internet Explorer WebBrowser controls
This policy setting determines whether a page can control embedded WebBrowser controls via script. If you enable this policy setting script access to the WebBrowser control is allowed. If you disable this policy setting script access to the WebBrowser control is not allowed. If you do not configure this policy setting the user can enable or disable script access to the WebBrowser control. By default script access to the WebBrowser control is allowed only in the Local Machine and Intranet zones.
Turn off . NET Framework Setup
This policy setting prevents the user’s computer from starting Microsoft . NET Framework Setup when the user is browsing to . NET Framework content in Internet Explorer. The . NET Framework is the next-generation platform for Windows. It uses the common language runtime and incorporates support from multiple developer tools. It includes the new managed code APIs for Windows. If you enable this policy setting . NET Framework Setup is turned off. The user cannot change this behavior. If you disable this policy setting . NET Framework Setup is turned on. The user cannot change this behavior. If you do not configure this policy setting . NET Framework Setup is turned on by default. The user can change this behavior.
Turn off . NET Framework Setup
This policy setting prevents the user’s computer from starting Microsoft . NET Framework Setup when the user is browsing to . NET Framework content in Internet Explorer. The . NET Framework is the next-generation platform for Windows. It uses the common language runtime and incorporates support from multiple developer tools. It includes the new managed code APIs for Windows. If you enable this policy setting . NET Framework Setup is turned off. The user cannot change this behavior. If you disable this policy setting . NET Framework Setup is turned on. The user cannot change this behavior. If you do not configure this policy setting . NET Framework Setup is turned on by default. The user can change this behavior.
Allow loading of XAML files
This policy setting allows you to manage the loading of Extensible Application Markup Language (XAML) files. XAML is an XML-based declarative markup language commonly used for creating rich user interfaces and graphics that take advantage of the Windows Presentation Foundation. If you enable this policy setting and set the drop-down box to Enable XAML files are automatically loaded inside Internet Explorer. The user cannot change this behavior. If you set the drop-down box to Prompt the user is prompted for loading XAML files. If you disable this policy setting XAML files are not loaded inside Internet Explorer. The user cannot change this behavior. If you do not configure this policy setting the user can decide whether to load XAML files inside Internet Explorer.
Allow loading of XAML files
This policy setting allows you to manage the loading of Extensible Application Markup Language (XAML) files. XAML is an XML-based declarative markup language commonly used for creating rich user interfaces and graphics that take advantage of the Windows Presentation Foundation. If you enable this policy setting and set the drop-down box to Enable XAML files are automatically loaded inside Internet Explorer. The user cannot change this behavior. If you set the drop-down box to Prompt the user is prompted for loading XAML files. If you disable this policy setting XAML files are not loaded inside Internet Explorer. The user cannot change this behavior. If you do not configure this policy setting the user can decide whether to load XAML files inside Internet Explorer.