Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1108
  • Last Modified:

RDS on Server 2008 R2 (seperate box to sbs 2011 standard)

Hi all,

I have an sbs 2011 standard server running with besx but my client has requested that an rds to be implemented...instead of purchasing the sbs premium ad on for standard 2011 i am going to install windows 2008 r2 on a seperate standalone box which will become the rds server.

Can someone please gude me on how to set this up....ie what roles need to be installed on the sbs 2011 server and what roles do i need to install on the rds standalone server

The idea is i want each user to have certain apps pushed out to them via RemoteApp so they appear on their desktops and also want them to have web access....i should mention i got it to work internally but would not work externally so i have rebuilt my server 2008 r2 to basics....

I would appreciate if a step by step guide was provided and which steps would be done in order...

Vikash Mohan
Vikash Mohan
1 Solution
You will then have to have Terminal Server CALs which are more exspensive than SBS premium CALs.

Having it working external is exactly the same as internal just open up firewall port to point 3389 to the server.

Hope this helps :)
Vikash MohanTechnical DirectorAuthor Commented:
We have purchased all the relevant products including CALS

There are a few roles that need to be installed such as;

Remote Desktop Services
Session Host

What roles need to be installed on what server....does a role need to be installed on the sbs2011 server or is everything done on the server 2008 r2 server...
Darius GhassemCommented:
You can do everything on Windows 2008 Server which would be easier to contain and separate the two.
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Rob WilliamsCommented:
To correct a couple of the above comments;  RDS CAL's are not more expensive than Premium CAL's.  The only advantage of buying the premium add-on is if you need an additional server license and SQL.  The premium add-on is more expensive as are the respective CAL's and offers no additional RDS features than Server 2008 R2, as dariusg already pointed out.  Also Premium CAL's do not replace RDS CAL's you would need both Premium and RDS CAL's.  Premium CAL's cover the same as SBS CAL's + SQL access.  You decission to purchase srver 2008 R2 was the best option in this case.

Also please do not open port 3389 as it is a major security risk.  SBS is already configured with the TS Gateway service allowing you to access the RDS server with RDP over port 443/SSL.  You may want to add the RDS server to RWA as per my blog:

On the new RDS server you need to add the RDS role including the Remote app manger, RD session host, and Remote Desktop Services Manager.  The licensing service can be installed on either the RDS server or the SBS.  My preference is on the SBS as it is backed up nightly.

You can then access the new RDS server through RWA or using the RDP client. When using the client from off-site you need to put in the actual name of the RDS server (NetBIOS name) and then under advanced tab click on settings and enter the remote address for your SBS server site such as remote.MyDomain.com  You will need to have the SBS self-signed certificate installed on the client or have a 3rd party certificate.  For certificates see:

I am probably not the best one to advise you on deploying remote apps.  You may find the following step-by-step remote apps guide helpful:
Vikash MohanTechnical DirectorAuthor Commented:
Thanks for all the input will try out and let you know

Vikash MohanTechnical DirectorAuthor Commented:

Can this also be done using sbs 2003?
Rob WilliamsCommented:
Yes.  However I am not sure of the exact requirements.  
I would assume the TS Gateway Service would have to be enabled on the RDS server instead of the SBS.  Doing so will almost certainly require a second public IP as 443 would be routed to the SBS and not the RDS server.
Vikash MohanTechnical DirectorAuthor Commented:
Have implemented this on separate server.  Thanks for all your replies
Vikash MohanTechnical DirectorAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for Vikmohan's comment #a38325603

for the following reason:

Rob WilliamsCommented:
Why are you deleting the question and not awarding points if you have implemented the solution with which we assisted?

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now