Using non-default port

[robertprimozic-art]

I have 2 RDP traffic policies , one on TCP 3389 and another on TCP33891. Differences between thenm is in RDP setting where policy on 33891 does not includes banner. Reason? When publishing app with RAL I do not want that user must open a window and click OK to continue on banner.
With RDP file download this works fine. When using SCALUS, it always use RDP connection policy under TCP3389.
SCALUS is version 1.1.0.470

[MattBeaudinQC]

Hi @robertprimozic-art ,

I took a look at this, and SCALUS currently always connects using the default RDP port (3389), ignoring any non-standard port specified in the connection URI.

There are a couple of workarounds in the meantime.

The first one would be to set up a Custom RDP Template with a %Port% token .

The template file would look like this:

full address:s:%Host%:%Port%
server port:i:%Port%
username:s:%User%
alternate shell:s:%AlternateShell%
remoteapplicationname:s:%Remoteapplicationname%
remoteapplicationprogram:s:%Remoteapplicationprogram%
remoteapplicationcmdline:s:%Remoteapplicationcmdline%
screen mode id:i:1
session bpp:i:32
use redirection server name:i:1
disableconnectionsharing:i:1

Then you would update your scalus.json file to use it:

{
  "Id": "my-rdp-config",
  "Name": "RDP with custom port",
  "Platforms": ["Windows"],
  "Protocol": "rdp",
  "Parser": {
    "ParserId": "rdp",
    "UseTemplateFile": "%AppData%\\MyRdpTemplate.rdp",
    "Options": ["waitforexit"]
  },
  "Exec": "C:\\windows\\system32\\mstsc.exe",
  "Args": ["%GeneratedFile%"]
}

You should try this in a test environment before deploying anything to production.

I've tagged this as an enhancement to see about getting the change in there for this type of use case.

Matt

[robertprimozic-art]

Thank you. And what is procedure to deploy this custom template to already installed clients and how to prepare SCALUS with this settings for depoy with deployment tools?

[MattBeaudinQC]

First thing I would do is to try it in an isolated test environment to ensure it works the way that you want it to. You can update configuration files on the fly and restart SCALUS as needed to have them be applied.

Once that's done, and you've got a working setup, there are third party tools that exist where you can modify configuration files on the host machines. Test this out in a small pool of users to ensure it works. Depending on how you deployed SCALUS in the first place, it may already be available to you.