Forum Discussion
Move RDS Roles to Another Server
I'm in the process of planning for the moving of our RDS Licensing Server to a new server. I'm currently on Windows Server 2012 and moving to 2012R2. The information I've found on how to do this is...
Keep us updated 😊
Harm_Veenstra I attempted to make the move to the new RDS Farm and ran into one problem. I thought that removing the RD session host from old RDS Farm into the new one would bring with it the Collection but it did not. I did some more investigating and found that the only two choices is to migrate Collection using PowerShell (only found one article talking about this) or recreating the Collection on the new RD Farm on the Connection Broker server.
My question now is, does creating a new collection cause any problems to the application already configured on that session host? or is the Collection simply a profile that just points to it to use the parameters we need such as user permissions to access RemoteApp published in collection, etc.?
I'm thinking if the answer is yes, then recreating the Collection seems to be an easier option than the troubles I'm running into trying to use PowerShell, but I'm willing to try both if needed. What do you think?
My question now is, does creating a new collection cause any problems to the application already configured on that session host? or is the Collection simply a profile that just points to it to use the parameters we need such as user permissions to access RemoteApp published in collection, etc.?
I'm thinking if the answer is yes, then recreating the Collection seems to be an easier option than the troubles I'm running into trying to use PowerShell, but I'm willing to try both if needed. What do you think?
- Ok, will do
- Yes, remove it first because other wise you can't add it to another collection?
- One more thing, when removing the RD session host from existing RD Farm, I believe I did it wrong the first time but figured out how to get back so I'm asking to be sure for next time.
When using Server Manager, you can remove a server from the pool but I did this before removing that session host from the actual Deployment Overview/Collection section, so that's what I want to confirm...I should be removing it from Deployment Overview/Collection first correct? - No problem, curious how it works out for you
- Awesome, I had that feeling but always rather get confirmation. After my last post, I was able to get past the PowerShell hurdles and just for experience...I'm testing this method too but for when I make my next attempt at moving RD session host to new RDS Farm, I'm definitely going to just recreate the collection...I'll keep you posted on how that goes...thanks a million!
- The collection and the apps in it, that's something you configure for the users (Kind of creating shortcuts to installed apps on the host) Just make note of permissions and settings and recreate them, no impact on the installed applications on the host itself. (It won't remove it from Add/Remove programs 🙂 )