Avoiding Explorer’s Security Warning Prompts

June 12, 2008

in Windows

Windows XP Service Pack 2 and Windows Server 2003 Service Pack 1 made some changes to the way Windows handles specific file types opened or downloaded from certain locations, which results in Open File – Security Warning prompts like these:

SecurityWarning

Quite often users see these prompts in environments where files are opened from UNC paths (think mapped drives or redirected folders) on Distributed File System namespaces. If you have this scenario (which I think you should be) because you are doing something like redirecting Start Menus, you can disable these prompts for your internal network locations.

Ideally you would do this by deploying specific Intranet zone settings (as in the screenshots below) or adding your internal sites to the Intranet zone via a script, Group Policy (Preferences or Internet Explorer Maintenance) or your tool of choice.

LocalIntranet1LocalIntranet2 

There’s a heap of information on how this stuff works at these links:

But all of that is not really the point of this post. I stumbled across a really simple method of telling Windows to avoid those checks and just open the files – create the environment variable SEE_MASK_NOZONECHECKS and set it to 1. You can set this as system environment variable but it appeared to be a little more consistent if set as a user environment variable. Not recommended for wide scale deployment but useful none the less.

{ 2 trackbacks }

{ 3 comments }

1 Brendon Davis June 13, 2008 at 1:45 am

I will definately be putting the registry key into action on my testing and DEV VM’s. Where the popups are just a pain in the ….

Thanks Parky

2 Shawn Bass June 19, 2008 at 9:28 pm

Aaron,

Nice post as always. FWIW, this restriction is only enforced by the Windows shell (Explorer and IE). So if you’re trying to get this bypassed on a larger number of machines temporarily and you don’t want to mess with the environment variables, you can simply invoke the command that you want to run via a cmd prompt (batch file).

Shawn

3 Aaron Parker June 19, 2008 at 9:31 pm

Thanks Shawn. I’m currently in the process of deploying a couple of hotfixes to fix some issues we’re seeing related to this. I might have to document these fixes.

Comments on this entry are closed.

Previous post:

Next post: