Recently I implemented a 2012 RDS Standard Deployment. Below is my current configuration:
REMOTE02 and REMOTE03 - Hyper-V servers hosting all of our Session Host VMs.
RDS01v - Web Access Server
RDSAPP01v - RDSAPP06v - Session Hosts Session Hosts for 1st Collection needed for a legacy app that must use a desktop.
RDSCB01v - RDS Connection Broker
LICENSE01v - Licensing Server
RDSOTHERAPP01v - 06v Session Hosts for a 2nd Collection needed for a legacy app that must use a desktop.
----------------------------------
During the configuration of the 2nd Collection, and preparing for the pilot for our end users (switching from Citrix to MS RDS), the vendor of the legacy app gave us another solution that would be easier for our end users. Therefore, we no longer needed (Collection #2) and the VMs. Rather than delete the VMs, I shut them down on the Hyper-V hosts for the time being, however, I did delete the collection. Now for some reason, when I log into RD Web Access, the 2nd Collection, and the Remote Desktop connection to that Collection via the Connection Broker still exists. I see Collection 1, and all works well, but the 2nd Collection still shows up. I've rebooted my Connection Broker, Web Server, shut down the Session Hosts I no longer need, but it still shows up. I deleted the AD Group associated with that specific collection. Can anyone help me here? Or has anyone run into anything similar?
Thanks! Nate