Set Execution policy scope through GPO - by Jeff Wouters

Status : 


Sign in
to vote
ID 781337 Comments
Status Active Workarounds
Type Suggestion Repros 0
Opened 3/14/2013 3:19:51 AM
Access Restriction Public


Although you can configure the scope of the PowerShell execution policy through the commandline, you can't configure the scope through GPO.
I think this should be possible.
Sign in to post a comment.
Posted by Mattias Borg - on 4/20/2013 at 11:31 AM

This is how you could set the execution policy through GPO:

Windows Components/Windows PowerShell
Policy: Turn on Script Execution                         
Setting: Enabled     
Execution Policy: Allow local scripts and remote signed scripts

Posted by Michel de Rooij on 3/14/2013 at 5:55 AM
What good is having a GPO to set the scope to process (i.e. current session) when there's no process (session)?
Chicken, egg ..
Posted by Jeff Wouters on 3/14/2013 at 5:11 AM
@Michel: Perhaps I should clarify. There are multiple options on the commandline, such as CurrentUser/LocalMachine/MachinePolicy/Process/UserPolicy. Although I should think that the machine and currentuser could be currently configured through GPO, process for example can't.
Posted by Michel de Rooij on 3/14/2013 at 4:08 AM
Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell : Script Execution