CODEWITHSUNDEEP
powershellpowershell-4.0remote-execution
A.Kazemi
A.Kazemi

Reputation: 13

Remote Execution of a PowerShell script results in "The WinRM client cannot process the request. [...] HTTPS transport must be used [...]"

I have written a PowerShell script which uninstall a program and install a newer version of the program on my servers (Update Programs). Now I want to create another script which run the aforementioned script on the servers. Consider that I have to connect to my servers through using IPs, UserName and password and using domain is not an option.

How is this possible?

PowerShell version is 4

I have tried this code to simply get date:

$User = "administrator"
$PWord = ConvertTo-SecureString -String "Password1234" -AsPlainText -Force
$Credential = New-Object -TypeName "System.Management.Automation.PSCredential" -ArgumentList $User, $PWord
$session = New-PSSession -ComputerName '10.60.60.100' -Credential $Credential
Invoke-Command -Session $session -ScriptBlock {Get-Date}

and I got this error:

New-PSSession : [10.60.60.100] Connecting to remote server 10.60.60.100 failed with the following error message : The WinRM client cannot process the request. If the authentication scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. You can get more information about that by running the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.

Upvotes: 0

Views: 6322

Answers (1)

Bryce McDonald
Bryce McDonald

Reputation: 1870

This is because you’re not running your command from a trusted host, or because the remote computers wsman service isn’t configured properly. I’d start by running the following command to configure wsman on the remote machine:

wsman quickconfig

If that doesn’t fix the problem, then you need to add your computer to the remote machines trusted hosts. You can do that by running the following:

winrm s winrm/config/client '@{TrustedHosts="RemoteComputer"}'

Upvotes: 2

Related Questions