Skip to content

can't bypass 'PowerShell Execution Policy'

Featured Replies

I've been trying to use unsigned powershell scripts as detection methods on several applications.
But it would only allow them if they were signed.

No problem..
-Went to administration
-Created a custom client policy called : "MyNewlyCreated"
-Picked Computer Agent -> PowerShell Execution Policy, changed it from 'All Signed' to 'Bypass'
-Made sure this custom client setting(2) had higher prioritize than the Default(1000)
-deployed the new custom client setting to a test collection
-asked the pc within the test collection to request new machine policy and client settings

-using powershell, I read from root\ccm\policy\machinerequestconfig
BrandingTitle = powershellexecutionpolicy.

it returned ->

Default : 0
MyNewlyCreated : 1

so the new policy is requested

My applications still fail to detect, saying they can't run unsigned powershell scripts.
what am I doing wrong?, if I don't allow them to be run by bypassing through a custom client setting, then where?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.