S
Shacker
Hi everyone,
I understand that there's no way to run .NET compiled code from a
network share without security modification but here's my issue - the
code needs to run on a number of workstations (50 or more) and having
each one modify their individual workstations would be an
administrative concern (the company is rather large and individual
workstation changes are frowned upon). Many of the workstations are
locked down, anyway.
Instead of using CASPOL or the .NET Configuration MMC, can the security
be granted on the server side (i.e., the server where the assemblies
reside)? This way we don't have to touch ANY workstation and
administration is easy.
Thanks in advance!
- Shacker
I understand that there's no way to run .NET compiled code from a
network share without security modification but here's my issue - the
code needs to run on a number of workstations (50 or more) and having
each one modify their individual workstations would be an
administrative concern (the company is rather large and individual
workstation changes are frowned upon). Many of the workstations are
locked down, anyway.
Instead of using CASPOL or the .NET Configuration MMC, can the security
be granted on the server side (i.e., the server where the assemblies
reside)? This way we don't have to touch ANY workstation and
administration is easy.
Thanks in advance!
- Shacker