The purpose is to protect the user against malicious downloads from the Internet but unfortunately it treats your local server files in the same way . It has probably caused more annoyance to millions of Windows users than any other security feature, as it means the warning message will be displayed even when routine programs like Accounts and Payroll are launched from a network location
So what can be done about this ...
There are a number of approaches
1) Google searches to fix the issue will give details of using the Group Policy editor to disable this, this is NOT reccommended , it would expose the user to genuine risks of malicious down-loads.
2) For most small businesses, there will just be a single server share often called something like AppServer1. This can easily be identified as a trusted location , but it does require carrying out a little configuration on each PC that you want to rid of these pop-up messages.
Do the following :
a) Use Windows Explorer :
Click to My Network Places ,Entire Network , Microsoft Windows Netork . Depending on how the network system is set up for company XYZ , you will see a folder structure something like XYZ, AppServer1, where your various applications are located on AppServer1, make a note of what it is called.
b) Open Internet Explorer :
Click on Tools , Internet Options,Security ,Local Intranet . Click the Sites button, click advanced , you will see the dialogue window pictured right
Add your file server share name as shown ( yes , do include the word file as shown)
This will add your server share as a trusted intranet location , which is exactly what it is !!!
The warning messages will no longer appear for applications run from your server , while still giving you full protection from any web-based downloads
This may still seem too complicated for most users , so the final option is to do nothing, just explain to your users that if it comes from running a regular network application, it is safe to run the file !!!
Finally , ITS will in future , digitally sign all applications with
a trusted certificate ,issued by a Microsoft-approved certificate authority
Comodo.
This will change the warning message to a re-assuring yellow shield , but more importantly it guarantees that our code cannot be tampered with .
For this option , you need to do NOTHING !!
This will change the warning message to a re-assuring yellow shield , but more importantly it guarantees that our code cannot be tampered with .
For this option , you need to do NOTHING !!