Re: Cannot run program from network drive
From: Nicole Calinoiu (calinoiu)
Date: 04/11/05
- Next message: jblo: "Re: Cannot open log for source {0}. You may not have write access. (Access right wanish after a while)"
- Previous message: Stefan: "Re: SIGN-IN AUTOMATICALLY..."
- In reply to: Joseph MCAD: "Re: Cannot run program from network drive"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 11 Apr 2005 08:54:26 -0400
"Joseph MCAD" <anonymous@microsoft.discussions.com> wrote in message
news:%23JPQQDpPFHA.1884@TK2MSFTNGP15.phx.gbl...
> April 8, 2005
>
> To make this work for all computers, just add this code group under the
> Enterprise --> All_Code group.
This will include applications run from the internet, so it's not
necessarily a great idea even if a strong name membership condition will
also be used. One can add a local intranet zone group under All_Code at the
enterprise level configured identically to the group that is included by
default at the machine level. The new strong name group should be placed
under such a group in order if the goal is to trust assemblies signed with
the relevant key iff they are run from within the intranet.
> Do the exact same thing and let the assembly
> have FullTrust, but check the box that states Policy levels below this
> level
> will not be evaluated and check This policy level will only have the
> permissions from the permission set associated with this code group. This
> will allow the assembly to have fulltrust throughout the domain.
No, it will not. Despite its name, the enterprise policy resides on the
local client machine, and changes are not automatically propagated over a
domain. Changes to the enterprise policy must be deployed to the respective
client machines (exactly as if they were changes to the machine-level
configuration). On a Windows domain, one fairly common means of deploying
such policy changes is as an MSI (created via .NET Configuration MMC)
distributed as a GPO.
> Hope this
> helps!
>
> Joseph MCAD
>
>
>
> "Bendix" <Bendix@discussions.microsoft.com> wrote in message
> news:46772C63-25DF-4353-BC39-CF9E049BDF4A@microsoft.com...
>>I tried the not recommended solution, but it only work for that specific
>> computer. What if I want to run the program from a lot of workstations?
>>
>> Bendix
>>
>> "Joseph MCAD" wrote:
>>
>>>
>>> April 6, 2005
>>>
>>> You are right. Doing that isn't recommended. What would be better is
>>> to
>>> strong name the assembly and then create a code group under
>>> LocalIntranet_Zone that gives FullTrust to assemblies with that strong
>>> name.
>>> What are the details of the Security Exception? I believe I could solve
>>> your
>>> permission problem, if I had the details?
>>>
>>>
>>> Joseph MCAD
>>>
>>
>
>
- Next message: jblo: "Re: Cannot open log for source {0}. You may not have write access. (Access right wanish after a while)"
- Previous message: Stefan: "Re: SIGN-IN AUTOMATICALLY..."
- In reply to: Joseph MCAD: "Re: Cannot run program from network drive"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
