Hi all! Anyone else raring to go on an RDS 2012 R2 deployment? I am currently configuring a new RDS 2012 R2 farm. Roles are separated like:
-Session host
-Connection broker
-Web access
-Gateway
Suddenly, RDWeb began populating what appeared to be duplicate RemoteApps. One of each pair was the RemoteApp configured in the collection, and the other is one of my troublesome "ghosts". I've gone so far as to uninstall every role on every server in the farm, and upon reinstalling, the ghost RemoteApp objects are still there. In fact, when I ran through the initial config again following the uninstall, the RemoteApp "ghosts" actually still appeared on the RDWeb site even before I configured a session collection again on the CB. Any ideas as to what might cause this? I have a feeling I could rebuild the CB and get positive results, but I'm a little more concerned with this behavior in terms of rolling out the farm to our organization. Should this happen in the future, I am going to need to know why and how to fix it.
Does anyone know the top-down mechanism by which RDWeb populates RemoteApps, so that we can try to determine from where on earth the CB (or the WA) server is pulling these ghosts? I should mention that I am familiar with the web.config file, in which you can add FQDN strings for legacy (08R2) SH's. No such config is in place, but having messed with that early-on in my Server 2012 (not R2) test bed, I can say that the appearance of those "ghost" RemoteApps, and their failure to disappear even when the CB reports no collections, feels in appearance and behavior like the result of having configured legacy SH's.
Any comments/thoughts are greatly appreciated!