Working on a Server Info script that will first test the connection of a remote server, if successful it will run Test-WSMAN and pull the stack version and if 2012 + will use default WSMAN during New-CimSession. If it does not meet minimum then it goes to another Try where a New-CimSession is created using -SessionOption DCOM This is for the older servers still in use where PowerShell may not be loaded at all.
This has been working for the last 4 weeks and today around 11:30 CST using WSMAN on the 2012 + Servers all came to a halt.
Contacted Networking who said Nothing is going on and IF there was any change it would be after hours not during the work day.
Server Support said the same thing. Of course nothing (supposedly) has changed but regardless of where the scripts are run they will no longer connect using WSMAN. Then I started getting reports that PSSession has also stopped working causing more phone calls.
“The WinRM client cannot process the request it cannot determine the content type of the http”
Test-WSMAN -Computername Server works ok against target servers.
I CAN force DCOM on the same servers and that will connect…
I am going to start troubleshooting when I get back in the morning checking:
Target Server Open Ports& test ports from Local PC
WinRM Services Running (which when prev checked has always been ok)
test-wsman -computername server01 -authentication default etc…
The WIN Firewall is not used however a 3rd party one is and Im leaning toward it being the culprit.
If anyone has any other suggestions I will be more then happy to take each into consideration.