"Set-ExecutionPolicy RemoteSigned -Scope CurrentUser" Does Microsoft have a Default Set-Execution command?

Question

PS C:\Users\19163> Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

Execution Policy Change

The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose

you to the security risks described in the about_Execution_Policies help topic at

https:/go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the execution policy?

[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"):

setting this to yes lets you run deployment workbench however,.....

???Once this is ran can you auto default it back if your done useing Deployment Workbench???

this is a security risk so can we default the policy all at once?

much like SFC/Scannow checks for issues 

a Policy scanner that checks with a default version for changes 

!!!Default and restricted do not lockout Deployment workbench again!!!

see once it was changed it stayed even if it displays restricted again.

I had a error like this before changing the execution policy. If I defaulted it how come when I change it back it no longer has this error?

Answer 1

Thank you for your help,

If I changed the set execution policy back to restricted, how come I no longer get this error message when I start the deployment work bench like before doesnt that lock it back out as its restriced again. If deployment work bench has nothing to do with powershell also why did it have this error when I started it the first time from powershell and the startbutton?  that's where it got confusing 

Answer 2

PS execution policies only apply to PS scripts. PS does not prevent you from calling programs like .exe or links to .msc, which is what you are doing by calling .lnk to DeploymentWorkbench.msc.