Re: IIS7: CreateProcessWithLogonW access denied
- From: David Wang <w3.4you@xxxxxxxxx>
- Date: Thu, 19 Jun 2008 22:15:52 -0700 (PDT)
On Jun 19, 10:20 am, "Kyle Alons" <re...@xxxxxxxxxxxx> wrote:
There is no alternative for your type of code to work with the default
setting -- that would be allowing the very security vulnerabilities
which were closed by changing the default.
Your choices are to either change the default or modify the default
Code Access Security on your system.
How is that done?
I highly recommend searching on the terms "Modify Code Access
Security" to arrive at good answers for your question.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
.
- Follow-Ups:
- Re: IIS7: CreateProcessWithLogonW access denied
- From: Kyle Alons
- Re: IIS7: CreateProcessWithLogonW access denied
- References:
- IIS7: CreateProcessWithLogonW access denied
- From: Kyle Alons
- Re: IIS7: CreateProcessWithLogonW access denied
- From: David Wang
- Re: IIS7: CreateProcessWithLogonW access denied
- From: David Wang
- Re: IIS7: CreateProcessWithLogonW access denied
- From: Kyle Alons
- IIS7: CreateProcessWithLogonW access denied
- Prev by Date: Re: iis 5.1, internet explorer, cached credentials and kerberos
- Next by Date: Re: SelfSSL IIS 6.0
- Previous by thread: Re: IIS7: CreateProcessWithLogonW access denied
- Next by thread: Re: IIS7: CreateProcessWithLogonW access denied
- Index(es):
Relevant Pages
|