Server Manager Remote Desktop Services overview empty

Remote Desktop Services tools aren't functional after you remove a server from Server Manager

• Article
• 09/24/2021
• 2 minutes to read
• 2 contributors

Is this page helpful?

Yes No

Any additional feedback?

Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.

Submit

In this article

This article provides a solution to an issue where Remote Desktop Services (RDS) tools aren't functional after you remove a server from Server Manager.

Applies to: Windows Server 2012 R2
Original KB number: 2910155

Remote Desktop Services deployment overview empty

Archived Forums

>

Remote Desktop Services (Terminal Services)

• Question

• 0

  Sign in to vote

  Hi all,

  after adding the role for virtual desktop to my RDS, the Server Manager crashed and after that the "Deployment overview" is empty - all items stay as the "plus" sign.

  If I go through PowerShell, the deployment is still there and works, but I can't manager it from the Server Manager. I've tried managing from another server in the pool but the result is the same.

  Deployment servers is also empty and in both cases, the "refresh bar" over them never stops.

  Any ideas?

  Tuesday, January 26, 2016 12:13 PM

Answers

• 3

  Sign in to vote

  Just fixed it - basically there was a broken Virtual Desktop Collection which prevented the manager from opening the deployment.

  Through PowerShell I've listed the collections (Get-RDVirtualDesktopCollection) and removed them (Remove-RDVirtualDesktopCollection).
  

  After that the Server Manager started working again.
  

  • Marked as answer by KeitaroBR Tuesday, January 26, 2016 1:51 PM

  Tuesday, January 26, 2016 1:51 PM

All replies

• 3

  Sign in to vote

  Just fixed it - basically there was a broken Virtual Desktop Collection which prevented the manager from opening the deployment.

  Through PowerShell I've listed the collections (Get-RDVirtualDesktopCollection) and removed them (Remove-RDVirtualDesktopCollection).
  

  After that the Server Manager started working again.
  

  • Marked as answer by KeitaroBR Tuesday, January 26, 2016 1:51 PM

  Tuesday, January 26, 2016 1:51 PM

• 0

  Sign in to vote

  Hi,

  Glad tosee thatthe issue is resolved and thank you for sharing the solution with us!

  Please feel free to let us know if there are any further requirements.

  Best Regards,

  Amy

  ---

  Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact .

  Monday, February 1, 2016 7:14 AM

• 0

  Sign in to vote

  Just fixed it - basically there was a broken Virtual Desktop Collection which prevented the manager from opening the deployment.

  Through PowerShell I've listed the collections (Get-RDVirtualDesktopCollection) and removed them (Remove-RDVirtualDesktopCollection).
  

  After that the Server Manager started working again.
  

  Just wanted to post that i ran into the same issue! had a failed collection deployment yesterday, and didnt realize that the RDCB still had the collection listed via PS even though yesterday that failed collection wasnt listed in server managers RDS collections. i had rebooted my RDS servers over night last night and came into the same issue where nothing was populating in the RDS overview pages in server manager. thought somehow my RDS deployment was borked! yet all my VDI users werent having any issue connecting so i knew RDS wasnt that broken!

  +100 to you for this fix! didnt even think to check via PS.

  Hopefully i can now have a relaxing rest of my friday! cheers!

  
  
  • Edited by _David_B_ Friday, August 11, 2017 2:51 PM

  Friday, August 11, 2017 2:48 PM

6 Replies

· · ·

Mace

OP

JitenSh

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Oct 16, 2017 at 09:22 UTC

(we still have 2 XP's left, which is why I haven't raised yet)

You dont need to worry about XP, worry only if you have domain controller with OLD OS.

Forest and Domain Functional level is 2012R2

> Its OK, there should be no problem.

Note: Each Session host that’s a member of an RDS collection is limited to only participating in one collection.

run from powershell do see the collection?

Powershell

Get-RDVirtualDesktopCollection

https://blogs.technet.microsoft.com/askperf/2012/10/30/windows-8-windows-server-2012-remote-desktop-...

0

· · ·

Jalapeno

OP

FV-ITBolig

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Oct 16, 2017 at 09:35 UTC

hi.

Yes I know a Host Server can only be used once. :)

RunningGet-RDVirtualDesktopCollection from the 2012R2 Connection Broker runs, but gives no output.

From other servers i get:

A Remote Desktop Services deployment does not exist on ServerXX.itbolig.local

Everything is working fine, and can be managed/viewed fine from a 2012R2 Server Manager.

the problem is only in a 2016 Server Manager, where "Session Hosts" is empty.

1 of the problems would be, that I'm not able to remove a Host Server from a collection, as they are simply not shown.

As stated, everything is OK in a 2012R2 Server Manager.

btw, licensing role is on 2016 server also.

0

· · ·

Jalapeno

OP

FV-ITBolig

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Oct 16, 2017 at 09:43 UTC

To clarify setup:

1 x 2012R2 with Gateway, connection Broker and Web Access roles.

2 x 2012R2 Session hosts in a Remote desktop "cluster" Collection.

1 x 2016 Session host Remote App Collection + RD licensingrole.

1 x 2012R2 unused Session host.

1 x 2016 Management Server (new)

1 x 2012R2 Management Server (old)

0

· · ·

Jalapeno

OP

FV-ITBolig

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Oct 16, 2017 at 09:52 UTC

From all servers running:

Get-RDVirtualDesktopCollection -ConnectionBroker "BrokerServer.domain.local" runs, but no output.

I can see the collections in Server Manager though. both in 2012R2 and 2016

0

· · ·

Jalapeno

OP

FV-ITBolig

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Oct 16, 2017 at 11:24 UTC

Raising Forest and Domain did NOT correct the problem.

0

· · ·

Jalapeno

OP

FV-ITBolig

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Oct 17, 2017 at 15:13 UTC

Changed everything to 2016 servers.

Except RD Connection Broker. (not possible to change)

Still problem.

Ended up setting up a new RDS Deployment.

Problem gone.

Looks like RD Connection Broker has to be 2016.

idk if it is possible to upgrade from 2012R2 to 2016, not testet.

0

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.