A
adam
Hi
We have built an aspnet application which uses a windows
user control embedded in an object tag. The app is to be
deployed on a large client intranet. The object requires
full trust security to work properly.
What is the easiest way to configure the client's
corporate network. They would quite like to do it only
for users in one particular NT Group.
They run a logon script for each user, from which command
line stuff can be run. Is it possible to use caspol to
set the security for the intranet zone to full trust.
They would prefer this option than setting this for a
particular assembly. If so what would be the syntax? We
did have a look at the documentation but couldnt work out
how to change the settings for the whole zone?
We also tried using mscorcfg.msc to alter the enterprise
settings for this zone. Although this appeared to change
the client machines, (all of them) the assemblies wouldnt
run. This was the despite the fact that using mscorcfg to
check the permissions for the appropriate assemblies
showed they had full trust at enterprise, machine and
user levels. They wouldnt run until we changed it at the
individual machine level on the approrpirate pcs.
Adam
We have built an aspnet application which uses a windows
user control embedded in an object tag. The app is to be
deployed on a large client intranet. The object requires
full trust security to work properly.
What is the easiest way to configure the client's
corporate network. They would quite like to do it only
for users in one particular NT Group.
They run a logon script for each user, from which command
line stuff can be run. Is it possible to use caspol to
set the security for the intranet zone to full trust.
They would prefer this option than setting this for a
particular assembly. If so what would be the syntax? We
did have a look at the documentation but couldnt work out
how to change the settings for the whole zone?
We also tried using mscorcfg.msc to alter the enterprise
settings for this zone. Although this appeared to change
the client machines, (all of them) the assemblies wouldnt
run. This was the despite the fact that using mscorcfg to
check the permissions for the appropriate assemblies
showed they had full trust at enterprise, machine and
user levels. They wouldnt run until we changed it at the
individual machine level on the approrpirate pcs.
Adam