MicrosoftMartin_Wildi
The Windows PowerShell Script Execution Policy ist not a security measurement, it's purely a safety net to not execute "foreign" scripts by mistake.
Any batch script can bypass the Execution Policy and then execute a Powershell script.
So no joke. MS just knows that many Exchange servers are prohibited to check signatures and then installations will fail.
There is no harm done whatsoever in setting the Execution Policy to Unrestricted and there is no need to sign them by Microsoft.
The only one that should sign is yourself, so when you run scripts (manual, task scheduler), you know that these are scripts for productions.
