Jump to content


P3nnyw1se

can't bypass 'PowerShell Execution Policy'

Recommended Posts

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?

Share this post


Link to post
Share on other sites

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...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.