I seem to have a problem with Windows Server 2012R2 remote desktop services. From time to time i cannot manage my servers. We have several Remote desktop farms, one 4 node widows Server 2008 RTM farm, a single Node Windows Server 2012r2 farm and a 6 node Windows Server 2012r2 farm. we have no issue with the Windows Server 2008 RTM farm, but have a lot of issue's with the two other ones. the same issue occurs on both nodes, and the issue is that i cannot manage them. In server manager i get the following error: "The WinRM client cannot process the request. It cannot determine the content type of the http response from the destination computer. the content type is absent or invalid."
When i try to manage the RD deployments via powershell i get:
PS M:\> Get-RDRemoteApp -ConnectionBroker connectionbroker.domain.group
Get-RDRemoteApp : A Remote Desktop Services deployment does not exist on connectionbroker.domain.group. This operation can be performed after creating a deployment. For information about creating a deployment, run "Get-Help New-RDVirtualDesktopDeployment"
or "Get-Help New-RDSessionDeployment".
last week i had it on the single node, but could manage the node from the other 6 node cluster. Rebooted the single node over the weekend, and the issue was resolved. This morning the issue returned, in which i was unable to manage Remote desktop deployment from all nodes, except one. All published applications are running fine, but cannot the deployment. Rebooting the node resolves the issue for that node.
Have been looking into the issue, where it could be that the kerberos ticket is to large for the logged-on user. However when i log on with a user which is only member of the domain admins, the issue isn't resolved. So think it is not related to where the kerberos, or NTLM authentication issue described here:
http://oyvindnilsen.com/solution-for-powershell-remoting-error-it-cannot-determine-the-content-type-of-the-http-response-from-the-destination-computer/
all servers are fully patched.
Answers provided are coming from personal experience, and come with no warranty of success. I as everybody else do make mistakes.