WinRM issues

Jonathan.Engstrom

So I am thinking I may have spn issues, and am not able to attempt some of the fixes, so I am stuck with adding a separate setspn to deal with just deal with this. Agent installs are not an option. My question is can Otter utilize session options in WinRM? Example I sound on technet:

As I have seen in this link:

https://www.reddit.com/r/PowerShell/comments/3ze9pp/cannot_use_powershell_remoting_when_a_http_spn/

You can create a port specific spn:

SetSPN.exe -s HTTP/$($env:COMPUTERNAME):5985 $env:COMPUTERNAME 
SetSPN.exe -s HTTP/$($env:COMPUTERNAME).$($env:USERDNSDOMAIN):5985 $env:COMPUTERNAME

and then create a session using an option:

# Create and use session
$sessionOptions = New-PSSessionOption -IncludePortInSPN
Enter-PSSession -Computername <computername> -SessionOption $sessionOptions

Product: Otter
Version: 2.2.0-beta.4

Setting "Session Options" currently isn't supported with the Powershell-based agent. But we will definitely consider it if you could put together a feature request.

I have no idea if it's easy/possible, but any insight into what other session options might be helpful could be nice.

Jonathan.Engstrom

Has there been any update to this?

atripp

There haven't been any other feature requests for this, and we haven't researched the feasibility of doing it; however we did add Impersonation and Process Isolation, both which were in-demand features.