Otter - Win2012 R2 computer can't access remote

I just installed Otter onto a fresh non-domain joined Win2012 R2 server.

The otter server is using IIS 8.5 with SQL Server 2012 Standard. I've installed all the prerequisites, and the installation itself completed fine.

However, I then installed an agent onto another Win2012 R2 server (Otter 1.0.0 agent) that's also not joined to a domain and then attempted a test to do a simple host file modification using Otter's built-in tool for Ensure Host File Entry.

I've verified the target server has .net 4.5 installed, and the firewall is fully disabled on both the Otter Server and the target server. These servers have no other software installed on them (no av, no other applications, etc).

I get the following error when the Otter server tries to modify the remote server:

Unhandled exception: System.NotSupportedException: The TcpAgent agent does not support the IRemoteMethodExecuter interface.
at Inedo.Otter.Extensibility.Agents.OtterAgent.GetServiceTService
at Inedo.Otter.Extensions.Operations.Network.EnsureHostsEntryOperation.<CollectAsync>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()

I'd really like to use Otter, but this makes me believe remote management doesn't work in Win2012 R2 and we have a very heavy Win2012 R2 environment.
at Inedo.Otter.PlanExecuter.OtterPlanExecuterBase.<PerformCollection>d__40.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.Otter.PlanExecuter.OtterPlanExecuterBase.<Inedo-ExecutionEngine-Executer-IExecutionHostEnvironment-ExecuteActionAsync>d__39.MoveNext()

Hi James, that is most definitely a bug with that particular operation, the configuration you describe should definitely be supported.

We'll get it a new version out pronto!

This issue has been resolved in Otter 1.0.1, now available for download at http://inedo.com/otter/download.

Awesome!!

Thanks guys!!