P3nnyw1se Posted September 4, 2014 Report post Posted September 4, 2014 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\machinerequestconfigBrandingTitle = powershellexecutionpolicy.it returned ->Default : 0MyNewlyCreated : 1so the new policy is requestedMy 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? Quote Share this post Link to post Share on other sites More sharing options...