In this blog post we will cover what each of our installable agents do so you can easily plan and implement a new 2X Remote Application Server installation.
The steps covered will also come in handy in situations where it isn’t possible to install the agents remotely via the 2X Remote Application Server console, due, to for example, network issues or firewall policies which can’t be changed.
In general, when running the 2X Remote Application Server set up, the Administrator is faced with two options, the Typical Installation method which installs the basic required agents alongside the 2X ClientGateway, or the Custom Installation method where you select which particular agents are to be installed on a given machine, and if required, also the 2X ClientGateway.
The default installation generally installs the following agents alongside the 2X SecureClientGateway:
- 2X Publishing Agent
- 2X Terminal Server Agent
By selecting the Custom Installation, the Administrator can choose to install any of the following items:
Knowing what each agent does is important because it can give better insight into the agents you might want to install and help you decide which machines to install them on.
Let’s go through what a typical deployment of 2X Remote Application Server might look like first of all.
In the above scenario, we can see that we have our Farm which consists of a machine running the 2X Publishing Agent and the 2X ClientGateway. We also have a machine running the 2X VDI Agent and another one running the 2X Terminal Server Agent.
We can also see clients that connect to the 2X ClientGateway either locally over a WAN, or over the internet through the company firewall.
As you might expect, all connecting clients that are normally running an installation of the 2X Client have to connect to the 2X ClientGateway. The gateway handles incoming connections from clients.
On the same machine in the scenario above, we can also see that the 2X Publishing Gateway is installed. The 2X Publishing Agent determines what applications are made available and who can use them after the Administrator has set up 2X Remote Application Server accordingly.
Both of these agents can also be installed on a machine configured as a Terminal Server. It will require the 2X Terminal Server Agent to be considered as a Terminal Server.
Other agents that can be installed during the installation setup are the 2X VDI Agent which can be deployed to VDI hosts running a pool of Virtual Machines, the 2X Guest Agent installed on guest machines running on a VDI host and also the 2X PC Agent. The 2X PC Agent is the agent used to add a Remote PC. Remote PCs can then be published and accessed as a remote resource by users connecting via the 2X Client.
As you can see, this is quite an extensive list of agents. The brief explanation above should provide an insight in to the purpose each agent serves and demonstrate why it is important to know what each one does before using the Custom Installation method.
Further to this, you can manage these agents from the 2X Remote Application Server Console which provides an easy to use and intuitive interface to install the agents remotely. For example, an Administrator can easily add new Terminal Servers to the farm by installing the 2X Terminal Server Agent from the console.