Multiple 2X Terminal Server Agents on a single system

[edwino]

Hello,

We are using different Terminal Services Connections (each running on a seperate tcp-port) to restrict user access to specific applications and "stripped" desktops. We are currently experimenting with 2X but we would like to know if it's possible to have 2X Terminal Server Agents running, each pointing to a different port on the same server.

This way we can combine our desktops and applications (published from 2X) in the 2X Client.

We tried to create multiple agents from the 2X Console, but this didn't work (only a single Agent keeps running).

Does anybody have any experience with this?

Regards,
Edwin Oldenburg

 

[nixu]

Hi there,

Only 1 2X Terminal Server Agent can run on one Termianl Server.

I did not really understand why you should have multiple TS Agents..

If you want to restrict user access, I sugguest you use User filtering and Block any wanted TCP/IP connection using a fire wall.

Nixu

 

[edwino]

Hello,

We are currently having problems with one of our applications in combination with 2X. This problem isn't visible/an issue when we run it from a 2X Published Desktop, but only when we publish it as an App.

As part of the security we are currently (non-2X-situation) running the application as a "startup when connected" for the specified usergroup on a seperate Terminal Service Port on the same server.

When we have the possiblity of 2 Agents on the same server, I can publish the desktop (with the problematic application) through 2X (port 3388) and all other application (which run fine with 2X) through the default port (3389). In the Publish from... within the 2X Console I can then maintain from where the applications are published.

Edwin

 

[nixu]

We are currently having problems with one of our applications in combination with 2X. This problem isn't visible/an issue when we run it from a 2X Published Desktop, but only when we publish it as an App.

I suggest you contact support to have this application investigated.

When we have the possiblity of 2 Agents on the same server, I can publish the desktop (with the problematic application) through 2X (port 3388) and all other application (which run fine with 2X) through the default port (3389). In the Publish from... within the 2X Console I can then maintain from where the applications are published.

1) When installing 2X App Server and Load balancer, you can publish a whole desktop. (This needs 2X Client)

2)When installing 2X App Server and Load balancer, if you connect (using msrdp) with the gateway on the RDP port, it forwards your connection to a terminal server (more configuration is available from the console, see Console-> Loadbalancing->advanced).

So I still see no use of installing 2 TS Agents.

I think you are not solving your issues in the correct manner.

Nixu

 

[zippo]

We are currently having problems with one of our applications in combination with 2X. This problem isn't visible/an issue when we run it from a 2X Published Desktop, but only when we publish it as an App.

I suggest you contact support to have this application investigated.

When we have the possiblity of 2 Agents on the same server, I can publish the desktop (with the problematic application) through 2X (port 3388) and all other application (which run fine with 2X) through the default port (3389). In the Publish from... within the 2X Console I can then maintain from where the applications are published.

1) When installing 2X App Server and Load balancer, you can publish a whole desktop. (This needs 2X Client)

2)When installing 2X App Server and Load balancer, if you connect (using msrdp) with the gateway on the RDP port, it forwards your connection to a terminal server (more configuration is available from the console, see Console-> Loadbalancing->advanced).

So I still see no use of installing 2 TS Agents.

I think you are not solving your issues in the correct manner.

Nixu

you can publish Desktops, applications and documents at the same time.