|
From 1 to thousands of monitored servers, ObserveIT can be deployed in many flexible scenarios, on virtual machines or on physical servers alike. Depending upon your requirements, the ObserveIT components can be installed on one server, creating an “All in One” solution, or on separate servers, achieving process, networking and security isolation.
The following page describes some of the most common deployment scenarios.
Small implementations
On the ObserveIT Server side, for a small implementations of ObserveIT consisting of 1 to up to 100 monitored servers, clients will usually want to install one server running the ObserveIT Application and the ObserveIT Web Management Console + a local installation of Microsoft SQL Server. This server can be a physical server, but it can also be a virtual machine running on a typical virtualization solution.
Medium-size implementations
For medium-size implementations of ObserveIT consisting of a few hundreds of monitored servers, clients will usually want to install one server running the ObserveIT Application and the ObserveIT Web Management Console, and another different server running an instance of Microsoft SQL Server.
Integration with LDAP
Active Directory connectivity is not part of the ObserveIT installation requirements, which means that ObserveIT can be deployed both in workgroup and in an Active Directory-based domain.
When deployed in a workgroup installation scenario, ObserveIT Console Users are created locally in the ObserveIT Web Management console. This means that you will need to manually create a Console User for each user that requires access to the ObserveIT Web Management Console.
However, it is possible to create a connection between the ObserveIT Application and Web Management Console server components and an external LDAP server, such as a Microsoft-based Active Directory Domain Controller. This connection is an LDAP, read-only connection, in which the ObserveIT server components query the LDAP server for logon information. This way, you will be able to utilize the user accounts from within the Active Directory domain to allow them access to the ObserveIT Web Management Console.
Web Console Isolation
For large enterprise-size implementations of ObserveIT, where there is need to separate the ObserveIT Application Server components from the ObserveIT Web Console component, clients would want to install these components on separate servers.
By doing so, clients will achieve Agent isolation from a management perspective.
Large Enterprise-size Implementations of more than 1000 monitored servers
For large enterprise-size implementations of ObserveIT consisting of more than one thousand monitored servers, where there are also high-availability and redundancy requirements, clients will usually want to install two or more servers running the ObserveIT Application and the ObserveIT Web Management Console using a Load Balancing (LB) solution. These clients will also usually use a cluster-based implementation of Microsoft SQL Server.
Remote vendor and remote privileged user access implementation
This is one of the most typical deployment scenarios for ObserveIT. For remote vendor and remote privileged user access implementation scenarios, as well as for remote user access when there is need to visually record all the actions that are performed on the corporate servers from the remote locations, we recommend using a VPN or SSL VPN + Terminal Server or Citrix Server combination. In this scenario, remote connections will use either a VPN or SSL VPN remote connection and once logged in, will connect to the Terminal Server(s) or Citrix Server(s). On these machines, the administrator will publish either just the applications required for the remote users' work, or the entire desktop, based on the company's security policies. The ObserveIT Agent will only be installed on the Terminal Server(s) or Citrix Server(s), capturing all remote sessions on these machines.
|
Products Overview
