Using non-default port #203

Activity

1. MattBeaudinQC

   self-assigned this

   on Jun 9, 2026
2. MattBeaudinQC commented on Jun 9, 2026

   

   MattBeaudinQC

   on Jun 9, 2026

   More actions

   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
3. MattBeaudinQC

   added

   enhancementNew feature or requestNew feature or request

   on Jun 9, 2026
4. MattBeaudinQC

   assigned

   DanPeterson

   on Jun 9, 2026
5. robertprimozic-art commented on Jun 11, 2026

   

   robertprimozic-art

   on Jun 11, 2026

   Author

   More actions

   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?
6. MattBeaudinQC commented on Jun 12, 2026

   

   MattBeaudinQC

   on Jun 12, 2026

   More actions

   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.