Click here to review the steps for the workaround.

This workaround is necessary because the Windows Server 2012 environment runs with .NET 2.0 version, while the DLLs in SCVMM 2012 SP1 and later are built with a newer .NET framework 4.0. The workaround is as follows: 

1. Create powershell.exe.config with the following:

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

   Note

   For a 64-bit OS you might want to create a similar powershell.exe.config file in the following location:

   C:\windows\syswow64\windowspowershell\v1.0

2. Copy the file into the powershell root directory: C:\Windows\System32\WindowsPowerShell\v1.0.
   For a 64-bit OS, create a similar powershell.exe.config file in the C:\Windows\SysWOW64\WindowsPowerShell\v1.0.

3. Run following from the command line:

   reg add hklm\software\microsoft\.netframework /v OnlyUseLatestCLR /t REG_DWORD /d 1
   reg add hklm\software\wow6432node\microsoft\.netframework /v OnlyUseLatestCLR /t REG_DWORD /d 1