{"id":4173,"date":"2013-02-12T00:01:00","date_gmt":"2013-02-12T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2013\/02\/12\/learn-how-to-easily-troubleshoot-powershell-remoting\/"},"modified":"2013-02-12T00:01:00","modified_gmt":"2013-02-12T00:01:00","slug":"learn-how-to-easily-troubleshoot-powershell-remoting","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/learn-how-to-easily-troubleshoot-powershell-remoting\/","title":{"rendered":"Learn How to Easily Troubleshoot PowerShell Remoting"},"content":{"rendered":"

Summary:<\/strong> Microsoft Scripting Guy, Ed Wilson, shows you how to easily troubleshoot Windows PowerShell remoting.<\/span><\/p>\n

\"Hey, Hey, Scripting Guy! I have a problem. I am running Windows 8 on my desktop, and I have upgraded our Hyper-V servers to Windows Server 2012. For those computers, I can easily use Windows PowerShell remoting and I have not seen a single problem. But when I attempt to connect to our servers running Windows Server 2008 R2, and even the Windows Server 2008 servers, then it seems to be hit or miss. I need an easy way to troubleshoot this without doing a lot of special logging and going all extreme. Can you help?<\/p>\n

—KG<\/p>\n

\"Hey, Hello KG,<\/p>\n

Microsoft Scripting Guy, Ed Wilson, is here. Well, today I am all in a dither (or a tither, not sure which). I just got a picture of Dr. Scripto through the email—no, no one has kidnapped him (á la Who’s Harry Crumb<\/a>), no, the picture is from my friend Kurt Hudson, who is a senior technical writer on the Information Experience team. You see, he and I were in meetings together a few weeks ago when I was in Redmond, and he mentioned his hobby—welding. I suggested he might try to weld a figure of Dr. Scripto—he not only accepted the challenge, as you can see in the image here, he excelled.<\/p>\n

\"Image<\/a><\/p>\n

Well, KG, as it turns out, I was reviewing a chapter from my Windows PowerShell 3.0 First Steps<\/a> book by Microsoft Press, and it seems that is the best way for me to answer your question—without the need to reinvent the wheel.<\/p>\n

So, here goes …<\/p>\n

Troubleshooting Windows PowerShell Remoting<\/h2>\n

The first tool to use to see if Windows PowerShell remoting is working (or not) is the Test-WSMan<\/strong> cmdlet. Use it first on the local computer (no parameters are required). The command and its associated output are shown here.<\/p>\n

PS C:\\> Test-WSMan<\/p>\n

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<\/p>\n

To test a remote computer, specify the –ComputerName<\/strong> <\/em>parameter. This following command runs against a Windows Server 2012 domain controller named DC3.<\/p>\n

PS C:\\> Test-WSMan -ComputerName dc3<\/p>\n

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<\/p>\n

But the Test-WSMan<\/strong> cmdlet also works against a computer running Windows PowerShell 2.0. The following command runs against a Windows Server 2008 domain controller named DC1.<\/p>\n

PS C:\\> Test-WSMan -ComputerName dc1<\/p>\n

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: 2.0<\/p>\n

To examine a specific Windows PowerShell session, use the Get-PSSession<\/strong> cmdlet. The easiest way to do this is to pipe the variable containing the Windows PowerShell session to the Get-PSSession<\/strong> cmdlet. The key items to pay attention to are the computer name, the state of the session, and the availability of the session. This technique is shown here.<\/p>\n

PS C:\\> $ps | Get-PSSession<\/p>\n

 Id Name            ComputerName    State         ConfigurationName     Availability
 — —-            ————    —–         —————–     ————
  3 Session3        ex1             Opened        Microsoft.PowerShell     Available
  4 Session4        dc3             Opened        Microsoft.PowerShell     Available<\/p>\n

To focus on a specific session, reference the session by either ID or by Name. Send the returned session object over the pipeline to the Format-List<\/strong> cmdlet and select all of the properties. This technique is shown here (using fl<\/strong> as an alias for the Format-List<\/strong> cmdlet).<\/p>\n

PS C:\\> Get-PSSession -Name Session4 | fl *<\/p>\n

State                  : Opened
IdleTimeout            : 7200000
OutputBufferingMode    : None
ComputerName           : dc3
ConfigurationName      : Microsoft.PowerShell
InstanceId             : c15cc80d-64f0-4096-a010-0211f0188aec
Id                     : 4
Name                   : Session4
Availability           : Available
ApplicationPrivateData : {PSVersionTable}
Runspace               : System.Management.Automation.RemoteRunspace<\/p>\n

You can remove a remote Windows PowerShell session by piping the results of Get-PSSession<\/strong> to the Remove-PSSession<\/strong> cmdlet. This technique is shown here.<\/p>\n

Get-PSSession -Name Session4 | Remove-PSSession<\/p>\n

You can also remove a PS session directly by specifying the name to the Remove-PSSession<\/strong> cmdlet. This technique is shown here.<\/p>\n

Remove-PSSession -Name session3<\/p>\n

KG, that is all there is to using the built-in Windows PowerShell cmdlets to troubleshooting remoting. Join me tomorrow for the exciting conclusion to Microsoft MVP and honorary Scripting Guy Richard Siddaway’s workflow series.<\/p>\n

I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

Ed Wilson, Microsoft Scripting Guy<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Microsoft Scripting Guy, Ed Wilson, shows you how to easily troubleshoot Windows PowerShell remoting.  Hey, Scripting Guy! I have a problem. I am running Windows 8 on my desktop, and I have upgraded our Hyper-V servers to Windows Server 2012. For those computers, I can easily use Windows PowerShell remoting and I have not seen a […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[57,3,4,45],"class_list":["post-4173","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-remoting","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell"],"acf":[],"blog_post_summary":"

Summary: Microsoft Scripting Guy, Ed Wilson, shows you how to easily troubleshoot Windows PowerShell remoting.  Hey, Scripting Guy! I have a problem. I am running Windows 8 on my desktop, and I have upgraded our Hyper-V servers to Windows Server 2012. For those computers, I can easily use Windows PowerShell remoting and I have not seen a […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/4173","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=4173"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/4173\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=4173"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=4173"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=4173"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}