I have been using the Windows Scripting Driver to run Exchange 2010
commands in the ScriptService for over a year now. I tried upgrading to
Scripting Driver so that I can use PowerShell 3. I know that
Exchange 2010 and Powershell 3 are not supported, but I thought I would
try to take a stab at getting the new Script Service to work. I
initially ran into an issue with RemoteExchange.ps1 throwing this

Exception calling "TryLoadExchangeTypes" with "2" argument(s): "Mixed
mode assembly is built against version 'v2.0.50727' of the runtime and
cannot be loaded in the 4.0 runtime without additional configuration

After some research I found http://tinyurl.com/p5nnt2p, for which I
created ScriptService.exe.config in the same directory with the

<?xml version="1.0"?>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>

It appears to be working now, but my question is for the more seasoned
..Net framework people, is there any harm with doing this for either the
Script Service or for the Exchange 2010 remote management tools?

Thank you in advance

schwoerb's Profile: https://forums.netiq.com/member.php?userid=2338
View this thread: https://forums.netiq.com/showthread.php?t=48953