Question

I have successfully connected to a remote powershell session through WinRM. It works like a charm. Problem begins when I try to import a module which uses an assembly built for .NET framework 4.

When working locally had the same problem but was easily solved by adjusting the app.config of powershell.exe. Tried doing the same on remote host but it doesn’t work. I guess WinRM has it’s own runspace that isn’t related to powershell.exe.

Is there a way to configure WinRM so that it runs under .NET 4?

Answer 1

Try creating a c:\windows\System32\wsmprovhost.exe.config file and a c:\windows\SysWOW64\wsmprovhost.exe.config file in 64bit OS like this:

<?xml version="1.0"?>
<configuration>
    <startup useLegacyV2RuntimeActivationPolicy="true">
         <supportedRuntime version="v4.0.30319"/>        
         <supportedRuntime version="v2.0.50727"/>        
    </startup>
</configuration>