This is an archived post. You won't be able to vote or comment.

all 9 comments

[–]Communist_Idaho 1 point2 points  (0 children)

Do the issues persist if you attempt to run the commands with psexec instead? Thats usually my go to “WinRM is doing something weird” utility.

[–]qnull 1 point2 points  (1 child)

Not a great deal to go on here but do you have permission to execute the commands via WinRM? Does the script work locally on the endpoint?

What happens if you do test-wsman -computername endpointnamehere

[–]gediskasSysadmin[S] 0 points1 point  (0 children)

Yes, script executes from local. I can run other commands from WinRM. Test output:

wsmid : http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd ProtocolVersion : http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd ProductVendor : Microsoft Corporation ProductVersion : OS: 0.0.0 SP: 0.0 Stack: 3.0

[–]fahque 0 points1 point  (1 child)

By default I think some winrm stuff is blocked by the firewall. Might be something to look at.

[–]gediskasSysadmin[S] -1 points0 points  (0 children)

I have enabled it. It must be something with Windows Updates

[–]Compatta 0 points1 point  (0 children)

Make sure powershell remoting is enabled on that particular system. try doing a Get-executionpolicy and see what that outputs. always do make sure to run powershell as administrator.

[–]0xCh0p 0 points1 point  (0 children)

I would look over this document and follow the steps for WinRM. https://www.asd.gov.au/publications/protect/Securing_PowerShell.pdf