Hi @Ricky
as an update:
we are finding that in order for the Set-Execution policy job to work (it always states job successful but the policy has not changed) the server needs to be logged in as the Run As account and PowerShell open
any other scenario - logged in but PowerShell closed, not logged in etc, the outcome is no change in the policy
would appreciate any other thoughts you have
thanks
Andy