While I recognize that installing anything to do with terminal services or RDS on a domain controller is not recommended it is my only choice for a very small business that I'm helping out. They have Server 2008 R2 and all they want to be able to do is have a couple of people remote in to their own computers when out of the office. What services are the simplest way to accomplish this? I can't find an answer to something this minimalist anywhere.

• Edited by Jim_Satterfield Wednesday, March 18, 2015 7:57 PM

For a couple of people it won't require any additional role, Windows server allows 2 administrative RDP connection.

https://technet.microsoft.com/en-us/library/cc770759.aspx

You can do that from Server Manager

That won't work because this is for non-technical users to remote in to their own computers in the office.

If they need to remote to a client I suggest a VPN, you can't just publish RDP connection from clients to RDS

Isn't that the point of Remote Desktop Web Connection and Remote Desktop Web Access?

I'm pretty sure that these services are meant to allow you to connect to a Remote desktop session host, not to a client.

• Proposed as answer by Dharmesh SMicrosoft contingent staff, Moderator 1 hour 23 minutes ago

No, one of the available services is connection to desktop clients like the old Remote Web Workplace in Small Business Server.

My bad, sorry I am not familiar with this feature of RDWA

I found this:

http://blogs.technet.com/b/sbs/archive/2014/05/07/configuring-and-customizing-remote-web-access-on-windows-server-2012-r2-essentials.aspx

You need the "essentials" server role installed on a Windows 2012 R2

Thanks for the link but I forgot to put in the original post that they are running Windows Server 2008 R2. I've fixed that oversight now, though.

If you want your users connect to their workstations from an external location (Home...), you can eithe ruse a VPN or you can use Remote Desktop Services Gateway role (Windows 2008 R2 and later)

Look here to a rapid overview

https://technet.microsoft.com/en-us/library/cc731150.aspx

Look here to install an configure this role

https://technet.microsoft.com/en-us/library/cc770690.aspx

Test it via the steps exposed in this thread (Answer number 7) : Use the IP address of the workstation you want to connect to, instead of RDSH

I'm trying to configure that service but I'm having two issues. First, even though I've gone through and configured it so that I should be able to have a single logon I'm still getting a logon prompt for RDWeb and the gateway. Also, when I go to link to a specific computer I get the message "This computer can't connect to the remote computer because the Terminal Services Gateway server is temporarily unavailable.".

Because of this and several articles that I've read I was wondering if, since there is only one server involved, I really needed the gateway and the connection broker services.

Hi Jim,

For your issue regarding double prompt, suggest you to enable RD Web SSO for your case; where we need to enter username and password once. In order for Web SSO to work:

a. The connection in RemoteApp and Desktop Connections must have an ID. By default, it is set to the Fully Qualified Domain Name (FQDN) of the RD Connection Broker server in case of RD Connection Broker mode. In RD Session mode, it is set to the FQDN of the RD Web Access server.
b. RemoteApp programs must be digitally signed using a Server Authentication certificate [Secure Sockets Layer (SSL) certificate]. 
c. Client operating systems must trust the certificate with which the RemoteApp programs are signed.

You can refer the following article for information.
Introducing Web Single Sign-On for RemoteApp and Desktop Connections
http://blogs.msdn.com/b/rds/archive/2009/08/11/introducing-web-single-sign-on-for-remoteapp-and-desktop-connections.aspx

In regards to your error, we need to have required port open to make successful connection. Need to bind port 443 for RD Web and RD Gateway successful connection. Also need to have proper certificate.

Addition something might have happened to your IIS settings and more specifically to your Default Application pool. For example if you install some third-party web application, it may have changed the 32/64 bit feature on your Application pool. So please check below points.
1) Go to IIS -> Application Pools -> DefaultAppPool -> Advanced Settings -> Enalbe 32-Bit Application - > if it's True , change it to False
2) Check other relevant application pools for the same setting - > SBS Web Workplace AppPool or SBS Web Applications application pool
All of the pools should run with Enable 32-Bit - False

More information.
This computer can't connect to the remote computer because the Terminal Services Gateway server is temporarily unavailable
https://support.microsoft.com/en-us/kb/969743

Hope it helps!

Thanks.