Current Setup
2x RDS Brokers – Server 2012 R2
1x RDS SQL Database / RD License / RD Web Access / no RS Gateway configured
Round Robin DNS configured to both Brokers – working as intended
5x RDSH 2012 R2 servers for PROD collection
2x additional RDS 2012 R2 servers yet to be added
The environment is used to connect to either a DEV, TEST or PROD app. Separate collections are setup for each. Domain Users have access to the collections and apps. Security to the apps is handled by the app itself with separate login requirements.
The Problem
I have built two new RDSH servers to help with capacity as the number of users has increased dramatically since the solution was released many years ago. When I try and add these new servers into the current PROD collection, I get an error “Unable to retrieve collection properties” and the wizard ends.
However, and here’s the odd part. When I create a new collection, I can add the two new servers plus one of the other PROD RDSH servers (I removed it as part of testing) to the newly created collection. I also have the same problem if I try just adding one of the old RDSH servers too. If I remove one of the RDSH servers from this Test Collection I can’t then re-add it back again. I have to scrap the collection completely and build a new one.
I’ve switched RDMS logging on and the logs don’t tell me anything I don’t already know – copy of log below (redacted server names). All servers im testing with are at the same current patch level too.
AddRemoveSessiontoCollectionWizardTask.Execute::<exisitingserver.domain.com>
RdmsUI: RDManagement\Add-RDSessionHost -CollectionAlias TEST -RDSHServer System.String[] -RDManagementServer <Broker1.domain.com>
AddRemoveSessiontoCollectionWizardTask.Execute:: RDMSModel.Instance().RdmsServerName-<Broker1.domain.com>
CommandLetExecutor: Job Progress Received for cmdlet: RDManagement\Add-RDSessionHost - Progress : 0 - -1% completed
CommandLetExecutor: Job Progress Received for cmdlet: RDManagement\Add-RDSessionHost - Add-RDSessionHost - 0% completed
CommandLetExecutor: Job Progress Received for cmdlet: RDManagement\Add-RDSessionHost - Progress : 0 - -1% completed
CommandLetExecutor: Job Progress Received for cmdlet: RDManagement\Add-RDSessionHost - Verbose: Input - -1% completed
CommandLetExecutor: Job Progress Received for cmdlet: RDManagement\Add-RDSessionHost - Verbose: Input - -1% completed
CommandLetExecutor: Job Progress Received for cmdlet: RDManagement\Add-RDSessionHost - InlineScript - -1% completed
CommandLetExecutor: Job Progress Received for cmdlet: RDManagement\Add-RDSessionHost - InlineScript - -1% completed
RdmsUI: Workflow 'RDManagement\Add-RDSessionHost' failed: System.Management.Automation.RemoteException: Unable to retrieve the session collection properties.
RdmsUI: Job finished for cmdlet RDManagement\Add-RDSessionHost
Has anyone encountered this problem before and if so, how did you solve it? Is this an issue with the RDS SQL database? If so, is there way I can fix it? Restoring isn’t an option as we don’t know how long its been like this and would take far too long in going through backups.
Thanks