juniorsa
asked on
Open File - Security Warning..... (We can't verify who created this file. Are you sure you want to run this file?
Hi - I have a windows 8 pro client machine that connects to a windows 2012 domain.
When an application that is mapped to a local share as drive x: we get
Open File - Security Warning
We can't verify who created this file. Are you sure you want to run this file?
...
If I remap the same location to the Y: drive all works.
I have no idea why the X drive is treated differently than the Y drive.
Any suggestions?
Thanks
When an application that is mapped to a local share as drive x: we get
Open File - Security Warning
We can't verify who created this file. Are you sure you want to run this file?
...
If I remap the same location to the Y: drive all works.
I have no idea why the X drive is treated differently than the Y drive.
Any suggestions?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If it is .NET application, mapped drive may have different caspol policies
or path to exe on y was whitelisted somehow
ASKER
Thanks David Needham for your solution. It does provide a workaround that works :) The problem is I can't find out why it treats the location as a non-trusted location. It is clearly on the local network and should be treated as an intranet.
Can anyone help me find out why this location when mapped to the letter x triggers this warning?
Can anyone help me find out why this location when mapped to the letter x triggers this warning?
Your Y: drive isn't already entered in: Control Panel>Internet Options>Security Tab>Local Intranet>Sites>Advanced and your X: drive not, is it?
ASKER
There wasn't anything in that dialog box.
X: drive gave warning
Y: drive worked
I added the X: drive to the dialog
Control Panel>Internet Options>Security Tab>Local Intranet>Sites>Advanced
Now X: drive doesn't give warning.
I don't understand why it is not needed for the Y: drive and it is required for the X: drive.
X: drive gave warning
Y: drive worked
I added the X: drive to the dialog
Control Panel>Internet Options>Security Tab>Local Intranet>Sites>Advanced
Now X: drive doesn't give warning.
I don't understand why it is not needed for the Y: drive and it is required for the X: drive.
I would imagine that you've stumbled across one of Microsoft's numerous bugs, that don't exist!!!
ASKER
Provided excellent work around - still not sure of root cause