Hey everyone, I've got a situation where we're deploying scripts with a system that usually works well, as long as we start with "Set-ExecutionPolicy Bypass." But now, at one location, all servers are giving me this error when I try to run my scripts, except for the Domain Controller, which is strange. The error message states that the script isn't digitally signed, and it seems like no matter what execution policy I use, I can't get around this issue. I've tried setting different execution policies like Bypass, Undefined, and RemoteSigned, but nothing seems to work. I'm wondering if there's a specific Group Policy or registry setting causing this problem, but my search hasn't turned up much. I'd appreciate any insights or suggestions you might have!
1 Answer
It sounds like there might be a Group Policy setting that's enforcing script execution rules. Check under Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell and see if the 'Turn on Script Execution' policy is active. If it's set to allow only signed scripts, that could be causing the issue you're experiencing. Remember, this could come from either Local or Domain Group Policy, so using GPResult could help identify if that's the case.
Thanks for the tip! I ran gpresult for the domain, but it didn’t show any configured policies. I also checked with mmc.exe on the local side, and nothing popped up there either. Pretty frustrating!