danielrostron

Thanks for your help with this. Just encountered one last problem. They can access it fine from Windows 7 clients, however the majority of them are based on Windows XP machines. Is there any configuration I need to take into account if the user is coming in from an XP client? Apparantly they can access our 2 published apps (Web pages) fine, but when they click on to load up an actual desktop its throwing up another Username and Pass box and the credentials aren't working.

Think I've managed it actually. I had installed the Gateway Role when I initially created the server. I popped in our remote.domain.co.uk in to the server name on the RemoteApp settings and fired up packet sniffer and then tried connecting up again from a laptop with a dongle. Voila not a 3389 in sight, and it looked as though it was going through 443. I disconnected and tried again and it error'd saying it couldnt find the server so I tried again and it worked! Not sure why it was intermittent though but at least I'm getting somewhere (I think!)

Hi James, so would that be changed in the RemoteApp Deployment Settings prompt (like below?) At the moment I don't have anything specified in here. Would I put remote.ourdomain.co.uk as the server name? Are there any other configuration changes I need to make or is that it?

Hi all, having a bit of a problem at the moment with our RDS Remote Web Access and getting it to work with some other organizations firewalls/proxies etc. Just a bit of background, the RDS server is setup and running fine, the certificate is installed correctly and users can access the web gateway via https://remote.ourdomain.co.uk/, they can log in and they can run either a published App or click Remote Desktop to load straight into a desktop. All of this works fine. We have some members of staff who have been seconded out to work in other partner organizations and I am coming against a problem whereby our remote access isn't being allowed through their proxies/firewall/whatever because when it makes a connection back to our server it does so on port 3389 directly, which is a big no-no. Now i'm under the understanding that the SSL port 443 is a port which will allow the traffic through but i'm a bit stumped at the moment in how to get the traffic routing over that so that it can traverse any firewalls and proxies it comes to without any problems. I'm not the greatest with all this RD Web remote access stuff so i'm not entirely sure if ive missed off a simple option, or if the way I have configured it is prohibiting it from being sent out over 443. I have 2 rules set up on our Draytek. One is to forward port 3389 on one WAN IP (the one that is pointing to our web access page) to 3389 on the RDS server (if I don't have this setup when a user clicks on the remote desktop link they can't get in, it just thros up an error when trying to connect). And another is port forwarding of 443 from the same WAN IP to the same RDS server (if I dont have this setup users can't access our https://remote.ourdomain.co.uk/ ) I'm not sure if these play any part in all of this. I have no idea if this is the correct way to do things but that's how I got it all to work in the first instance and upon looking at a packet tracer I can see that when it does connect it connects on 3389. Is anyone able to offer any advice/guidance on how I might get it so that all the data is sent over 443 instead of 3389? Thanks.

Hi all, i've set up a 2008 R2 server at work with Remote Desktop Services on and have rolled out thin clients to one of our offices who can connect up fine and dandy and work as I'd like them to, they can even plug in USB pen drives and they are picked up fine in their session. However i've just come to setting up some new systems at another office and i'm trying to trial Windows ThinPC instead of buying thin clients. I've got the machine all set up so that it boots straight to the RDP connection window and then users can log directly onto the server from that, but for some reason I can't get it to redirect the USB drive that is plugged in on the local machine. Ive tried it both before i've been logged on and whilst logged on and it won't show up for me and I can't figure out why! I've checked the local resources in the RDP connection file and ive got the boxes ticked for 'drives that I plug in later' and also 'other supported plug and play devices' but this has not worked. I've also explicitly ticked the USB drive when I have it plugged in prior to connection to the server but this still does not work. Anyone any ideas? I can't understand why it works fine on the Wyse thin clients but not on these Windows ThinPC machines. Could it be a group policy i've set? I've had a brief look but can't put my finger on anything?!

Hi all, i've set up a 2008 R2 server at work with Remote Desktop Services on and have rolled out thin clients to one of our offices who can connect up fine and dandy and work as I'd like them to, they can even plug in USB pens and they are picked up fine in their session. However i've just come to setting up some new systems with Windows ThinPC instead of buying thin clients and i've got the machine all set up so that it boots straight to the RDP connection window, but for some reason I can't get it to redirect the USB drive that is plugged in on the local machine. Ive tried it both before i've been logged on and whilst logged on and it won't show up for me and I can't figure out why! I've checked the local resources in the RDP connection file and ive got the boxes ticked for 'drives that I plug in later' and also 'other supported plug and play devices' but this has not worked. I've also explicitly ticked the USB drive when I have it plugged in prior to connection to the server but this still does not work. Anyone any ideas? I can't understand why it works fine on the Wyse thin clients but not on these Windows ThinPC machines. Could it be a group policy i've set? I've had a brief look but can't put my finger on anything?!

From the GPO? I did try specifying a VBS file for the Custom User Interface GP but it didn't seem to want to load that. This is the VBS script I had (found it online and modified it slightly).... C:\EB.rdp being the custom RDP file I'd setup. (would it be possible to have that read from a network location?) Also does the mstsc.exe need to be a full path like "%windir%/system32/mstsc.exe...." or is just mstsc.exe OK? Does that look right? I stored the script in a network share and pointed the GP to it but it didn't seem to play ball, it loads up the mstsc.exe client fine when I just specify the path of mstsc.exe in the GP, but not when I put the VBS script path in.

Arthur - thanks for the upload Is there any documentation anyway as to how I actually use Shelly? localzuk - I was thinking more towards a full shell replacement so that it would be easy for end users to log on to a server. I've managed to get the machine to auto login with a domain account through GPO, and have also got MSTSC to open as the shell instead of Explorer but I'd prefer it if the MSTSC that opened was from a custom RDP file I have created. I tried to specify the RDP file in the 'Custom User Interface' GPO but it doesn't seem to want to open it. I'd like to incorporate Shelly so that if the user closed the RDP window it would re-open - and also give some sort of ability to shut down the machine altogether at the end of the day!

Does anyone have a working link to Shelly and how to use it aswell? I can't seem to find anything online?

Sorry to resurrect an old thread, can anyone assist further with getting a ThinPC install to function more as a true thin client?