We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After running a CLI WinRM session, the WinRM session still appears to persist on the guest machine.
If you review the running processes after each invocation, you'll note that the number of 'winrs.exe' processes linearly increases.
You can test this behaviour with the winrm CLI itself: winrm "powershell -command \"\$(Get-Process | select-string -Pattern winr | group).Count\"".
winrm
winrm "powershell -command \"\$(Get-Process | select-string -Pattern winr | group).Count\"".
The text was updated successfully, but these errors were encountered:
No branches or pull requests
After running a CLI WinRM session, the WinRM session still appears to persist on the guest machine.
If you review the running processes after each invocation, you'll note that the number of 'winrs.exe' processes linearly increases.
You can test this behaviour with the
winrmCLI itself:winrm "powershell -command \"\$(Get-Process | select-string -Pattern winr | group).Count\"".The text was updated successfully, but these errors were encountered: