Remote Desktop Services

[lholland421]

Hi all, I have setup remote desktop services and published some apps which are working well. I would like some members of staff to be able to remote straight into their workstations. How could i set this up ?

 

Thanks

[3s-gtech]

Do their own workstations have anything special on? Could they just remote in to a single central server?

[lholland421]

most staff should be okay remoting into a central server but i have a couple of staff that would need to go into their machines directly.

[Oaktech]

I've just given their domain users terminal rights on their desktops, they remote into an app dashboard and their user group gives them MSTSC.exe as a published app and they type their workstation in and away they go.

 

This has been done like this mainly so the BM can use his finance package from home.

[lholland421]

Can i save an rdp file and publish that? Also how do i setup users to remote into a single central server?

[lholland421]

Anyone know how i can configure it to work across 2 domains?

[3s-gtech]

Single central server - you just build a Remote Desktop Services session-based host, with the usual needed software on it, you can then publish that via your gateway.

 

To work across two domains, you'll need a trust in place - that what we have and it works fine.

[lholland421]

We have a trust in place and it still doesn't seem to work. Im guessing the trust must be setup both ways?

[3s-gtech]

Yup I think it will need to be. Just because the trust is two way, doesn't mean that permissions will suddenly be granted to users/admins across the trust. Our trust enables Exchange, Lync, ACLs, logons to PCs etc etc to work properly between domains.

[RowlandoGloom]

Before we brought in RDS - I came up with a daft idea.

 

I have a TMG server setup

 

Set up a NAT for different external port numbers. They were then transated to 3386 pointing to a particular PC.

 

For example, the user entered into the Remote Desktop Connection our external IP followed by the published port number:

 

xxx.xxx.xxx.xxx:1001

xxx.xxx.xxx.xxx:1002 etc.

 

A bit messy but it worked.

[DavePa]

Before we brought in RDS - I came up with a daft idea.

 

I have a TMG server setup

 

Set up a NAT for different external port numbers. They were then transated to 3386 pointing to a particular PC.

 

For example, the user entered into the Remote Desktop Connection our external IP followed by the published port number:

 

xxx.xxx.xxx.xxx:1001

xxx.xxx.xxx.xxx:1002 etc.

 

A bit messy but it worked.

 

I use exactly this for RDP to a number of servers, works well enough for our needs. Only difference from your example is that I used non-sequential port numbers (which you may have used for clarity) that were way above any 'standard' ports - 51213, 53497, 61442 type of thing.

 

If you are implementing something similar please ensure all users have strong passwords - no password1 or 12345 type of thing! Our password policy insists on a minimum of 10 characters with uppercaes, lowercase, numbers and special characters all represented.

[RowlandoGloom]

I use exactly this for RDP to a number of servers, works well enough for our needs. Only difference from your example is that I used non-sequential port numbers (which you may have used for clarity) that were way above any 'standard' ports - 51213, 53497, 61442 type of thing.

 

If you are implementing something similar please ensure all users have strong passwords - no password1 or 12345 type of thing! Our password policy insists on a minimum of 10 characters with uppercaes, lowercase, numbers and special characters all represented.

 

Basically how you say. We used ports in the 7,000 range, but did sequentially. Our password policy requires at least 8 characters and a number too.