Quantcast
Channel: Configuration Manager 2012 - Application Management forum
Viewing all articles
Browse latest Browse all 4762

Client Setting: PowerShell Execution Policy - Bypass

$
0
0

I am trying to setup an application that will install RDC and BITS using powershell and the ServerManager module.  I have set the PowerShell execution policy to Bypass.  From the deployment I am runningpowershell.exe -file .\script.ps1.  This does not seem to work.  If I change the command topowershell.exe -ExecutionPolicy ByPass -file .\script.ps1 then that seems to work.  Can someone explain how this client setting referenced below is supposed to work?  I assumed that setting this to "Bypass" would allow the PowerShell script to run without having to customize the command line.  Also what about the powershell scripts that can be used to determine if an application is already installed?

PowerShell execution policy

When you select Bypass, the Configuration Manager   client bypasses the Windows PowerShell configuration on the client computer   so that unsigned scripts can run. When you selectRestricted, the   Configuration Manager client uses the current Windows PowerShell   configuration on the client computer, which determines whether unsigned   scripts can run.

This option requires at least Windows PowerShell version   2.0 and the default isRestricted.

http://technet.microsoft.com/en-us/library/gg682067.aspx


-Jason Dye Consultant - Systems Management



Viewing all articles
Browse latest Browse all 4762

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>