APM - RDP AppTunnel with Multiple monitors

[AlexBCT]

Hi,

I'm trying to get the RDP Application Access to pick up on multiple monitors on the client side. (normally done by adding the parameter /multimon into the command). However, when adding this into the RDP Application Access object, no luck.

You can get this to work by building your own "custom" AppTunnel, create standard AppTunnel, include application path to mstsc.exe, point to the local proxy IP and then add the /multimon parameter). Unfortunately, the AppTunnel doesn't seem to provide SSO integration (probably because it's too generic and it doesn't know how to intercept the authentication screen.

So, does anyone know how to get RDP Application Access to work with multiple monitors, or failing that, how to implement SSO on a normal AppTunnel for RDP?

Thanks in advance!

[Ryan77777]

Have you come across a solution for this?

I tried custom parameters in the Acess Policy -> Secure Connectivity -> Application Access -> Remote Desktops -> {desktop name} -> Custom Parameters

... but to no avail. I tried use multimon:i:1 and span monitors:i:1 with no such luck.

App tunnel with a /multimon parameter seems to work fine... but then like you said, SSO issues as well as local device/clipboard issues.

Hopefully with version 13 coming out soon, they've addressed some of these problems.

[AlexBCT · Accepted solution]

Hey Ryan,

I've now tested this on version 13.0 and it works! As you said, the multimon:i:1 custom parameter doesn't work in v12.x, but it now does in v13.0. Just to ensure I didn't miss anything, I tested it again on v12.x as I started to doubt myself...

To clarify for anyone else, to get multiple monitors to work in an APM RDP session in V13 APM, go to; Access -> Connectivity / VPN -> VDI / RDP -> Remote Desktops -> {desktop name} -> Custom Parameters -> Insert parameter "use multimon:i:1" (note the changed menu structure in v13)

I suspect that it has to do with the different way the RDP is now integrated in APM. It used to be part of the plugin, but in v13, the RDP tunnel is set up and the connection parameters are saved to a seperate file, which can then be opened with the native RDP client.

[Adam_Willcox]

Sorry to bump such an old topic. But I just did this intuitively, it didn't work, and my first search of the forums hit on this post telling me to do exactly what I did! Am I missing something basic? It doesn't actually need the quotes does it?

[AlexBCT]

Hey Adam,

Looks indeed pretty good to me. What's the chance that one of the above parameters is causing trouble and the RDP client doesn't reach the multimon parameter when it parses the file? (e.g. the Disableremoteappcapscheck:i:1 could be wrong?) Not too sure about them, but maybe you can try putting the multimon parameter to the top of the Custom Parameters bit and see if that makes a difference? And/or temporarily removing a bunch of them and see if only the multimon-one works?

See below the full configuration of my RDP object which get used daily, so still works 😉

[Ryan77777]

Yup... worked for me too. I even used both parameters so it'll fallback to spanning if multimon doesn't work. Pretty cool!