> When deployed, we can:
Set the user (or machine) execution policy. Not really a security issue; if someone can get onto the system to run a script, restricted script execution can be bypassed trivially anyway.
Sign the script. Requires a code-signing certificate, maybe from the AD CA?
Use a batch file as a launcher - launch the script with powershell -ExecutionPolicy Bypass -File script.ps1 (I did say it's trivial to bypass the execution policy - it's more insurance against ---idiots--- unaware users downloading and running scripts than a real security measure.)