2 Replies Latest reply on Apr 2, 2020 4:40 AM by rmrunal

    Set-ExecutionPolicy not persistent on win2k12

    rmrunal Novice


      I have set Execution policy to RemoteSigned for LocalMachine as well as CurrentUser scope. However when my application is running powercli commands using sdk, I am getting following error -

      "File C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\VMware.VimAutomation.Sdk.psm1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170."

      1) OS - Windows Server 2012 Standard

      2) PowerShell Version -


      Major  Minor  Build  Revision
      -----  -----  -----  --------
      3      0      -1     -1

      Major  Minor  Build  Revision

      -----  -----  -----  --------

      3      0      -1     -1

      Also tried by upgrading Powershell version to 5.1. It throws same error.

      3) Get-PowerCLIVersion

      PowerCLI Version


         VMware PowerCLI 11.5.0 build 14912921


      Component Versions


         VMware Common PowerCLI Component 11.5 build 14898112

         VMware Cis Core PowerCLI Component PowerCLI Component 11.5 build 14898113

         VMware VimAutomation VICore Commands PowerCLI Component PowerCLI Component 11.5 build 14899560


      Then I tried doing this setting in code for each connection I make, I don't see the error then.

      Since the setting is global, want to avoid it setting through code. Any clue to why the natively done setting is not persistent through multiple sessions?

      Thanks in advance.