S
Stefan Falk
Hello everybody,
I just tried the following in order to have .NET applications in a given
network folder enough permissions to run:
On the domain controller, in .NET 1.1 framework configuration, created a
code group for the Organization under the All_Code group giving the URL
file://P:/Apps/* full trust (P: is a network drive mapped to the file
server). Then I created an MSI file for the organization and deployed this
MSI file via Group Policy to a test workstation.
The workstation (running XP SP2) successfully got the MSI file (as I can see
in the local .NET framework configuration). However, the changes have no
effect: Apps from P:\Apps still get security exceptions.
On a developer machine, that approach worked with minor changes: There,
there was a machine-wide code group under Local_Intranet giving
file://P:/SomeFolder/* full trust. Therefore I thought it would be that easy
to just have P:\Apps configured organization-wide.
What must I do? Use UNC (but why did P: work in the local machine
configuration then)? Have the new code group be nested under a
Local_Intranet code group as is in the machine configuration?
Any enlightment on this is well appreciated.
Greetings,
Stefan Falk
I just tried the following in order to have .NET applications in a given
network folder enough permissions to run:
On the domain controller, in .NET 1.1 framework configuration, created a
code group for the Organization under the All_Code group giving the URL
file://P:/Apps/* full trust (P: is a network drive mapped to the file
server). Then I created an MSI file for the organization and deployed this
MSI file via Group Policy to a test workstation.
The workstation (running XP SP2) successfully got the MSI file (as I can see
in the local .NET framework configuration). However, the changes have no
effect: Apps from P:\Apps still get security exceptions.
On a developer machine, that approach worked with minor changes: There,
there was a machine-wide code group under Local_Intranet giving
file://P:/SomeFolder/* full trust. Therefore I thought it would be that easy
to just have P:\Apps configured organization-wide.
What must I do? Use UNC (but why did P: work in the local machine
configuration then)? Have the new code group be nested under a
Local_Intranet code group as is in the machine configuration?
Any enlightment on this is well appreciated.
Greetings,
Stefan Falk