Server 2012 R2: HAVE: RD Web Access working. NEED: rdp connection file

RD Web Access works fine with certs and SSO and everything is nice when users connect from IE
Server1: Connection Broker, RD Gateway, RD Web Access
Server2: Session Host
Server3: Session Host
Server4: Session Host

For internal computers I would like to have a RDP connection file. How to configure that?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
You can deliver the RSS feed via GPO and all users will get a folder called Work Resources. That's the simplest way to do it.

1: Set up Single Sign-On for 2012 R2 (domain linked GPO)
2: Set up SSO for RD Gateway (User GPO)
3: Set up RSS and deliver via GPO

For external users, they can connect by typing in any Windows 7+ Pro and up clients:
Start --> RemoteApp -->

Log on using Domain\FirstLast (however it's set up) and their password and they are done.

Always tick the "Don't ask me again" options for the two possible certificate warnings. Makes it easy.
itpartner_danmarkAuthor Commented:
Thanks Philip. You totaly lost me with that RSS feed GPO. Sorry for that.

In the meanwhile I just added three host records in DNS called farm.mydomain.local pointing to each session host IP.

Then users can do a normal RDP connection to farm.mydomain.local

I have checked in eventlog that the connection broker registers the connections, so it seems fine.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
The broker is the proper place to terminate session requests. It is the one that sends the request along to the RDSH with the least load.

DNS Round Robin is not the answer. Please set the farm up correctly.
itpartner_danmarkAuthor Commented:
Think the farm DNS round robin solution is the simplest and solves the issue.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.