Hi All,
I'm in the process of a VMware to Hyper-V migration and whilst in the process rather than migrating the 2012 RDS VM's over to Hyper-V I have decided to setup a bunch of 2012 R2 VMs. My original setup was
1 x Windows Server 2012 VM running RDSCB, RDSGW & RDSWA
2 x Windows Server 2012 VMs running RDSSH
My new environment runs
1 x Windows Server 2012 R2 VM running RDSCB, RDSGW & RDSWA
2 x Windows Server 2012 R2 running RDSSH
I have the connection broker running in HA mode for SSO purposes and publishing the correct name. This also made life easier when running the upgrade as I joined the new 2012 R2 VM to connection broker group which worked fine. I then set the new 2012 R2 RDSCB VM as the active connection broker. At this point the old 2012 VM was decommissioned (Without the RDS roles removed). As the old 2012 VM is now offline and un contactable when I add any new session hosts to the collection I see an error stating it can't contact the old 2012 RDSCB.
I have been through the RDS connection broker database and removed any reference to the old RDSCB VM but this hasn't helped. Does anybody have any other ideas or would you suggest re creating the collections from scratch?
Alex