"VanguardLH" <V@nguard.LH> wrote in message news:firstname.lastname@example.org...
> Viktor Krammer wrote:
>> IE7 on XP and Vista is based on the same code base. This is the reason why
>> you may find some protected mode settings also under XP, but which are not
>> in effect under XP since protected mode is based on new security features
>> that are only available in Vista (and later).
> I was wondering if the install of IE7 was what created this policy
> settings. Seems silly, however, to establish policy settings in a
> version of Windows that cannot be effected. Obviously the install could
> detect that it was not Vista under which IE7 was being installed and
> simply not add those policy settings.
I think the same sort of thing started happening in IE6sp2 regarding "hardening"
E.g apparently that mostly applies to Windows Server 2003.
<TITLE>What Is Internet Explorer Maintenance Extension?: Group Policy</TITLE>
(Live Search for
"internet explorer" hardening site:microsoft.com
Updated: March 28, 2003
Internet Explorer Enhanced Security Configuration, also known as Microsoft Internet Explorer Hardening,
reduces a server's vulnerability to attacks from Web content by applying more restrictive Internet Explorer security settings.
You can deploy Internet Explorer Enhanced Security Configuration settings to target computers
through Internet Explorer Maintenance only if Internet Explorer Enhanced Security Configuration
is enabled on the target computer. This is because the Internet Explorer Maintenance CSE stores
these settings on the target computer in the equivalent registry location from where they were imported.
Those registry keys are read only by Windows Server 2003 because it is currently
the only operating system that supports Internet Explorer Hardening.