D
Disso
Hi all,
I test adding programs to exceptions running from mapped network drives.
Here are the results.
1- Mapped network drive - T:\test.exe
2- UNC Path: \\192.168.2.5\share\test.exe
T = \\192.168.2.5\share
- Run the program from map network drive and click unblock | Go to
exceptions tab | Edit program's entry | Path: \\192.168.2.5\share\test.exe
- Run the program once again from T, no blocking warning even the UNC path
is shown in exceptions.
- Manually add program's path (T:\test.exe), run the program, warning
appears.
Is it possible to use mapped network drive letters in exceptions? Why
exceptions requires UNC names? I analyze with procexp and it shows programs
running path as network drive.
Thanks,
Mark.
I test adding programs to exceptions running from mapped network drives.
Here are the results.
1- Mapped network drive - T:\test.exe
2- UNC Path: \\192.168.2.5\share\test.exe
T = \\192.168.2.5\share
- Run the program from map network drive and click unblock | Go to
exceptions tab | Edit program's entry | Path: \\192.168.2.5\share\test.exe
- Run the program once again from T, no blocking warning even the UNC path
is shown in exceptions.
- Manually add program's path (T:\test.exe), run the program, warning
appears.
Is it possible to use mapped network drive letters in exceptions? Why
exceptions requires UNC names? I analyze with procexp and it shows programs
running path as network drive.
Thanks,
Mark.