Hi
I am doing a POC on RDS and I am currently running into some limitations that I hope someone here on the forum can help answer if those are indeed limitations or if what I try to do can be achieved in another way.
Explanation of environment.
1 datacenter site (6 RDS hosts)
11 large branch sites (2-3 RDS hosts in each branch)
Datacenter is publishing applications from central systems running in the datacenter
Branches are publishing applications from system running locally on the branches. Most of these local systems for several reasons have to run locally in the branches and it is mission critical for thin clients and computers running at the same local branch
to have access to those local published applications 24/7. That means also when the WAN link to the datacenter should go down.
Published applications must be able to be launched from computers and mobile devices, from the internet. This should be archived with gateways and web access servers placed only in the Datacenter. We don't want to have internet facing servers running on
our branch sites. Of course those local published apps on branches can only be launched from internet when the WAN link to the datacenter is up, but this is ok. Critical part is for local clients on the same site as the RDS hosts to be able to launch them
if WAN should be down.
Design considerations
Since we don't want an individual deployment for each branch, where we would need internet facing gateway and web access servers on each branch, those should be placed in the datacenter, so the best fitting design here would be the below.
Datacenter: 2 x RDS gateway/Web access servers, 2 x connection broker, license server and 6 RDS hosts.
Branches: 2-3 RDS hosts
Collections: 1 for datacenter and 1 for each of the 11 branches.
This setup however would not allow clients to start locally published applications if the WAN link is down to that branch, since users in that branch cannot reach the Web access and broker in the datacenter.
Questions:
Is there any way around this or any way it could be designed to allow users to start local published apps (not desktops) when users cannot reach the broker and web access servers.
Can you setup that if a broker is not available, the remote apps will still launch, just without load balancing and the feature to reconnect to disconnected sessions. So it should just launch directly against RDS host servers (You could probably use DNS
RR to then still get some kind of client distribution across the hosts) ?
When setting up remote desktop clients on phones and computers, they require a URL feed. This is pointed to the Web access server "https://server.domain/rdweb/feed/webfeed/xxxxxx.aspx" does this mean that the web access server is mandatory to even
be able to launch remote apps or is there another way to launch them that doesn't rely on the Web access server ?
Thanks
Martin