cmaohio
asked on
GPO Open File Security Warning Dialog - Tried Everything!
So far, I have tried everything under the sun and I am coming up short. I really need some help here. We just upgraded from Server 2003 to Server 2008 Active Directory servers and now I'm getting security Warnings all over the place and software deployments won't run.
this is what I have done:
These settings are supposed to work but I still get prompted no matter what!
One scenario is I want to open a file through a DFS share like: \\domain.org\deploy\filena me.msi But that won't run I get the warning.
I don't know what else to do, I have been through this a thousand times.
this is what I have done:
Created a Group Policy. Under Computer (and User) Configuration\Policies\Adm inistrativ e Templates\Windows Components\Internet Explorer\Internet Control Panel\Security Page I set these:
Intranet Sites: Include all network paths (UNCs): Enabled
Intranet Zone Template: Low
Site to zone Assignment List: file://domain.org:1 (our domain), flie://server1:1, etc (1 equals Intranet Zone)
turn on automatic detection of the intranet: disabled
Under the /Intranet Zone section I modified: Launching programs and unsafe files: Enable with "enable" below that.
Intranet Zone Template: Low
Site to zone Assignment List: file://domain.org:1 (our domain), flie://server1:1, etc (1 equals Intranet Zone)
turn on automatic detection of the intranet: disabled
Under the /Intranet Zone section I modified: Launching programs and unsafe files: Enable with "enable" below that.
These settings are supposed to work but I still get prompted no matter what!
One scenario is I want to open a file through a DFS share like: \\domain.org\deploy\filena
I don't know what else to do, I have been through this a thousand times.
Should "Turn on automatic detection of the intranet" be enabled to allow the other settings to work?
ASKER
All the posts I have read said to turn that setting off and turn on the UNC setting.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
That was the problem. For some reason the system was believing that the files came from an untrusted source.
ASKER
Sure, I agree with you. However, they were always from an untrusted source, yet, before the AD upgrade to 2008, I never got the warning.
as time goes by Microsoft strengthens its security protocols, Microsoft is a much more security conscious company than in the past
ASKER
I ultimately found the reason.