Technology Tips and News
Trying to install RDS on 2012 I get the following error.
"Unable to connect to the server by using Windows Powershell Remoting" On the "Checking Compatibility" window. I'm just trying to install the "Quick Start: option
I did the "Enable-PSRemoting -force" on the server and still have the error.
enabled "allow remote server management through WinRM" in group policy also, still same problem.
Thanks ahead of time.
Hi,
I would like to know how did you install the role, by Windows Powershell remoting or use Server manager to manage remote Server?
After enable both server's psremoting, please restart them and try again.
Regards,
Yan Li
Hey there, did you ever get an answer to this?
I am having the same issue.
psremoting IS already enabled on this server.
I am using server manager to install roles.
Add Roles and Features Wizard > Remote Desktop Services Installation > Quick Start > Session-based desktop deployment, Select my server > click next > "Unable to connect to the server by using windows powershell remoting"
After working for weeks with M$ Support level 2 and higher on this issue below is the fix and reason for the issue.
In a PS Shell
Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000
then reboot
The default remote shell is allotted 150MB of memory. If we have Sharepoint/IIS App pool on the server then this memory is not sufficient to create a remote session (This is used mostly while installing any roles on windows server 2012) . Therefore by running that command we have enabled the remote shell to use 1000mb which will provide more memory to windows powershell to make remote sessions and resolve the issue.
After working for weeks with M$ Support level 2 and higher on this issue below is the fix and reason for the issue.
In a PS Shell
Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000
then reboot
The default remote shell is allotted 150MB of memory. If we have Sharepoint/IIS App pool on the server then this memory is not sufficient to create a remote session (This is used mostly while installing any roles on windows server 2012) . Therefore by running that command we have enabled the remote shell to use 1000mb which will provide more memory to windows powershell to make remote sessions and resolve the issue.
After working for weeks with M$ Support level 2 and higher on this issue below is the fix and reason for the issue.
In a PS Shell
Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000
then reboot
The default remote shell is allotted 150MB of memory. If we have Sharepoint/IIS App pool on the server then this memory is not sufficient to create a remote session (This is used mostly while installing any roles on windows server 2012) . Therefore by running that command we have enabled the remote shell to use 1000mb which will provide more memory to windows powershell to make remote sessions and resolve the issue.
I added the 'Windows Remote Management' rule to my firewall and that fixed the problem.
I added the 'Windows Remote Management' rule to my firewall and that fixed the problem.
I added the 'Windows Remote Management' rule to my firewall and that fixed the problem.
Hello,
Although I disabled the FW, allowed WinRM and Remote Powershell, I used two different NT accounts: one from a trusted forest and a 3nd one from the same forest as the server, gpupdate the policy to allow Remote Management, Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB I was trying to configure with RDS I still got the:
"Unable to connect to the server by using Windows Powershell Remoting" On the "Checking Compatibility"
In my case the solution was to "Shift" click on "Server Manager" and select "Run as administrator" .
It is a little bit silly that for "Server Manager" the elevation is not proposed even.
I hope it helps.
Best Regards,
Tiberiu Baraboi
Hello,
Although I disabled the FW, allowed WinRM and Remote Powershell, I used two different NT accounts: one from a trusted forest and a 3nd one from the same forest as the server, gpupdate the policy to allow Remote Management, Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB I was trying to configure with RDS I still got the:
"Unable to connect to the server by using Windows Powershell Remoting" On the "Checking Compatibility"
In my case the solution was to "Shift" click on "Server Manager" and select "Run as administrator" .
It is a little bit silly that for "Server Manager" the elevation is not proposed even.
I hope it helps.
Best Regards,
Tiberiu Baraboi
Hello,
Although I disabled the FW, allowed WinRM and Remote Powershell, I used two different NT accounts: one from a trusted forest and a 3nd one from the same forest as the server, gpupdate the policy to allow Remote Management, Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB I was trying to configure with RDS I still got the:
"Unable to connect to the server by using Windows Powershell Remoting" On the "Checking Compatibility"
In my case the solution was to "Shift" click on "Server Manager" and select "Run as administrator" .
It is a little bit silly that for "Server Manager" the elevation is not proposed even.
I hope it helps.
Best Regards,
Tiberiu Baraboi
Still not working for me
tried services and PS enable and PS expand Shell size....nothing
here's my other issue - I'm following the MS MOC - trainer guide for MCSE Desktop Infrastructure
Testing it out so I can teach this component - lol - hard to teach if it don't work
any ideas??
had same issue fixed it by
clearing the proxy
netsh winhttp reset proxy
worked for me
had same issue fixed it by
clearing the proxy
netsh winhttp reset proxy
worked for me
had same issue fixed it by
clearing the proxy
netsh winhttp reset proxy
worked for me
None of this worked for me :(
I'm Trying in W Azure Scenario with 1subnet.
http://s7.postimg.org/e45xr7t07/w2012rds_fail.jpg
None of this worked for me :(
I'm Trying in W Azure Scenario with 1subnet.
http://s7.postimg.org/e45xr7t07/w2012rds_fail.jpg
None of this worked for me :(
I'm Trying in W Azure Scenario with 1subnet.
http://s7.postimg.org/e45xr7t07/w2012rds_fail.jpg
I had the same issue, none of the above worked for me.
I decided to see what my FQDN was resolving to and it was using the IPV6 address FE80 etc, I disabled IPV6 and retried and it worked for me.
I had the same issue, none of the above worked for me.
I decided to see what my FQDN was resolving to and it was using the IPV6 address FE80 etc, I disabled IPV6 and retried and it worked for me.
I had the same issue, none of the above worked for me.
I decided to see what my FQDN was resolving to and it was using the IPV6 address FE80 etc, I disabled IPV6 and retried and it worked for me.
Reference following article,
http://searchwindowsserver.techtarget.com/feature/How-to-enable-PowerShell-remoting
I just solved
In case you're using a Hyper-V based scenario: for me it helped to disable "Integration Services > Time Synchronization" within the Hyper-V settings for the virtual machine I tried to deploy remote desktop services on.
The problem was that the virtual machine was somehow out of sync with the domain controller and thus was not trusted to use remote management/powershell ...
Here's what I've found. Adding RDS with the "Quick Start" option, followed at some point later removing RDS, seemed to give me the "Unable to connect to the server by using Windows Powershell Remoting".
I did the powershell fix. "Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000",
reboot and retry didn't do it for me.
Also the Server Manager SHIFT runas Administrator (not sure how it's even possible NOT to run as Administrator really?) didn't do it for me.
I had my firewall turned off, so no issues there. I did reset it and turn it off again. Still nothing.
Re-adding back IIS along with RPC for HTTP Proxy, rebooted. Was able to add the RDS and Quick Start role again.
Not 100% sure how that's the case. But I removed them. Got the same error. Readded them (rebooting between add and removal) it worked again.
Hope this saves someone some frustration.
Here's what I've found. Adding RDS with the "Quick Start" option, followed at some point later removing RDS, seemed to give me the "Unable to connect to the server by using Windows Powershell Remoting".
I did the powershell fix. "Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000",
reboot and retry didn't do it for me.
Also the Server Manager SHIFT runas Administrator (not sure how it's even possible NOT to run as Administrator really?) didn't do it for me.
I had my firewall turned off, so no issues there. I did reset it and turn it off again. Still nothing.
Re-adding back IIS along with RPC for HTTP Proxy, rebooted. Was able to add the RDS and Quick Start role again.
Not 100% sure how that's the case. But I removed them. Got the same error. Readded them (rebooting between add and removal) it worked again.
Hope this saves someone some frustration.
Here's what I've found. Adding RDS with the "Quick Start" option, followed at some point later removing RDS, seemed to give me the "Unable to connect to the server by using Windows Powershell Remoting".
I did the powershell fix. "Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000",
reboot and retry didn't do it for me.
Also the Server Manager SHIFT runas Administrator (not sure how it's even possible NOT to run as Administrator really?) didn't do it for me.
I had my firewall turned off, so no issues there. I did reset it and turn it off again. Still nothing.
Re-adding back IIS along with RPC for HTTP Proxy, rebooted. Was able to add the RDS and Quick Start role again.
Not 100% sure how that's the case. But I removed them. Got the same error. Readded them (rebooting between add and removal) it worked again.
Hope this saves someone some frustration.
I tried all the above but did not succeed. But after I had changed my network from public to domain network it worked.
How I did this?
I have a separate domain controller server in my network and also a NAT/Firewall. This NAT/Firewall is setup as DHCP server so I have set my DNS towards this server. 10.0.0.1 As a secondary server I have set my Domain controller's IP 10.0.0.10 and now the network changed to Domain-Network and I am able to install RDP services.
Hope this helps you guys.
The link from Anonymous2992 helped me to this solution. Thanks!
I tried all the above but did not succeed. But after I had changed my network from public to domain network it worked.
How I did this?
I have a separate domain controller server in my network and also a NAT/Firewall. This NAT/Firewall is setup as DHCP server so I have set my DNS towards this server. 10.0.0.1 As a secondary server I have set my Domain controller's IP 10.0.0.10 and now the network changed to Domain-Network and I am able to install RDP services.
Hope this helps you guys.
The link from Anonymous2992 helped me to this solution. Thanks!
I tried all the above but did not succeed. But after I had changed my network from public to domain network it worked.
How I did this?
I have a separate domain controller server in my network and also a NAT/Firewall. This NAT/Firewall is setup as DHCP server so I have set my DNS towards this server. 10.0.0.1 As a secondary server I have set my Domain controller's IP 10.0.0.10 and now the network changed to Domain-Network and I am able to install RDP services.
Hope this helps you guys.
The link from Anonymous2992 helped me to this solution. Thanks!
Hi Guys,
This silly error wasted my 1 precious day
In my case i restarted the DC and RDS server to resolve this issue.
Hope this may help someone.
Goodluck !!
had same issue fixed it by
clearing the proxynetsh winhttp reset proxy
worked for me
Hi Tibi,
Ur solution worked in my case...
Have tried all the above and none have worked for me on Windows 2012 R2 RDS.
On Windows 2012 RDS servers it works fine without any problem
Have tried all the above and none have worked for me on Windows 2012 R2 RDS.
On Windows 2012 RDS servers it works fine without any problem
Have tried all the above and none have worked for me on Windows 2012 R2 RDS.
On Windows 2012 RDS servers it works fine without any problem
@joshhoff
Have you managed to resolve the issue yet?
All the solutions mentioned before didn't solve our problems. Finnaly we decided to uninstall Powershell completely from our newly installed RDS Server...the site affect of this is that the GUI also will be unistalled. After te uninstall of powershell we
rebooted the server. Via our DC's Server Manager we installed Powershell remotely again along with the GUI and this solved our problem. Because the other newly installed servers didn't have this problem I guess that this problem is introduced after installing
a feature (my guess is the Desktop Experience Feature, but i'm not sure and will test this later this week).
i found another possible reason, this solution worked for me:
http://oyvindnilsen.com/solution-for-powershell-remoting-error-it-cannot-determine-the-content-type-of-the-http-response-from-the-destination-computer/
I tried to set up powershell remoting on a server and kept getting this error:
Enter-PSSession : Connecting to remote server failed with the following error message : The WinRM client cann ot process the request. It cannot determine the content type of the HTTP response from the destination comput er. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help to pic.
After a bit of troubleshooting I discovered that the problem was that the authentication packets was to big (over 16k), this will cause WinRM to reject the request. The reason for authentication packets getting too big can be because the user is member of very many security groups or in my case because of the SidHistory attribute.
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.
i found another possible reason, this solution worked for me:
http://oyvindnilsen.com/solution-for-powershell-remoting-error-it-cannot-determine-the-content-type-of-the-http-response-from-the-destination-computer/
I tried to set up powershell remoting on a server and kept getting this error:
Enter-PSSession : Connecting to remote server failed with the following error message : The WinRM client cann ot process the request. It cannot determine the content type of the HTTP response from the destination comput er. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help to pic.
After a bit of troubleshooting I discovered that the problem was that the authentication packets was to big (over 16k), this will cause WinRM to reject the request. The reason for authentication packets getting too big can be because the user is member of very many security groups or in my case because of the SidHistory attribute.
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.
i found another possible reason, this solution worked for me:
http://oyvindnilsen.com/solution-for-powershell-remoting-error-it-cannot-determine-the-content-type-of-the-http-response-from-the-destination-computer/
I tried to set up powershell remoting on a server and kept getting this error:
Enter-PSSession : Connecting to remote server failed with the following error message : The WinRM client cann ot process the request. It cannot determine the content type of the HTTP response from the destination comput er. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help to pic.
After a bit of troubleshooting I discovered that the problem was that the authentication packets was to big (over 16k), this will cause WinRM to reject the request. The reason for authentication packets getting too big can be because the user is member of very many security groups or in my case because of the SidHistory attribute.
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.
Same problem, but what worked for me was deleting stored credentials for the RDVH via cmdkey.
Same here, tried everything else. Turning IPv6 off finally worked.
Stupid.
I tried everything above..."Enable-PSRemoting -force", "Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000", resetting the proxy, elevating rights, running as a domain admin rather than just local admin, I already had RD Licensing Manager & RD Session Host roles installed, I uninstalled them figuring maybe that was the issue. Still the same error message over and over again no matter what I tried.
Despite the error text I was able to connect fine using Enter-PSSession [servername] from a remote host. What FINALLY fixed it for me, was pulling the server out of it's OU, putting it in the default "Computers" OU so almost no GPOs would apply to it, did a gpupdate /force, rebooted, and I was able to run the install without issue, so there's something wonky with one of my GP settings that breaks the RDS install.
Hello,
I did the Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000.
But now i cant logon the server annymore.
Can you help me?
Tami Jones solution worked for me Windows server 2012 Datacenter Edition in Windows Azure:
- by clicking server manager.. local server and enabling "remote management"
Tried everything.
Finally, disable IPv6 work for me.
Try this command.
Enable-PSRemoting -force in Powershell
This resolves the issue on my Windows Azure Server
Regards,
Nandha
I tried running server manager as administrator (nope), disabling Windows firewall (nope), Enable-psremoting -force (was already enabled). None of these items fixed my issue.
Disabling IPV6 via the hotfix found here: https://support.microsoft.com/en-us/kb/929852
^ that resolved my issue.
Windows Server 2012 R2 Standard on VMWare 5.1
In our case it was IPv6. A little digging revealed that we applied a GPO using Computer -> Policies -> Administrative Templates -> Windows Components -> Windows Remove Management -> WinRM Service -> Allow remote server management through WinRM
Because we were not using IPv6 we did not add an IPv6 Filter so it simply blocked everything on that protocol. It, of course, was working for everything else because we were using IPv4.
Hi, in my case the problem was that our DC is based on Samba 3.
Upgrading to Samba latest version this error does not come up.
Tried everything else on this page but none worked except this.
Thanks amentma !
This topic is archived. No further replies will be accepted.
Other recent topics
Click here to get your free copy of Network Administrator. Over 25 plugins to make your life easier