How to disable Open file – Security warning

After installed SP2 for Windows Server 2003 Standard, If I try to run batch files (.bat; .cmd;.lnk;.pif) from the network share, I get an “Open file – Security warning” -dialog where I must confirm that you allow the execution of the unsigned file.

security-warning1.jpg

Basically this prevents scheduled scripts to run on the system. If you are absolutely sure you want to allow the execution without confirmation, you can add the server which shares the executable file(s) in the Internet Explorer’s Local Intranet Zone. The systax is file://servername not http://servername. Note that this action compromises the system security.

This entry was posted on Monday, July 2nd, 2007 at 12:01 am and is filed under IT-Windows Server & TS. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

9 Responses to “How to disable Open file – Security warning”

  1. Steve O Says:
    July 19, 2007 at 6:36 pm | Reply

    Thanks for this. It was just starting to annoy me too.

  2. iswarade Says:
    July 20, 2007 at 9:29 am | Reply

    Nice, I can help.

  3. Xman Says:
    November 14, 2007 at 1:56 pm | Reply

    How can i do this programatically. Like adding the share to the registry or something like that ?

  4. M Mustafa Says:
    April 30, 2008 at 9:22 am | Reply

    Excellent explaination, thanks you so much

    Well done and many thanks again

  5. Nguyen Hiep Thong-VietNam Says:
    February 3, 2009 at 12:44 pm | Reply

    http://answers.yahoo.com/question/index?qid=20061107232556AAsBdFe
    View in this link !

  6. Holly Says:
    May 31, 2009 at 11:33 pm | Reply

    Thanks, it’s very useful for me.

  7. HITESH Says:
    July 20, 2009 at 4:51 am | Reply

    THANKS DUDE TO SOLV MY PROBLEM

  8. Eric Says:
    October 2, 2009 at 2:06 pm | Reply

    I am reconfiguring a new terminal server and I can not get this to go away for my terminal server users. It does not affect the admin account, only users. I have tried everything “ever” posted on the internet to no avail. Going on a wekk of trouble shooting already. I use Group Policies to config this but, as best I can tell, the settings are not being applied to the user profiles. I have an older Terminal Server which is accepting the Group Policies just fine. Just this new Terminal Server is causing the pain. Again, I have tried every fix posted to no avail. Any help or sugggestions anyone could toss my way would be greatly appreciated.

  9. Eric Says:
    October 2, 2009 at 3:12 pm | Reply

    Answered my own problem a few minutes ago.

    The policy “MUST” be set on the terminal server itself directly by running gpedit.msc on the Terminal Server. I was attempting to set the policy using domain policies on the Domain COntroller in Active Directory. Odd, I don’t know why that would not have worked other than maybe the Terminal Server might have had to be in the OU of the policy for it to work. Oh well, it’s fixed now.

Leave a Reply