Differences with Enter-PSSession

When using pypsrp to start a session, there are some different to a session started with Enter-PSSession.

For example, using the Set-PSDebug or Trace-Command cmdlets seems to have no effect. And similarly, output from a script in a JEA role capabilities file configured using ScriptsToProcess does not come through to any of the session streams – such as the output from Write-Host "Hello world".

Is this a scoping issue or some other session configuration option that I have overlooked?

[malthe]

I figured out how to make it work:

ps.add_cmdlet("Set-PSDebug").add_parameter("Trace", 1)
ps.add_cmdlet("Invoke-Job1")

That is, the equivalent of Set-PSDebug -Trace 1 | Invoke-Job1.

If I use ps.add_statement() before the second cmdlet, it stops working – I’m thinking that must be a scoping issue.

[jborean93]

That’s interesting that you couldn’t have it span across statements as essentially the add_script example in mine was doing the same thing… It sounds like you’ve got a decent workaround and the problem was on the server side not respective the setting in the previous statement.