PowerShell in GUI - Remove AllSigned or Digitally Sign the Module
When running the PowerShell Cmdlets from within the GUI in System Center Configuration Manager it forces a confirm before it allows the Console to run. The problem is simple as the Console is being run with "allsigned" as the executionPolicy but the Module is NOT Digitially signed. Change the launching ExecutionPolicy to Bypass or Digitally Sign the Module (either would resolve the issue)
Unfortunately there’s not enough actionable information provided here for us at this time.
All of our PowerShell modules should be signed. You may initially receive a prompt to accept the signer of the modules, but beyond that they should function as expected in AllSigned mode.
If you’re not seeing this, please let us know the exact error you’re seeing along with the product version you’re using so we can dig deeper into this issue.
AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) commented
I'm not sure I understand the problem. All of our PowerShell modules are signed. Are you referring to the initial notification that appears asking you to trust the signer of the certificate or are you referring to something else?
Can you provide a screen shot demonstrating what you're seeing?