powershell remoting Win2008R2 "The WSMan service could not launch a host process to process the given request"

powershell windows-server-2008 powershell-2.0 powershell-remoting
richard wadsworth picture richard wadsworth · Jan 5, 2012 · Viewed 13.1k times · Source

I've recently upgraded a number of servers from 2003 to 2008R2. Since the upgrade I've started to see the following error:

[servername] Connecting to remote server failed with the following error message : The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server and proxy are properly registered. For more information, see the about_Remote_Troubleshooting Help topic.

The error is seemingly random. The script will work and then fail. The command to create the session is in a loop (create session, remove session) and is called numerous times as part of a set of deployment scripts. When the script fails, it fails at different points.

I've checked the event log on the local workstation (win7) destination server (win2008R2) but there are no errors that I can see.

This is the lines that randomly fails:

$session = New-PSSession -ComputerName $serverName -Credential $credential

I did not see this issue on Win2003. The scripts have not changed. I'm assuming the problem is on the destination server but cannot find any errors or logs to look at. It will work once and then fail so my deployment scripts will sometimes succeed and then fail at different points.

Any guidance on tracking down this problem would be much appreciated.

Answer

IT M picture IT M · Apr 6, 2020

You need to be setting the WSMan TrustedHosts. If you want, you can set it to everything using wildcards (*).

You can do it via PowerShell: Set-Item WSMan:\localhost\Client\TrustedHosts -Value *.

Keep in mind that you also need to enable the Windows Remote service. Use the native winrm qc command for this. Enable-PSRemoting -Force might do it as well.

You can also use the PSExec Tools from Sysinternals. Keep in mind that these tools will likely be blocked by your EndPoint Security, so don't forget to white list it.

Is there a specific reason you migrate your old OSes to a newer, but still EOL OS? You can do a lot via PowerShell in 2008R2, but it's still pretty limited. IMO, Using PowerShell is best starting from 2012R2 and onwards.

Related questions

Create directory if it does not exist

I am writing a PowerShell script to create several directories if they do not exist. The filesystem looks similar to this D:\ D:\TopDirec\SubDirec\Project1\Revision1\Reports\ D:\TopDirec\SubDirec\Project2\Revision1\ D:\TopDirec\SubDirec\Project3\Revision1\ Each project …

Read More
Multiple -and -or in PowerShell Where-Object statement

PS H:\> Invoke-Command -computername SERVERNAME { Get-ChildItem -path E:\dfsroots\datastore2\public} | Where-Object {{ $_.e xtension-match "xls" -or $_.extension-match "xlk" } -and { $_.creationtime -ge "06/01/2014"}} Above is my code example. I'm trying to remotely run this PowerShell code on my file server and …

Read More
Extracting columns from text file using PowerShell

I have to extract columns from a text file explained in this post: Extracting columns from text file using Perl one-liner: similar to Unix cut but I have to do this also in a Windows Server 2008 which does not have …

Read More