[POSH] ExecutionPolicy: PerUser or PerMachine
- From: "Keith Hill [MVP]" <r_keith_hill@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 28 Apr 2006 15:35:36 -0600
Shouldn't the ExecutionPolicy be stored under HKCU instead of HKLM? I know
that Windows tends not to be multi-user but in terminal services scenarios
it is multi-user. In that scenario do you want one user to dictate to the
other users what the execution policy is going to be? Or worse, last person
to set it wins. This is also a drag in Vista because you have to elevate in
order to even execute Set-ExecutionPolicy because by default the filtered
token of a protected admin prevents writes to HKLM. BTW this would also
solve the issue of new installs wiping out the execution policy since it is
per user i.e. the setting would still be there from a previous install.
--
Keith
.
- Follow-Ups:
- Re: [POSH] ExecutionPolicy: PerUser or PerMachine
- From: Jeffrey Snover [MSFT]
- Re: [POSH] ExecutionPolicy: PerUser or PerMachine
- Prev by Date: Re: No table headers for Get-ItemProperty
- Next by Date: Re: [PSH] Methods/functions and blank spaces
- Previous by thread: Security and monad
- Next by thread: Re: [POSH] ExecutionPolicy: PerUser or PerMachine
- Index(es):