Server 2012 R2 RDS to replace Server 2003 TS

I have just replaced an SBS2003 box with a new box running Server 2012 R2 as a Hyper-V host, with several Server 2012 R2 VMs and a Server 2008 R2 VM running Exchange 2010 SP3.
I now need to replace our old Server 2003 R2 64-bit box (called TS2) which was our Terminal Server, with a VM to provide RDS. the RDS VM will be called 'Atlas'

All I really need (at this stage) is the ability for one or two remote users to be able to login and access their network drives and run MS Office applications. Previously they just used Remote Desktop Connection to connect to TS2 and their login script mapped the required network drives.

RDS appears to be a fair bit more complex than the old TS on Server 2003. So is there a good straightforward guide to RDS that might put me in the right direction? We really won't be doing anything very tricky and it is only a very few remote users that will be using it.

The immediate problem is that the old TS stopped working after the decommissioning of the SBS 2003 box and I haven't been able to get it going. So I figured it made more sense to put the effort into getting the new RDS server running than sorting out the old TS which will be decommissioned as soon as I get the RDS running anyway.

Meanwhile our remote users have no access.

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.

Dirk KotteSECommented:
there are no big differences between TS at W2003 and RDS at w2008/2012.
There is a little bit more security (your users should use the current client).
You need new TS-CALS (naw called RDS-Calls).
Yeah, Remote Desktop got significantly more complicated. Many places that describe a simple single server deployment. The connection broker is now required, in addition to the session host (terminal server) and license server. If users are connecting from the Internet, the RD Gateway can provide access without the risks of using VPN.

Fortunately, there is a wizard to get things started.
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Is there a need for HTTPS/443 inbound anywhere else on the network?

If not, then point your edge to your newly installed RDSH VM.

When you go to configure your setup by running the wizard choose ALL of the roles.

Once that process has completed what URL do folks use to access the WAN IP? You will need an SSL certificate. We use RapidSSL for that task.

CSR in IIS on RDS. Paste that into the SSL Vendor's portal, go through the authentication process, and download the certificate. Complete the CSR in IIS.

EXPORT the newly seated SSL from Certificates.MSC --> Personal store. Check all available options. INCLUDE the key. Set a password to the file.

In Server Manager go into Deployment Properties --> Certificates. Bind the newly exported certificate to the bottom two services (leave the top two self-issued unless you have an Internet TLD and ownership of the domain name set up internally).

SPLIT your DNS (new Forward Lookup Zone just like SBS). Set the URL used via the Internet to the internal IP of RDSH.

Once the above steps are complete you will be able to access the RDSH Desktop, RDWeb, or RemoteApps/RemoteApps Feed via the assigned URL.

Feed URL:

Make sure 3389 is NOT forwarded from the edge to the RDSH. Use RD Gateway and make sure Network Level Authentication is checked for a more secure connection.
gregmiller4itAuthor Commented:
Hi Guys,
I have been following the step-by-step guide at:

and I am well into it, but have hit a problem. I am up to where it says:
"Configure RD Connection Broker for High Availability"
and I need to put in the following details:

Database connection string:
DRIVER=SQL Server Native Client 11.0;SERVER=ITWDC01;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;DATABASE=ITWRDCB
Folder to store database files:
C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA
I used the instance default folder.
DNS round robin name:
The DNS Zone name we configured in DNS earlier.

I have checked and I am using SQL Express 12. The database it looks like it is called 'tempdb'.
I have changed the settings to suit the above (I think) but I am getting this message:

"The database specified in the database connection string is not available from the RD Connection Broker server servername.
Ensure that the SQL server is available on the network, the SQL Server Native Client is installed on the RD Connection Broker server, and the RD Connection Broker has write permissions to the database."

Can someone suggest how I might actually check this stuff?
You're not doing a high availability configuration, so don't try to put the connection broker in HA configuration.

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
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.