Group Policy configuration Excution policy for PowerShell

PowerShell has its own security mechanism, by default, PowerShell execution policy is limited, that is, restricted, we want to execute the script must first adjust this execution policy, on the computer in Administrator mode to open PowerShell, Then enter the Set-excutionpolicy command, followed by the execution policy you want to set, and PowerShell's execution strategy is restricted,allsigned,remotesigned,unrestricted. Bypass these 5 kinds of models, the specific strategy we can learn from Baidu.
Today's introduction is how to modify a user's execution policy through Group Policy (note: After you modify the execution policy through Group Policy, local execution set-excutionpolicy a warning that your changes cannot take effect because of Group Policy)

First we open the Group Policy console, the user Configuration-Administrative Templates--window component---Windows Powershell, find the object that enables script execution under this path, modify its value, and usually take security into account, we will select "Allow local script and remote signature script"

After the configuration is complete, we can go to the client to use Gpupdate/force strong brush Group Policy, if it is your 2012 domain control, then more simple, directly select the Group Policy to apply the OU, right-click, in the pop-up menu, select "Group Policy Updates", This Group policy refreshes the applicable objects in the OU in immediate Group Policy

Group Policy configuration Excution policy for PowerShell