Remote Applications

Hi folks, this is half a HAP question and half RDWeb so not sure if this is the right place. Feel free to move around if need be.

Anyway, does anyone happen to have a fully usable guide on getting this working properly? Using HAP 8.5 with good success (damn it's easy, staff love it!). Intention is to have SIMS published as a remoteapp to it. Got as far as generation an .rdp file which after reading up other threads here we got working, but only internally. Externally it doesn't find the server name.

My knowledge of RemoteApps and this area in general is very patchy at best so wasn't sure if we'd set it up right.

HAP is set up on our remote server as the default website and that seems to break RDWeb Access (couldn't access the config page for instance) - but then I still wasn't sure if we needed to even touch RDWeb if we had the .RDP file.

Obviously I'm very near clueless on this - any help would be gratefully received!

This is my SIMS RDP file, note I use a launcher program that maps the S:\ drive

Code:

---

redirectclipboard:i:1
redirectposdevices:i:0
redirectprinters:i:1
redirectcomports:i:1
redirectsmartcards:i:1
devicestoredirect:s:*
drivestoredirect:s:*
redirectdrives:i:1
session bpp:i:32
prompt for credentials on client:i:1
span monitors:i:1
use multimon:i:1
remoteapplicationmode:i:1
server port:i:3389
allow font smoothing:i:1
promptcredentialonce:i:1
authentication level:i:2
gatewayusagemethod:i:2
gatewayprofileusagemethod:i:1
gatewaycredentialssource:i:0
full address:s:{INTERNAL NETWORK ADDRESS}
alternate shell:s:||SIMS Remote
remoteapplicationprogram:s:||SIMS Remote
gatewayhostname:s:{GATEWAY SERVER}
remoteapplicationname:s:SIMS.net Remote
remoteapplicationcmdline:s:
alternate full address:s:{INTERNAL NETWORK ADDRESS}

---

Note the gateway host name, which is your server with the RDP Gateway installed

That is odd, I am also setting up rdweb apps to work over HAP and get an error when using externally.

I will be watching this thread.

Still no luck, even making the mods from your RDP file, Nick.
Made sure the RDP port is open for the server too (and confirmed).

This is (edited) ours:

Code:

---

redirectclipboard:i:1
redirectposdevices:i:0
redirectprinters:i:1
redirectcomports:i:1
redirectsmartcards:i:1
devicestoredirect:s:*
drivestoredirect:s:*
redirectdrives:i:1
session bpp:i:16
prompt for credentials on client:i:1
span monitors:i:1
use multimon:i:1
remoteapplicationmode:i:1
server port:i:3389
allow font smoothing:i:1
promptcredentialonce:i:1
authentication level:i:2
gatewayusagemethod:i:2
gatewayprofileusagemethod:i:1
gatewaycredentialssource:i:0
full address:s:servername.domain.internal
alternate shell:s:||SIMS
remoteapplicationprogram:s:||SIMS
gatewayhostname:s:{GATEWAY SERVER}
remoteapplicationname:s:SIMS .net
remoteapplicationcmdline:s:"C:\Program Files (x86)\SIMS\SIMS .net\Pulsar.exe"
alternate full address:s:servername.domain.internal

---

Works perfectly internally - hence I suspect it's something more the RD side of things.

It'll be the RDP gateway, make sure it's configured and has the SSL certificate installed that matches HAP

Got it! And tested great :D

RDP file now looks like this:

Code:

---

redirectclipboard:i:1
redirectposdevices:i:0
redirectprinters:i:1
redirectcomports:i:1
redirectsmartcards:i:1
devicestoredirect:s:*
drivestoredirect:s:*
redirectdrives:i:1
session bpp:i:16
prompt for credentials on client:i:1
span monitors:i:0
use multimon:i:0
remoteapplicationmode:i:1
server port:i:3389
allow font smoothing:i:1
promptcredentialonce:i:1
authentication level:i:2
gatewayusagemethod:i:2
gatewayprofileusagemethod:i:0
gatewaycredentialssource:i:0
full address:s:hap.school.northants.sch.uk
alternate shell:s:||SIMS
remoteapplicationprogram:s:||SIMS
gatewayhostname:s:hap.school.northants.sch.uk
remoteapplicationname:s:SIMS .net
remoteapplicationcmdline:s:"C:\Program Files (x86)\SIMS\SIMS .net\Pulsar.exe"
alternate full address:s:hap.school.northants.sch.uk

---

Basically everything is pointing externally now. No real change to configuration other than changing around some internal DNS which may or may not have had any effect (TTL is too long to warrant testing a change) - rather than having A records pointing our external domain name to our internal address (let's face it, our router does that anyway so there's no need for that to exist) we've now got a CNAME pointing external domain name to internal domain name. That's probably better practice anyway really as it forces it through DNS here.

So, job's a gooden! Thanks for the input :D

Also learned that RDP files by default use current monitor configuration, so when using dual monitor setups it throws that in for some unusual results too ;)

Odd, dual monitors works very well with RDP files and me, I can drag SIMS from one monitor to another like I do with any other application at home

Not moaning at all - it does work wonderfully, but it creates the setup on a dual monitor system and when you go to a single monitor it tries to "split" teh screen between the two. Not a problem :)

Ah, I've never tried to resume a session on a single screen.

One last annoyance I can't quite shake. There's a rogue SSL certificate being punted with the RDP file somewhere. SSL is perfect for everything else but it's got a locally signed one for our server (internal network name) which obviously is no good for external connections. Certificate being punted isn't in the list of certificates on the server on IIS nor is it called by the RDP file, digital signatures or remote gateway setup. Argh! So close to perfection.

*** Update: Found the little chuffer! Session host configuration, the little unassuming "Certificate" option down the bottom!

yep that's the one, but it needs to match the server name