Reply To: Execution of scripts is disabled on this system.

  • Topaz George

    Organizer
    15 July 2020 at 8:45 am
    • You can do the either one of the following.
     Set-ExecutionPolicy unrestricted

    or execute the script using the following command.

    powershell.exe -noprofile -executionpolicy bypass -file .\getcal.ps1

    The acceptable execution policy values are as follows:

    • AllSigned : Requires that all scripts and configuration files are signed by a trusted publisher, including scripts written on the local computer.
    • Bypass : Nothing is blocked and there are no warnings or prompts.
    • Default : Sets the default execution policy. Restricted for Windows clients or RemoteSigned for Windows servers.
    • RemoteSigned : Requires that all scripts and configuration files downloaded from the Internet are signed by a trusted publisher. The default execution policy for Windows server computers.
    • Restricted : Doesn’t load configuration files or run scripts. The default execution policy Windows client computers.
    • Undefined : No execution policy is set for the scope. Removes an assigned execution policy from a scope that is not set by a Group Policy. If the execution policy in all scopes is Undefined, the effective execution policy is Restricted.
    • Unrestricted : Beginning in PowerShell 6.0, this is the default execution policy for non-Windows computers and can’t be changed. Loads all configuration files and runs all scripts. If you run an unsigned script that was downloaded from the internet, you’re prompted for permission before it runs.

    Source => https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-7

    • This reply was modified 3 years, 8 months ago by  Topaz George.

DCOM hardening issue.

This application fails to authenticate with WMI on the SCCM server because Microsoft has not yet hardened DCOM on their Windows Preinstallation Environment. We are working on a different approach, but it will only be released during the first quarter of 2024. But until that time, the only workaround will be to uninstall the update corresponding to KB5004442.