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?