A. ObserveIT for Servers is a client/server software application that monitors, audits and records all activities performed by people on an enterprises servers. The indexed, searchable, visual database allows those activities to be replayed to see exactly what is happening on the monitored servers.

A. People, the invisible component in IT infrastructure, are responsible for more errors and failures than software and hardware put together. ObserveIT for Servers helps to:

• Reduce Human Errors
• Reduce Mean Time to Repair
• Increase Security
• Supervise Third-Party Projects
• Improve Auditing, Compliance and Accountability
• Provide proof of user actions
• Reduce Harmful Activities
• Retain and Leverage IT Expertise
• Lower Server Documentation Costs

A. Any company that has multiple individuals with access to its enterprise servers can benefit by using ObserveIT for Servers. This is particularly true when, in addition to IT administrators, developers, project managers and consultants are able to modify server configuration.

A. ObserveIT for Servers not only monitors and captures user activity on a server, it allows context-sensitive information to be provided to users while they are working at the server console. Sticky Notes can be attached at any point in a program dialog or configuration setting to provide specific information about what to do (or NOT to do) for that situation. Users can also use the Context Search feature to get a list of previous user actions related to that configuration setting. Finally, ObserveIT for Servers can also issue an alert when a user makes a configuration choice that has been flagged as an error.

A. When a server begins to function abnormally, ObserveIT for Servers allows support staff to immediately see exactly what actions were performed on that server. Many times, a single configuration change can have unintended effects and looking through system event logs to try to identify both the problem and the cause can be time consuming. ObserveIT for Servers allows the troubleshooter to either pinpoint the cause of the problem, or rule out user error as the cause.

A. Because ObserveIT for Servers records exactly the actions that contracted employees and consultants are doing on the enterprises servers and when they are doing it, project managers can verify:

• Compliance with enterprise policies
• Actual working hours
• Documentation of deliverables and work performed

A. ObserveIT for Servers has three powerful features to help document and retain an organizations IT expertise.

• Any time a portion of a captured user session represents a best practices method or otherwise demonstrates the correct process for repeated tasks, it can be tagged and saved for training purposes.
• When additional instructions are required for any particular task, Sticky Notes can be attached at any point in a program dialog or configuration setting to provide specific information about what to do (or NOT to do) for that situation.
• The Context Search feature is available at all times to get a list of previous user actions related to that configuration setting and see exactly what choices were made.
• The servers that the user touched, to track actions that should span across multiple servers.

A. ObserveIT for Servers can integrate with other network and system management systems, to receive alerts based on thresholds/rules defined within the 3rd party system. ObserveIT for Servers will link a recorded sequence to the alert event.

A. While ObserveIT for Servers has no direct competitors, it incorporates functionality of change management, knowledge management, and security monitoring applications. One of the most important differences is how ObserveIT for Servers compares to most change management applications.
In a typical change management application, a snapshot of the monitored systems configuration is periodically taken and compared to the previous snapshot. The result is an aggregated delta of changes between snapshots including files and registry entries. For troubleshooting purposes, this can be too much information, and it can be difficult, if not impossible, to reverse engineer exactly what happened and determine how it happened.
Troubleshooting with ObserveIT for Servers starts with reviewing what actions occurred instead of looking at the result of those actions. A single checkbox in a configuration dialog can result in numerous file and registry changes. By finding the cause of the changes, the action can be reversed without having to determine exactly which file and registry entries will be affected.

A. No, this is the fundamental reason you are using ObserveIT for Servers; the ability to easily and quickly find the information you need about what is happening on your servers. ObserveIT for Servers unique, patented technology provides multiple search capabilities: context sensitive, free text and reports, that are specifically designed to allow you to pinpoint the exact actions you are interested in.

A. Yes, within the Web Console it is possible to define what the Agent is to capture, by inclusion or exclusion, almost anything: the users, applications, specific files, URLs and specific keystroke events.

A. Yes, an entire session or part of a session can be exported to a standalone executable of the video sequence.

A. Part of the ObserveIT for Servers configuration is to identify generic accounts like Administrator that require additional authentication when used to login to a server. The Agent uses ObserveIT for Servers Identification Services to prompt for additional identification and authentication before the user is allowed to proceed. All actions performed on the server are then linked to the specific user account.

A. Reports are created by querying from three main components - server, user, and a resource which can be any screen element that the user interacts with: menus, application dialog, files, etc. The following are examples of ObserveIT for Servers reports:

• List users that have accessed selected servers by date and time
• List users that have accessed selected resources such as files, applications, configuration property pages, etc.
• List resources (registry entries, applications, screens, files, etc.) that were accessed on selected servers by date and time
• List installed/uninstalled applications on selected servers
• List installed/uninstalled application by selected users

A. Any time a portion of a captured user session represents a best practices method or otherwise demonstrates the correct process for repeated tasks, it can be tagged and saved for training purposes.

A. ObserveIT for Servers can be configured to generate an alert whenever a specified resource is accessed including files, registry entries, application property pages or any other screen element. Alerts can be sent by email, pager, SNMP event, SMS or to a separate alert management system.

