Set execution policy via CM 2012 SP1

Question

Good afternoon everyone.
Sorry about the last question.  I'd attempted to resolve this in so many ways that the last question was based on an old attempt.
I'm trying to set the PowerShell Execution Policy through a batch file.  Specifically, the batch file contains one single command: 
PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& {Start-Process PowerShell -ArgumentList 'Set-ExecutionPolicy RemoteSigned -Force' -Verb RunAs}"
If I run this command standalone, either as local Admin or not, the batch file completes and the execpol is changed appropriately.
When deploying the batch file through CM, Software Center shows a successful installation but the ExecPol value does not change.  The batch file within CM is configured to run as administrator.
Any suggestions as to what I may be doing wrong would be greatly appreciated.
Thanks very much.
IAmStrings

Answer 1

Hi Narco.
Yep, tried that as well.  Tried Registry /s with a reg file and tried calling another PoSH script under a temp ExecPol of bypass that ran:
set-itemproperty-path"registry::HKLM\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell"-nameExecutionPolicy-value"UnRestricted"
If they're deployed, they don't change the value. 
It's almost as if the deployment isn't really running as admin.  I've looked at the execmgr.log but I never see any entries with "Failed" or anything like that.  There are some entries stating that it's "WaitingServiceWindow" but then I later see
the state changing from "WaitingServiceWindow to Ready"
Thanks for replying.
IAmStrings