Help!! Domain privs to run standalone .Net EXE from domain account?

[JackBlack]

Hi, all. Still trying to track down what privileges are necessary to allow
a Windows XP/Pro SP2+ (appropriate .Net framework installed) workstation to
execute a stand-alone VB.Net (2k5) application on a domain drive from a
domain account. The domain accounts are NOT adminisrator, and the
stand-alone app runs fine from the local drive in a folder with sufficient
privs. Setting those same privs on a domain folder does not work.

Any suggestions would be helpful here. This must run as stand-alone
(basically XCOPY distribution) because running an installer on each machine
is not feasible.

Jack

 

[Chris Dunaway]

Hi, all. Still trying to track down what privileges are necessary to allow
a Windows XP/Pro SP2+ (appropriate .Net framework installed) workstation to
execute a stand-alone VB.Net (2k5) application on a domain drive from a
domain account. The domain accounts are NOT adminisrator, and the
stand-alone app runs fine from the local drive in a folder with sufficient
privs. Setting those same privs on a domain folder does not work.

Any suggestions would be helpful here. This must run as stand-alone
(basically XCOPY distribution) because running an installer on each machine
is not feasible.

Jack

You need to grant trust on the local workstation to the app which is
running from the network share. You can do this with the .Net
Framework configuration tool or using the caspol.exe utility.

Chris

 

[JackBlack]

Well, I've already tried the caspol.exe option, and it didn't have any
effect whatsoever (based on another posting in this group). I also haven't
found where the config with the configuration tool should be set, so any
pointers in that direction would help. Is it me or is this kind of thing
really badly documented by MS???

Jack

 

[aaron.kempf]

crappy ass .NET is documented REALLY poorly

they just need to make it open source; and I won't start in .NET until
they do

-Aaron