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
UseIT | Roman Levchenko 
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.
Nice to hear that! Thanks for your feedback.
I’ve been fighting this for a day and finally found this article, thank you for posting it.
Here is the thing I don’t understand, if they are moving us to ipv6 then why on earth are they not making these programmers work with it?
Sheesh
Thanks, disabling IPv 6 was also the option for us.
Thanks, worked perfectly
Doesn’t work in my case.
HI, Thanks heaps, the clue for me was: •PowerShell is configured to receive remote queries (Enable-PSRemoting) – Using Server 2012 R2 Foundation series – was running as a DC and after finding the above little germ, everything installed and working. Thanks again !
If you find that disabling IPv6 resolves the issue your WinRM listener is probably not listening on IPv6. The solution is to configure it to listen on IPv6 as well as IPv4 rather than disabling IPv6.
Thanks a lot rlevchenko.
This is resolve my issue
It worked just disabling IPv6 for me!! thanks so much!!