1. By all means let us see how to do this by configuring CAS Policies.


  2. Ben (the VPC Guy) writes: "The reason this happens is that PowerShell is a .Net application – and as a .Net application it does not run with sufficient privilege to be able to talk to our COM interfaces. "

    This is what triggered me into thinking: then why not configure PowerShell with enough privileges.

    After a couple of tests I found out that PowerShell.exe is not a *real* .NET app so I can’t configure it using CAS Policies as far as I can see…


Comments are closed.