Product Documentation

Getting Started with SmartAuditor

Aug 09, 2013

After you perform the following steps, you can begin recording and reviewing XenApp sessions.

  1. Become familiar with the SmartAuditor components.
  2. Select the deployment scenario for your environment.
  3. Verify the installation requirements.
  4. Install SmartAuditor.
  5. Configure the SmartAuditor components to permit recording and viewing of sessions.

SmartAuditor consists of five components:

  • SmartAuditor Agent. A component installed on each XenApp server to enable recording. It is responsible for recording session data.
  • SmartAuditor Server. A server that hosts:
    • The Broker. An IIS 6.0+ hosted Web application that handles the search queries and file download requests from the SmartAuditor Player, handles policy administration requests from the SmartAuditor Policy Console, and evaluates recording policies for each XenApp session.
    • The Storage Manager. A Windows service that manages the recorded session files received from each SmartAuditor-enabled computer running XenApp.
  • SmartAuditor Player. A user interface that users access from a workstation to play recorded XenApp session files.

This illustration shows the SmartAuditor components and their relationship with each other:

In the deployment example illustrated here, the SmartAuditor Agent, SmartAuditor Server, SmartAuditor Database, SmartAuditor Policy Console, and SmartAuditor Player all reside behind a security firewall. The SmartAuditor Agent is installed on a XenApp server. A second server hosts the SmartAuditor Policy Console, a third server acts as the SmartAuditor Server, and a fourth server hosts the SmartAuditor Database. The SmartAuditor Player is installed on a workstation. A client device outside the firewall communicates with the XenApp server on which the SmartAuditor Agent is installed. Inside the firewall, the SmartAuditor Agent, SmartAuditor Policy Console, SmartAuditor Player, and SmartAuditor Database all communicate with the SmartAuditor Server.


Important Deployment Notes

Updated: 2015-05-05

  • To enable SmartAuditor components to communicate with each other, ensure you install them in the same domain or across trusted domains that have a transitive trust relationship. The system cannot be installed into a workgroup or across domains that have an external trust relationship.
  • SmartAuditor does not support the clustering of two or more SmartAuditor Servers in a deployment.
  • Due to its intense graphical nature and memory usage when playing back large recordings, Citrix does not recommend installing the SmartAuditor Player as a published application.
  • The SmartAuditor installation is configured for SSL/HTTPS communication. Ensure that you install a certificate on the SmartAuditor Server and that the root certificate authority (CA) is trusted on the SmartAuditor components.
  • If you install the SmartAuditor Database on a stand-alone server running SQL Server 2005 Express Edition or SQL Server 2008 Express Edition, the server must have TCP/IP protocol enabled and SQL Server Browser service running. These settings are disabled by default, but they must be enabled for the SmartAuditor Server to communicate with the database. See the Microsoft documentation for information about enabling these settings.
  • Consider the effects of session sharing when planning your SmartAuditor deployment. Session sharing for published applications can conflict with SmartAuditor recording policy rules for published applications. SmartAuditor matches the active policy with the first published application that a user opens. After the user opens the first application, any subsequent applications opened during the same session continue to follow the policy that is in force for the first application. For example, if a policy states that only Microsoft Outlook should be recorded, the recording commences when the user opens Outlook. However, if the user opens a published Microsoft Word second (while Outlook is running), Word also is recorded. Conversely, if the active policy does not specific that Word should be recorded, and the user launches Word before Outlook (which should be recorded, according to the policy), Outlook is not recorded.