deploying executable to network to be ran in logon script

31 Jul 2006 9:59 PM

Tyler

I have written a .net app that basically collects a few pieces of information
from the computer it was executed on. (Domain,User,MachineName, etc....) I
would like to deploy this executable to a location on the network and include
it in the logon script. However, when testing i discovered the security
issue that comes along with executing a .net app from a network location. I
have about 300 users that will need to execute this program. Its not
practical to change the CAS settings on all of these machines.

Is there a better way to do this? Am I missing something, it seems like it
has to be easier than this?

Any thoughts or suggestions are welcome.

Thanks

--
Tyler

31 Jul 2006 10:55 PM

Joe Kaplan (MVP - ADSI)

You need to either change the CAS settings (which you could possibly do
through GPO or a machine-level logon script) or deploy the application
locally (possibly via GPO again), or make sure your app doesn't request any
data that isn't allowed (which probably won't get you what you want).

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--

Show quoteHide quote

"Tyler" <Ty***@discussions.microsoft.com> wrote in message
news:91C710BE-CCF5-48AF-8D18-F9820546F8DF@microsoft.com...
>I have written a .net app that basically collects a few pieces of
>information
> from the computer it was executed on. (Domain,User,MachineName, etc....)
> I
> would like to deploy this executable to a location on the network and
> include
> it in the logon script. However, when testing i discovered the security
> issue that comes along with executing a .net app from a network location.
> I
> have about 300 users that will need to execute this program. Its not
> practical to change the CAS settings on all of these machines.
>
> Is there a better way to do this? Am I missing something, it seems like
> it
> has to be easier than this?
>
> Any thoughts or suggestions are welcome.
>
> Thanks
> --
> Tyler