Add detail to error message that Disconnect is only supported with WSMan#6689
Conversation
| </data> | ||
| <data name="DisconnectNotSupportedOnServer" xml:space="preserve"> | ||
| <value>The disconnection operation is not supported on the remote computer. To support disconnecting, the remote computer must be running Windows PowerShell 3.0 or a later version of Windows PowerShell.</value> | ||
| <value>The disconnection operation is not supported on the remote computer. To support disconnecting, the remote computer must be running Windows PowerShell 3.0 or a later version of Windows PowerShell and using the WSMan transport.</value> |
There was a problem hiding this comment.
From the message I understand nothing that I should do.
Maybe simply say "The disconnection operation is not supported for SSH sessions."
There was a problem hiding this comment.
It's also not supported for named pipes and PowerShell Direct remoting. The doc update I linked in the PR description should hopefully make this more clear.
|
@SteveL-MSFT Is the PR really fix #5313? Maybe not close the Issue? |
|
@iSazonov there's no immediate plan to support Connect/Disconnect with anything other than WSMan. I've submitted some doc updates to reflect this. Longer term, we will want to support this scenario. However, on Linux/macOS, you would use |
PR Summary
If you use
Disconnect-PSSessionwith a PSSession using any transport other than WSMan, the error message doesn't give enough details why it failed. Fix is to specify that this capability is only supported with WSMan.Fix #5313
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:to the beginning of the title and remove the prefix when the PR is ready.[feature]if the change is significant or affects feature tests