A. All versions of Windows 2000/2003 Server are currently supported. A version for Linux and Unix platforms is in the works.

A. The Application Server, Management Server (Web Console), Database Server can be on a single platform or distributed on multiple platforms. The ObserveIT Agent is deployed on any server that is to be monitored in the enterprise. The following diagram illustrates the components and their relationship.

A. There is no inherent limit on the number of managed instances. ObserveIT for Servers scales up and out to support as many systems as necessary.

A. Yes, there is a published set of APIs and an SDK that developers and administrators can use to integrate functionality with 3rd party applications.

A. Each of the server components can coexist with other applications using the same physical hardware platform. ObserveIT for Servers has specific configuration settings to allow integration with Active Directory, CA e-Trust and other application software.

A. In a Microsoft SQL Server database on the Database Server.

A. The Application Server is stateless and multiple Application Servers can be deployed using a load balancing router. The Database Server is based on MS SQL Server technology which supports a distributed database architecture across multiple hardware platforms. For more information, please refer to the Implementing ObserveIT in the Enterprise white paper.

A. The data is digitally signed and encrypted when it is stored in the database. Access to the data is limited by permissions defined within the Web Console.

A. The Agent and Application Server use a token exchange to prevent session hijacking and replay and to encrypt the data communication. SSL communication is also supported.

A. The Agent posts HTTP or HTTPS data to the Application Server on a configurable port. The Application Server communicates with the Database Server on the default SQL Server port (TCP 1433).

A. A user-mode executable that binds to every user session.

A. There is a health check process that polls the Agents, Application Server(s) and Database Server to verify communication and functionality.

A. Yes

A. Any user interaction with the server console can be captured and monitored whether it is via Terminal Services Client, Citrix, Remote Desktop, PcAnywhere, VNC, or NetOP. For Client/Server applications, please refer to ObserveIT for Workstations.

A. In addition to capturing the screen image for each user action, ObserveIT for Servers extracts information about the state of the operating system and the application program being used which allows ObserveIT for Servers to precisely identify what the user is doing. This information is analyzed and encoded in a standardized format that becomes the metadata stored in the Database Server.

A. ObserveIT for Servers patented technology has the ability to identify each type of user interaction (dialog boxes, configuration tabs, confirmation prompts) including the result of that action, and index it as metadata for search and retrieval. In addition to the screen information, the captured metadata provides the context for each user action performed on the server. Unlike some other monitoring software, the Agent only captures during user activity and the data is compressed to conserve bandwidth and storage.

A. All activities which require user input from either the keyboard or mouse.

A. Idle time when there is no user input is not recorded.

A. Yes, within the Web Console it is possible to define what the Agent is to capture, by inclusion or exclusion, almost anything: the users, applications, specific files, URLs and specific keystroke events.

A. In a Microsoft SQL Server database on the Database Server.

A. In addition to the screen and underlying metadata, the date, time, IP address, and user is stored in the database.

A. Please refer to the ObserveIT for Workstations product information sheets.

A. The easiest method is to use ObserveIT for Servers One-click Installation. Simply pick the destination SQL Server name and click install for a five minute installation. Click here Link to video to see a demonstration.

A. Yes, the Agent has a silent installation that will work well with most distribution applications including MS SMS.

A. Upgrades are installed over previous versions retaining all settings and configuration.

A. An existing ObserveIT for Servers client with similar resources (including systems administrators, developers and consultants) is averaging 25 GB per year with a moderate level of activity.

A. The maximum network utilization by Agent to Application server communication per session is 30KBps. This communication only occurs when a user is actively interacting with the server. There is minimal communication for health checks during idle time.

A. No, all data is communicated to the Application Server and subsequently stored on the Database Server.

A. 10 MB.

A. Approximately 5% while the user is actively interacting with the system.

A. Approximately 25MB.

A. The Agent has a watch dog mechanism that restarts the Agent if the process is ended and sends an alert to the Application Server. The health check system continually monitors all components and verifies that they are communicating properly.

A. The health check system monitors each Agent as well as the Application and Database Servers to verify that all components are functioning and communicating properly.

A. A centralized error log is accessible through the Web Console. It can be exported to send to Technical Support for troubleshooting assistance.

A. ObserveIT for Servers is designed for minimal maintenance and management but should be included in disaster recovery and business continuity operations.

A. Because ObserveIT for Servers is based on MS SQL Server architecture, standard database practices are available for archiving and maintaining data.

A. The Web Console provides a familiar and intuitive interface to all ObserveIT for Servers configuration and administration.

A. The Agents periodically poll the Application Server for configuration changes made in the Web Console.

A. ObserveIT for Servers has role based administration that limits and controls access to functionality and content in the Web Console. For example, a DBA can be granted access to view videos of sessions on a SQL Server while being restricted from access to those from Exchange or Active Directory servers.

A. Yes, each time a video is accessed a log is created with the user, IP, capture session and frames viewed.

A. ObserveIT for Servers is licensed by the number of Agents installed.

A. Please refer to the ObserveIT for Servers pricing guide.