Restrict or enable Powershell execution
Microsoft recommends restricting the Powershell Execution environment to secure against malicious attacks such as Cryptolocker etc. These scripts help secure Powershell from executing PS scripts and only interactive sessions are supported with the correct elevated privileges.
A custom field update is included at lines 12 and 15 that allow the Procedure to update a 'Powershell Status' custom field that can then be used to create Views for Policy Management use.
I've been meaning to write this for some time. I'd say the exchange is working!
This should be part of a standard deployment it looks like
Do either of these require a reboot to take effect?
No neither script should require a reboot.