CMPivot: Add an option to provide a code signing certificate for the generated scripts from CMPivot
In our organization only signed scripts may be executed on the clients. However, the scripts from CMPivot queries are not signed and are therefore not executed. This restriction is set by GPO and cannot be overridden by "PowerShell execution policy" in the SCCM client computer agent.
Anonymous
shared this idea
6 comments
-
Anonymous
commented
any further information on when this will be included?
-
Paul K (TCC)
commented
what version is this part of?
-
Paul K (TCC)
commented
We have the same issue. CMPivot doesn't work due to policy set to require signed scripts. ( same as the issue with W10 diags all being unsigned scripts so they never report any problems)
Some sort of workaround to enable CMPivot would be nice. -
Sara Barkley
commented
Same issue here. Domain policy set to All Signed. CMPivot completely nonfunctional, returns status "Unsupported PowerShell Version" except for the handful if devices that have exception to the policy.
-
Paul K (TCC)
commented
We have the same issue. CMPivot is non-functional as we have powershell execution policy at all signed site wide.
-
Anonymous
commented
We are running into this problem also. Our execution policy is predominately AllSigned for our servers and thus CMPivot queries will not execute, returning an error message of "Unsupported PowerShell Version". This is happening on servers with PowerShell 5.1 installed (Server 2008 R2, Server 2012 R2, Server 2016 and Server 2019). When I change the execution policy to RemoteSigned (we have some exceptions we allow) on a test server, then CMPivot queries succeed.