I agree on setting this via GPO but sometimes you just don’t have access to these GPO’s or sys admins don’t want to set this so that’s why I’ve added the first line, thanks for the tips on the confirmation message and the execution policy level.

Regards,

Kees

Thanks,
Alain

The executionpolicy for PowerShell is something that, in my opinion, should be set by a policy and not in each script. Now you would get a message where you would have to confirm that you want to change the exectution policy.
But in case you do want this to be included in your sript, some recommendations:
To avoid that nasty confirmation message, use the -force parameter.
Set the execution policy on the leven you desire. Right now the default (LocalMachine) will be used where (i think) process or currentuser level should suffice in this case?

And last… very good idea and code 😀

Jeff.