Agreed. Restricted is useless.
I'm sure developers are all gung ho about signing their 1000 line script masterpieces, but as a sysadmin, signing scripts is too onerous for my 10-20 line throw together scripts to solve an immediate problem. Unrestricted is the way to go. On Tue, Nov 5, 2013 at 12:26 PM, Trevor Sullivan <[email protected]> wrote: > Hey folks, > > > > Can anyone make a specific and compelling argument for why the PowerShell > execution policy should be configured to anything **except** > “unrestricted? > > > > In other words, is there any **solid** reason why one of these values > should be configured instead? > > · RemoteSigned > > · AllSigned > > · Restricted > > > > As best I can tell, there is no apparent benefit of configuring one of the > above, bulleted items, since you can simply call PowerShell.exe > -ExecutionPolicy Bypass to work around it. > > > > Cheers, > > Trevor Sullivan > > ================================================ > Did you know you can also post and find answers on PowerShell in the > forums? > http://www.myitforum.com/forums/default.asp?catApp=1 ================================================ Did you know you can also post and find answers on PowerShell in the forums? http://www.myitforum.com/forums/default.asp?catApp=1
