Unable to connect to the server using windows powershell remoting

RDS: Unable to connect to the server by using Windows Powershell Remoting

Scenario

You are trying install RDS 2012 R2 (no matter quick or standard mode) and get error during compatibility check:

Unable to connect to the server by using Windows PowerShell remoting.

  • Server is joined to domain
  • Server is running on 2012 R2 up-to-date
  • Current user is a member of group “Administrators” (lusrmgr.msc -> groups)
  • PowerShell is configured to receive remote queries (Enable-PSRemoting)
  • Remote Desktop Services are not forbidden in GPOs (default policies)
  • Remote management is enabled in Server Manager (servermanager -> local server -> remote management)
  • Firewall rules for remote management are enabled (Get-NetFirewallRule *winmgmt*|select name,enabled)
  • There are no network and time synchronization issues between this server and my environment

Solution

If you ping server you may notice IPv6 name format (in my case). Windows Server management consoles don’t like it in my case (any thoughts/comments?). So turn off IPv6 (if you are not using it) on your network adapter. I think unchecked “register this connection in the DNS”, ipconfig /flushdns work too. But did no try.

I had a lot of VDI deployments but faced with this problem for the first time.

Note: same issue was with Active Directory mmc. There was the wrong status of Domain Controller in “change domain controller..” (was Offline). Turning IPv6 ON resolved this behavior. Agruments against disabling IPv6

Share this:

Like this:

11 thoughts on “RDS: Unable to connect to the server by using Windows Powershell Remoting”

Thank you very much! your post helped me to solve my issue. I was configuring a RDS server on a Azure VM , to proceed some tests regarding internal/External access, and got this error right on the first step of my tests. I researched on a bounch of sites, but just the steps described here helped me to solve my problem! If you dont mind, I will create a new post in my natual language (PORTUGUÊS – Brazil) replying the steps that you mentioned here, and keeping your blog URL as reference.

This worked for me, I also uninstalled a network adapter that was no longer in use which may have been causing the issue.

Читайте также:  Линукс это хороший windows

Nice to hear that! Thanks for your feedback.

Unable to connect to the server using windows powershell remoting

Вопрос

We are trying to install RDS on one of the server OS 2016. But facing below error

Unable to connect to the server by using Windows Powershell Remoting

— We are installing all RDS Role on the same server, there is no remote server involve in it.

Did below troubleshooting but still issue persist .

— We ran below command but no luck.

Enable-PSRemoting -force
Set-Item WSMan:localhostShellMaxMemoryPerShellMB 1000

— Disable windows firewall

Ran «Set-ExecutionPolicy -ExecutionPolicy RemoteSigned»

Ran «Set-ExecutionPolicy -ExecutionPolicy UnRestricted»

— Further we tried to install the RDS from DC but when we tried to add the server **3 in server manager group it shows below error.

Error **3 : Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: «winrm quickconfig». 7/19/2017 5:03:36 AM

— We provide local admin rights to user «helpdesk» but no result.

Unable to connect to the server by using Windows Powershell Remoting

Situation: When attempting to add licensing server in Windows 2012 R2 RS service, you may get this message: Unable to connect to the server by using Windows Powershell Remoting.

We fix the problem. It is Environment Variables. Search online, we find some people have the similar case. Changing the path from %systemroot% to c:\windows and that fixed the problem.

In our case, chaging from PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Millennium 3;C:\Program Files (x86)\Microsoft Office\Office16;C:\Bat;

to
C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Millennium 3;C:\Program Files (x86)\Microsoft Office\Office16;C:\Bat;

Note: without PATH= fixes the problem.

1. Disable IPv6 for a test.

2. Run Powershell, run this command: Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000

Then restart the server.

3. It could be the firewall issue. disable the Windows firewall or add ‘Windows Remote Management’ rule to my firewall.

4. clearing the proxy by running this command: netsh winhttp reset proxy

5. Compatibility problem when installing Remote desktop services role on 2012 “Unable to connect to the server by using Windows Powershell Remoting”

Читайте также:  Рейтинг vds серверов с windows

6. “Enable-PSRemoting -force” worked for me.

7. Solved the issue – DC and RDS server had 3 hour time difference. Syncing time worked.

8. If you want to add TS licensing service, add Server role. If you want to add this server under RDS licensing server to receive the RD CALs, go to Deployment.

9. had same issue fixed it by clearing the proxy

netsh winhttp reset proxy

10. Domain admin can’t seem to do anything so added another admin account (with local admin rights) then running the RDS Deployment from an elevated Server Manager session did the trick for me.

11. The solution was to increase the MaxFieldLength and MaxRequestBytes keys in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters

If the keys does not exists you can create them, be sure to use the DWORD type.

I sat MaxFieldLength to DEC value 40000 and MaxRequestBytes to DEC value 32768 and rebooted the server. Problem solved.

12. Solved the issue – DC and RDS server had 3 hour time difference. Syncing time worked.

13. My systems engineer found that my issue was caused by a System variable that was set incorrectly. The Path variable had been cleared, which was keeping Powershell Remoting from working correctly. He copied the variables from another server, and it is nowworking correctly.

14. If there is a GPO setting on the network that affects the server you are trying to install RDS on and that GPO controls WinRM listening ports and is incorrectly configured then you will get this error.

Run winrm enumerate winrm/config/listener on the target server and if ListeningOn = null is returned then check GPO on this box with gpresult /h result.html & result.html. Search this GPO output for Windows Components/Windows RemoteManagement (WinRM)/WinRM Service and IPv4 Filter and IPv6 Filter need to contain * or an IP range that includes this server. If the value is blank or wrong IP range then you will get the original posters error message!

15. In Server Manager/Remote Management was already enabled. My fix was to disable and then re-enable Remote Management. I was then able to reinstall RDS.

16. use “net time /domain:*** /set” and problem fixed.

Unable to connect to the server using windows powershell remoting

Вопрос

We are trying to install RDS on one of the server OS 2016. But facing below error

Unable to connect to the server by using Windows Powershell Remoting

— We are installing all RDS Role on the same server, there is no remote server involve in it.

Читайте также:  Фикс мыши windows 10

Did below troubleshooting but still issue persist .

— We ran below command but no luck.

Enable-PSRemoting -force
Set-Item WSMan:localhostShellMaxMemoryPerShellMB 1000

— Disable windows firewall

Ran «Set-ExecutionPolicy -ExecutionPolicy RemoteSigned»

Ran «Set-ExecutionPolicy -ExecutionPolicy UnRestricted»

— Further we tried to install the RDS from DC but when we tried to add the server **3 in server manager group it shows below error.

Error **3 : Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: «winrm quickconfig». 7/19/2017 5:03:36 AM

— We provide local admin rights to user «helpdesk» but no result.

Unable to connect to the server using windows powershell remoting

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

We are trying to install RDS on one of the server OS 2016. But facing below error

Unable to connect to the server by using Windows Powershell Remoting

— We are installing all RDS Role on the same server, there is no remote server involve in it.

Did below troubleshooting but still issue persist .

— We ran below command but no luck.

Enable-PSRemoting -force
Set-Item WSMan:localhostShellMaxMemoryPerShellMB 1000

— Disable windows firewall

Ran «Set-ExecutionPolicy -ExecutionPolicy RemoteSigned»

Ran «Set-ExecutionPolicy -ExecutionPolicy UnRestricted»

— Further we tried to install the RDS from DC but when we tried to add the server **3 in server manager group it shows below error.

Error **3 : Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: «winrm quickconfig». 7/19/2017 5:03:36 AM

— We provide local admin rights to user «helpdesk» but no result.

Оцените статью