Tuesday, March 7, 2017

RDS 2012 R2 - Server Manager Won't Show RDS Deployment


Scenario

Ok so you know that you installed your RDS roles and your server manager used to show you your RDS deployment.  But today you logged in and you get the above message: "A Remote Desktop Services deployment does not exist in the server pool.  To create a deployment, run the Add Roles and Features Wizard and select the Remote Desktop Services installation option".

When this happened to me, I verified that the RDS roles were in installed - they were.  My remote apps still worked, the roles were still there, etc.  But server manager would not recognize the deployment.


Turns out that I had to disable IPv6 in order to get server manager to see the RDS deployment.  I don't know why this is the case, but it consistently resolves my issue.

In my case, I have two network adapters. If IPv6 is enabled on either one of them, or both of them, server manager will not detect my RDS deployment.


You have to uncheck this on all your network adapters. Once I did that, I was able to see my deployment again.

10 comments:

  1. For what it is worth. I was experiencing the same problem. Unchecking IPv6 support also worked for me. I'm still trying to figure out why this is the case.

    ReplyDelete
  2. John, thanks for commenting. If you find out why this is the case, I would be grateful to know why.

    ReplyDelete
  3. I am also having this issue. I have 4 NICs. 2 Teams of 2. Team 1 is on Network 1 Team 2 is on Network 2. All adapters and Teams have IPv6 unchecked. Server Manager still will not detect my deployment. All remote Apps are working fine. Ideas?

    ReplyDelete
  4. Been fitting this for a while. Did tons of Google searches and was not able to find anything to fix this issue. Even opened a support ticket with Microsoft. Spent over 2 hours on the phone with them and they had no clue. They were going to research it over the weekend and call me back. Just happen to stumble on this post today and it totally fixed my issue. Thanks for posting this.

    ReplyDelete
  5. Unfortunately, I don't know why this happens and only know what resolved my issue. If you hear back from MS regarding this issue, I would love to know what is going on. If someone gets some procmon and network traces while in the broken state and in the working state, I would be happy to take a look at them.

    ReplyDelete
  6. I had this issue. Disabling IPv6 might work for some, but it is just a workaround. On my case, you normally install the RDP roles by selecting "Role-Based or Feature-Based installation" in Installation Type, which is ok. However, after you finish installing your roles and restart your server, you have to go back to the Add Roles and Features Wizard, and this time "Remote Desktop Services Installation" under Installation Type, assign the server to each one of the roles in the wizard, and that will do it.

    https://tr1.cbsistatic.com/hub/i/2015/05/07/c73feea8-f4ab-11e4-940f-14feb5cc3d2a/c-2013-02-06_01-54-05.png

    ReplyDelete
    Replies
    1. You are me hero. This is an old post, so you may never see it, but I've been fighting this for two days. Thank you.

      Delete
  7. Hi, I came across this issue on Windows 2016, all of sudden users couldn't connect to Remote Desktop Host Session. Went onto server manager, Remote Desktop Services, Overview and got "A Remote Desktop Services deployment does not exist in the server pool. To create a deployment, run the Add Roles and Features Wizard and select the Remote Desktop Services installation option". Tried disabling IPv6 but didnt fix the issue.

    I then checked the domain controllers and spotted one of DC's time was out by over an hour, corrected the time, rebooted the Remote Desktop server and hey presto fixed the issue.

    What's odd is that i couldnt change the time via "Adjust date/time" the normal way, it was locked saying this setting is managed by your organisation despite no GPO locking this for the domain or DC policy. So run cmd, typed time and adjusted it that way.

    ReplyDelete
  8. old, but please check if you have configured a GPO for WinRM to listen only on specific IPv4 addresses. Connection Broker uses IPv6 internal, this is why "disabling IPv6" works.

    Computer > Administrative Templates > Windows Components > Windows Remote Management (WinRM) > WinRM Service > Allow remote server management through WinRM

    ReplyDelete