{"id":5014,"date":"2016-05-27T09:04:00","date_gmt":"2016-05-27T13:04:00","guid":{"rendered":"http:\/\/jdhitsolutions.com\/blog\/?p=5014"},"modified":"2016-06-08T07:50:32","modified_gmt":"2016-06-08T11:50:32","slug":"friday-fun-a-better-test-wsman","status":"publish","type":"post","link":"https:\/\/jdhitsolutions.com\/blog\/powershell\/5014\/friday-fun-a-better-test-wsman\/","title":{"rendered":"Friday Fun: A Better Test-WsMan"},"content":{"rendered":"

I saw a question on Facebook about how to get Test-WsMan<\/a> to return a simple Boolean result. The Test-Connection<\/a> cmdlet has a -Quiet parameter that makes this possible. But Test-Wsman does not.\u00a0 Certainly, you could script a comparable outcome. Here's one way:<\/p>\n

\"chi-hvr2\",\"chi-hvr1\",\"chi-p50\" | foreach {\r\n  $r = Test-WSMan $_ -ErrorAction SilentlyContinue\r\n  if ($r) {\r\n    $True\r\n  }\r\n  else {\r\n    $False\r\n   }\r\n  }<\/pre>\n
Or, if all you want is to simply filter a list of names you could use an expression like this:<\/p>\n
\"chi-hvr2\",\"chi-hvr1\",\"chi-p50\" | Where { test-wsman $_ -ErrorAction SilentlyContinue}<\/pre>\n
The only names that come out the end will be those that responded to Test-WsMan. Or you can go another way and create your own version of Test-WsMan which is what I did.<\/p>\n
I used my Copy-Command script<\/a> to create a wrapper function I named Test-MyWsMan.\u00a0 I added a parameter called -Quiet so that the command behaves like Test-Connection.\u00a0 While I was at it, I also addressed some other shortcomings (for me at least) in Test-WsMan. When testing multiple computers, not having a computername property meant the results weren't that useful. And you could only get values in the ProductVersion property if you specified an Authentication parameter value. So I fixed these \"issues\".<\/p>\n
You can find my new command on as a gist in GitHub.<\/p>\n