You have two installation options to execute Operations Sentinel under control of the Terminal Services for Windows environment.
One option is to install Operations Sentinel server on the Terminal Services server. See Figure E-1. When using this option, you are running both the server and workstation components of Operations Sentinel on that server. This has the advantage of being simpler to install and to manage but increases the processing load on the server.
Figure E-1 shows this environment with a firewall logically positioned between the workstation of the user where the Terminal Services client is executed and the Operations Sentinel server that is running the server components and the workstation components.
The illustration shows two Operations Sentinel servers; however this is not a requirement. You can have one, two, or more, depending on your needs. Similarly, you can have one desktop client or multiple desktop clients, restricted only by your Terminal Services license and your needs. Also, there is no restriction on the number or type of systems you can monitor other than that imposed by your Operations Sentinel license. Note that the desktop clients connect to the Terminal Services server on the Operations Sentinel servers through port 3389 (default). Terminal Services automatically secures this connection through encryption. If you use a firewall between your Operations Sentinel users and the Operations Sentinel servers, you must configure port 3389 for pass-through.
