RDWeb and RemoteApp

[Chuckster]

Hey all,

 

I am looking to install and implement Remote Desktop Web Access and RemoteApp very soon.

 

Does anyone have any walk-through guides that I can look at? Is it simple? There's way too many confusing guides and each author has their own funny way of doing things.

 

Also, one thing I can't get my head around is how would I publish this on the school's website. I know I will need a SSL certificate but where should I obtain this from and what type should I get? SSL certs is something I have never touched base on.

 

Additionally, do I inform our ISP (local authority) that I want remote access?

 

Any help will be greatly appreciated.

 

Cheers.

[Homer]

It's not the hardest thing to do but make sure you get yourself a wildcard SSL cert if you're going to go live with this. I got ours from CBT Solutions (http://www.cbtsolutions.net) who I think I found references to on here. I think ours was around £58 for a year, and I have had absolutely no problems with compatibility and when I did need to speak to them they were more than happy to help.

 

Ideally you will need 3 separate servers, one for the connection broker (CB) role, one for the gateway role and one for the RDWeb role. You will then need a separate physical machine either running Server 2012 with the HyperV role installed or a box running HyperV Serverfor your actual machines - are you thinking of doing session host or virtualised desktop? If doing session host you will also need a licensing server although this can sit on one of the boxes doing CB/gateway role.

 

You will also need to bear the cost of licenses in mind, not much relatively speaking but it is one thing you will need to cost for.

 

You'll need to use server manager to do the deployment, it is quite straight forward from start to end just make sure you read instructions carefully but even more importantly plan on what you intend to do with it. Is it a simple limited remote access system or will you expand it to a full blown VDI or a large scale remote working solution? Just things to bear in mind as you deploy the various infrastructure as it will need to scale out.

 

As for your ISP, I don't know what your agreement with them is but providing they have no stipulations about not allowing remote access all you will need is two IP addresses, one for the gateway and one for the rdweb (although I think you can do it with one IP but I'm not sure - again think long term with this one) and then you will need to set up your firewall/router accordingly.

 

Hope this helps a little

Edited October 16, 2015 by Homer

[Snuffkins]

This seemed like a pretty decent walk through RDS Blog

 

There's load of info out there though.

 

Everything else is as @Homer has said. It's worth checking with your ISP. As another option we use ssl247 for our certs and don't have any issues.

[maxrebo]

We use this using a Session host, although i didn't know you could have virtualised desktop. I might look in to setting it up this way. Can you have it running both SH and Virtualised? or is it just one or the other? (Sorry to hijack the thread)

[Homer]

You can run both - you'll need to get another physical box prepared and then run the remote services deployment in server manager again - leave the existing CB/gateway/redweb roles selected, choose where to put the licensing server and then choose which box you want to use for session host. You will need to get CALs for this though, and the license server will check in on your Microsoft agreement for quantities purchased. You'll have 180 days grace before it will become an issue if not licensed...

 

Then just configure your desktops on there and away you go!

Edited October 16, 2015 by Homer

[win]

Setting it up is straight forward. I recommend getting a wildcard ssl cert from a place like godaddy.

 

The tricky bit is trying to lock it down without messing up peoples profiles