Mundy

IT Knowledge Base

User Tools

Site Tools


Sidebar

Contact me at dan@mundy.co for any feedback or suggestions.


My other sites:

Search all my sites:

how_to_move_a_remote_desktop_session_host_to_a_deployment_on_a_different_connection_broker

How to move a remote desktop session host to a deployment on a different connection broker

The official Microsoft answer to “how do you migrate to a new connection broker” involves setting up High Availability, which requires the use of SQL Server and may be too complex for your scenario.

But it's also possible to simply remove the session host from one collection, remove it from the deployment (and delete the deployment if it's the last member), and then just add it to a new collection on a different connection broker. Following is the procedure to do that.

I'm assuming you will test this in a non-production environment. It worked when I tried it, but I can't guarantee that it will work for you.




Assumptions: collection1 is the old one, collection2 is the new one

  1. Server Manager > Remote Desktop Services > Collections > collection1
  2. In “HOST SERVERS”, click Tasks > Remove RD Session Host servers
  3. Follow the prompts to remove the session host server from the collection
  4. Go up one level, to “Collections”
  5. In “HOST SERVERS”, click Tasks > Remove RD Session Host servers
  6. Follow the prompts to remove the session host server from the deployment. Do NOT check “Uninstall the RD Session Host role service”
  7. If this was the last session host in the deployment, you'll get an error “Delete all the session collections before deleting the deployment”
    1. Cancel the wizard, do not remove the server yet
    2. Right click on collection1, “Remove Collection”
    3. In “HOST SERVERS”, click Tasks > Remove RD Session Host servers
    4. Follow the prompts to remove the session host server from the deployment. Do NOT check “Uninstall the RD Session Host role service”
    5. You'll get a warning “Removing all the RD Session Host servers deletes the existing session-based desktop deployment. To create it again, you must use the Remote Desktop Services installation option. Do you want to continue?”
    6. Click Yes, and then Remove
  8. You may see the message “A Remote Desktop Services deployment does not exist in the server pool”. For now, go to “All Servers” in Server Manager and remove any session hosts that have not yet been moved to the new connection broker, and the old connection broker. Just add the new connection broker and any session hosts that may exist in collection2
  9. On the new connection broker, Server Manager > Remote Desktop Services > Collections
  10. In “HOST SERVERS”, click Tasks > Add RD Session Host Servers (if the session hosts are not a selectable option, add them back in Server Manager > Manage > Add Servers)
  11. Follow the prompts to add the session host to the deployment on the new connection broker
  12. Server Manager > Remote Desktop Services > Collections > collection2
  13. In “HOST SERVERS”, click Tasks > Add RD Session Host Servers
  14. Follow the prompts to add the session host to collection2
  15. This would be a good time to configure User Profile Disks, to match the configuration that was on collection1 (if required)
how_to_move_a_remote_desktop_session_host_to_a_deployment_on_a_different_connection_broker.txt · Last modified: 2018/04/09 09:56 (external edit)