WinXP SP2 / IE6

[P James]

I've got a web application that uses the FileSystemObjects to write to a
file locally. Prior to XP SP2 my users simply had to agree to the ActiveX
Security Dialog. Post XP2, my users have to jump repeatedly through several
security warnings including the new yellow bar at the top of IE, as well as
the original ActiveX Security Dialog. Is there a way to eliminate some or
all of these hoops? I remember reading years ago about marking ActiveX DLLs
as safe for scripting. Does that apply here? Or does SP2 ignore those
registry entries now?

Thanks,
PJ

[P James]

Helping myself here a little bit, I came across the following kb article
about how to mark an object as Safe For Scripting...
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdhowsfs.asp

Turns out this eliminates only the third dialog box presented to the user.
The first (the yellow bar and the popup menu that the user has to click to
agree to allow active content) and then the second dialog box remain, even
after marking my DLL as safe for scripting per the above registry entry.

My question becomes, how do I get rid of the first two hoops now, caused by
WinXP SP2? They are driving my users crazy. See below for more details.
Any help is much appreciated.

Thanks,
PJ



"P James" > wrote in message
...
>
> I've got a web application that uses the FileSystemObjects to write to a
> file locally. Prior to XP SP2 my users simply had to agree to the ActiveX
> Security Dialog. Post XP2, my users have to jump repeatedly through
several
> security warnings including the new yellow bar at the top of IE, as well
as
> the original ActiveX Security Dialog. Is there a way to eliminate some or
> all of these hoops? I remember reading years ago about marking ActiveX
DLLs
> as safe for scripting. Does that apply here? Or does SP2 ignore those
> registry entries now?
>
> Thanks,
> PJ
>
>
>
>
>
>

[RJK]

Lots of options to Allow | Disable | Enable | Prompt for ActiveX controls
in Advanced Options, in IE6 , and can be set for each Zone.

regards, Richard


"P James" > wrote in message
...
>
> Helping myself here a little bit, I came across the following kb article
> about how to mark an object as Safe For Scripting...
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdhowsfs.asp
>
> Turns out this eliminates only the third dialog box presented to the user.
> The first (the yellow bar and the popup menu that the user has to click to
> agree to allow active content) and then the second dialog box remain, even
> after marking my DLL as safe for scripting per the above registry entry.
>
> My question becomes, how do I get rid of the first two hoops now, caused
> by
> WinXP SP2? They are driving my users crazy. See below for more details.
> Any help is much appreciated.
>
> Thanks,
> PJ
>
>
>
> "P James" > wrote in message
> ...
>>
>> I've got a web application that uses the FileSystemObjects to write to a
>> file locally. Prior to XP SP2 my users simply had to agree to the
>> ActiveX
>> Security Dialog. Post XP2, my users have to jump repeatedly through
> several
>> security warnings including the new yellow bar at the top of IE, as well
> as
>> the original ActiveX Security Dialog. Is there a way to eliminate some
>> or
>> all of these hoops? I remember reading years ago about marking ActiveX
> DLLs
>> as safe for scripting. Does that apply here? Or does SP2 ignore those
>> registry entries now?
>>
>> Thanks,
>> PJ
>>
>>
>>
>>
>>
>>
>
>

[Steven L Umbach]

The info below on some of the new Group Policies settings for Internet
Explorer may help such as the one for add ons. --- Steve

http://www.microsoft.com/technet/security/prodtech/windowsxp/secwinxp/xpsgch04.mspx

"P James" > wrote in message
...
>
> I've got a web application that uses the FileSystemObjects to write to a
> file locally. Prior to XP SP2 my users simply had to agree to the ActiveX
> Security Dialog. Post XP2, my users have to jump repeatedly through
> several
> security warnings including the new yellow bar at the top of IE, as well
> as
> the original ActiveX Security Dialog. Is there a way to eliminate some or
> all of these hoops? I remember reading years ago about marking ActiveX
> DLLs
> as safe for scripting. Does that apply here? Or does SP2 ignore those
> registry entries now?
>
> Thanks,
> PJ
>
>
>
>
>
>