Hi,
Microsoft drives us hard to use RD Broker, IIS etc.. But this is totally over killing my needs. For instance a RD Broker is a single point of failure, so you need actually two. IIS is a target for attacks. By using Roaming profiles, you need a file server, which is also a single point of failure, so you also need two, clustered. In addition you need to fine tune what part of the profile is roaming and what part is redirected. So you're ending up with an extremely complex infrastructure.
In the long run a complex infrastructure is more prone to failure IMO. So I like my RDS servers being autonomous entities. High availability being handled by the underlying virtualization infrastructure. (OK I don't have "ultra" high availability but my users and I can live without it.)
I know that we can install Remote Desktop Session Host role by going through a "Role based or feature based installation" instead of a "Remote Desktop Services installation". So far so good for Full Desktop access. (Expect that we are still missing the Remote Desktop Service manager MMC. )
But how to give access to a RemoteApp w/o installing IIS, RD Broker etc... ? (Note that I'm publishing RemoteApps internally, not to the entire world.... I don't need IIS, I'm happy with my GPO pushing the rdp files to my clients.).