I have the latest scripting driver & scripting driver service up and running.
But for some reason I cannot load the Exchange commandlets with 'RemoteExchange.ps1'.

As a workaround I still use the deprecated 'Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn' command.
This works well (Exchange provisioning works flawlessly) and makes believe that the general service combo driver/service is setup properly.

My current setup:
IDM 4.6SP1
Exchange 2016
scripting driver running as local system user on Exchange 2016 server
Script command running as local system user on same Exchange 2016 server
IDM Exchange driver appears to be correct and 'bin\scriptclient.exe' is executed.

-address localhost:8198
-command . "C:\Program Files\Novell\WSDriver\scripts\powershell\scriptser vice.ps1"

"C:\Program Files\Novell\WSDriver\scripts\powershell\scriptser vice.ps1"
Get-Date > c:\Windows\Temp\test.txt

. "C:\Program Files\Microsoft\Exchange Server\V15\Bin\RemoteExchange.ps1"

Get-Date >> c:\Windows\Temp\test.txt

# Workaround, since above RemoteExchange.ps1 does not work, script appears to stop here (only one timestamp in the test file)
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn

Get-Date >> c:\Windows\Temp\test.txt

Connect-ExchangeServer -auto -ClientApplication:ManagementShell

Get-Date >> c:\Windows\Temp\test.txt

What am I missing?

What is the recommended setup?
- under what account should I execute the scripting driver (local system vs. local user vs. AD user)
- under what account should I run the scripting service (local system vs. local user vs. AD user)

What else should I check?