citrix edgesight 4.5 poc workshop - amazon web...

Citrix EdgeSight 4.5 POC WorkshopCitrix EdgeSight 4.5 POC WorkshopPaul Murray, Senior Systems Engineer, MSG EMEACitrix Systems International [email protected]

Paul Murray, Senior Systems Engineer, MSG EMEACitrix Systems International [email protected]

2© 2007 Citrix Systems, Inc. — All rights reserved

The “Flexible” Agenda• Overview of EdgeSight for Load Testing (inc. LAB)

• EdgeSight for CPS and Endpoints – Key Configurations

• Break

• How to Successfully Implement an EdgeSight POC

• EdgeSight Console Review and Guidelines

• Break

• EdgeSight Use Cases (LAB)

• EdgeSight Custom Reporting Guidelines

• Break

• EdgeSight Troubleshooting Tips

Overview of EdgeSight for Load TestingOverview of EdgeSight for Load Testing


What is EdgeSight for Load Testing?

Citrix EdgeSight for Load Testing provides a leading load-testing solution for any application delivery infrastructure that utilizes the Citrix® ICA® protocol – most notably Citrix Presentation Server™ and Desktop Server environments. The product extends the application performance visibility that Citrix EdgeSight™ possesses by introducing pre-production application performance tools.


The EdgeSight for Load Testing Solution

• Load and regression testing tool

• Records the actions of a real user

• Creates reusable, graphical scripts

• Replays the script to create user load

• Accurately simulates any number of real users

• Designed to answer Citrix customer needs


Key Drivers and Messaging

Predictability | Reliability | ScalabilityImprove application availability

Simplify capacity planning and regression testing

Understand system limits before roll out

Competitive LandscapeCompetitive Landscape


Competitive Landscape

Competitor Key Market Segment Key EdgeSight for Load Testing Advantages

Mercury LoadRunner

- Application performance management- Infrastructure management- ITIL change, configuration and release

management

- Easier to install and configure- Cost- Tailored to Citrix

Scapa Testing and Performance Platform

- Application performance testing- Diagnosis and monitoring

- Easier to install and configure- Tailored to Citrix

DeNamikLoadGen

- Application performance testing - More mature

LicensingLicensing


Licensing

• Starter Pack• 50 Virtual Users - $7500• Additional User Pack - $5000

• Evals• Provides functionality for 15 users for 30 days

• Consulting Edition• Provides 250 users for 30 days• For consulting engagements only

Component ArchitectureComponent Architecture


Component ArchitectureController• Overview

• Manages and runs the load test• Management console for the recording, editing, and playback of

scripts• Allows central monitoring and reporting

• Platform• Windows XP• Windows 2000• Windows 2003


Component ArchitectureLauncher• Overview

• Used by Controller to launch virtual users• Can be installed on any number of computers for ICA simulation

• Platform • Windows XP• Windows 2000• Windows 2003• Requires ICA Client 8.1 or above


Controller• Virtual user control• Visual scripting

Launcher• Virtual user creation and

control• Input and response to

system under test• ICA focused

Citrix Infrastructure• CPS or Desktop Server

infrastructure• Single or multiple

servers

Component ArchitectureHigh-level Architectural Overview

Concurrent ICA session limit varies with hardware platforms. Pentium 4 1 GHz Processor and 1 GB of memory will support ≈ 50 virtual user sessions.


Port Source Destination Usage

18745 Controller Launcher(s) Used to upload scripts to execute and ICA settings and credentials to be used by launchers

18746 Launcher(s) Controller Used to communicate statistics for reporting to the Controller

1494/2598 Launcher(s) Presentation Servers Default ports used by ICA during activity simulation

Component ArchitectureCommunication Flow


Component ArchitectureInter-process Flow

Record and ReplayRecord and Replay


Record and Replay Visual ScriptingOverview• Provides configurable ICA Session recordings

• Provides the ability to record mouse, keyboard, idle times, and synchronization events

• Provides an interface to modify, organize, and extend visual scripts• Simplifies script creation with a visual interface instead of

programmatic scripting commands• Allows the controlled generation and rate of adding users


Record and Replay Visual ScriptingHow does it work?1. Create a script for the load test Controller

Launcher

Presentation Server

Balanced: Attempt to keep equal number of users on each connection.

Rotate: Execute one virtual user after another, moving through all available users in the script.

Top Down: Execute users giving preference to the first users specified in a script; only execute latter users if the required concurrency level demands it.


Record and Replay Visual ScriptingHow does it work?1. Create a script for the load test

2. Record an ICA SessionController

Launcher

Presentation Server

In recording mode, ICA sessions are recorded with listeners retrieving application events.



2. Record an ICA Session

3. Input converted into visual script

Controller

Launcher

Presentation Server

Keyboard input, mouse input, idle times, and synchronization points collected from listeners





4. Modify or extend visual script

Controller

Launcher

Presentation Server

Scriptlets developed in Jscript can be inserted to extend native functionality






5. Visual scripts converted to Jscript and sent to launchers during testing

Controller

Launcher

Presentation Server






5. Visual scripts converted to Jscript and sent to launchers during testing

6. Launchers interpret Jscript instructions to simulate ICA activity

Controller

Launcher

Presentation Server

DemoDemo

EdgeSight for CPS and Endpoints –Key Configurations

EdgeSight for CPS and Endpoints –Key Configurations


EdgeSight 4.5 Infrastructure

• EdgeSight Agent• Endpoint Agent collects data on processes, system resources, and

network• Presentation Server Agent collects ICA session data in addition• Both types of agents store data in local database• Each agent type can have different collection and upload schedule

• EdgeSight Server Infrastructure• Web Server (includes Web Console)• SQL Reporting Services• Database Server (SQL Server 2000/2005)• License Server


Collecting Data on Agent Machine

• EdgeSight monitors all processes, network, and system resources • No instrumentation necessary• Advanced per-process data is captured

• Local firebird database stores all data• Data collected every five seconds and placed into virtual memory• Data then stored into local database every five minutes• Data is aggregated into hourly data and sent to EdgeSight Web

Server (once a day by default)• Permits offline operation of agent from server


Systems Management Integration

(OpenView, MOM, Tivoli)

EdgeSight Server• Business rules• Data aggregation

and analysis• Centralized agent

administration

EdgeSight 4.5 Architecture

End User Devices

Presentation Server Infrastructure

EdgeSightEndpoint Agent• Non-intrusive self-

configuring agent• Continuous data

collection

EdgeSightCPS Agent• Rich, per-user session

data capture• System level metrics• Server capacity reporting

EdgeSight Console• Web-based UI• Real-time alerts• Root-cause• Historical trending

Citrix License Server• Platinum Products

Licensing

ES

ES


Monitoring Applications

EdgeSight AgentHow does agent monitor? Anyway it can …

Start/Stop Faults/Errors PerformanceTasks/Usage Trace Events

Firebird DB

Interception through DLL injectionApplication performance data polled against PerfmonInstrumented via application API calls

Perfmon data persisted every 5 seconds for Endpoints, 15 seconds for Presentation Server and later consolidated into 5-minute slices.

Application developers can tie in directly to EdgeSight monitoring.


System Monitoring


Configuration Event log PerformancePlug & Play

Firebird DB

Asset info (WMI) & disk space monitored by scheduled workers

HW events captured through Windows device change notification System performance data polled against Perfmon

Applications

Event Log error entries derived through callback notifications

Perfmon data persisted every 5 seconds for Endpoints, 15 seconds for Presentation Server and later consolidated into 5-minute slices.


Monitoring the Network


Volume Delay Stats

Firebird DB

Interception through Dll injection allows monitoring of socket connections (System-wide network statistics also retrieved through Perfmon)

Applications

System


Presentation Server Environments


Session start/stop

User logon/logoff

Firebird DB

ApplicationsSystemNetwork

CPS Configuration

Session Performance

Session/user info Gathered through Winlogon or TS APIs

ICA performance metrics retrieved through “EUEM” subscription Configurations such as published apps retrieved through MFCOM


Payload data stored in local data folder from where it is retrieved and processed by EdgeSight Script Host (RSSH).RSSH uploads payload data using ADO.NET to SQL Server database.Payload data is compressed and sent to Web component using HTTP/HTTPS. ≈ 80KB of data transfer per dayCore service queries local database and aggregates polled payload data into 60-minute chunks.

Core Service(rscorsvc)

Database Server

RSSH

Firebird DB

Local File System

IIS

Agent ServerWeb Server

SQL Server

EdgeSight AgentData Upload Process

IPC

HTTP/S

ADO.NET

HTTP/S

Agent first contacts server to find out what data is requested based on when last successful upload occurred


EdgeSight Key Configurations

Department

Workers

Alerts

AgentLogical structure for organizing agents

ALL Agents must be tied to a department


Departments

• Overview• Groups similar devices• All devices share the same agent configuration, worker configuration,

and alerts

• Factors that can influence need for departments• Use of both Endpoint Agents and Presentation Server Agents• Use of both Desktops and Laptops• Presentation Server load managed groups• Time zone differences among agents• Device operation times


Departments Considerations

• Inheritance scheme for configurations• Default configurations can be deployed to top-level departments• Child departments will inherit the top-level configurations unless a

specific configuration is applied to the department• Specific configurations replace the top-level configuration (they are

not aggregated)

• Alerts aggregated between parent and child departments• Default alerts can be applied to top-level departments• Specific alerts can be applied to child departments• Child departments will use both sets of alerts



Department

Workers

Alerts

AgentControls agent behavior such as the data collection schedule


Agent Configuration

• Define general agent behavior• When to collect data? (days and times)• How long to store uploaded payload data in local database?• How long to store non-uploaded payload data in local database?• Monitor plug-and-play devices?• How many processes and sessions to monitor simultaneously?• Which executables to exclude from monitoring?• Time to wait between running workers (in seconds)?

• Default configurations supplied for Endpoint and Presentation Server agents


Default Agent Configurations

• Endpoint Default Agent Configuration• Monitors Monday through Friday 7am to 7pm• Stores uploaded data for 3 days• Stores non-uploaded data for 29 days (allows for offline use)

• Presentation Server Default Agent Configuration• Monitors every day of the week (24/7 schedule)• Stores uploaded data for 3 days• Stores non-uploaded data for 5 days


Agent Configuration Licensing Settings

• EdgeSight Agents on Presentation Server point to the Presentation Server license server by default• If this license server is not at the 4.5 level or does not contain

EdgeSight licenses, these agents need to be point to a different license server

• Agent Configuration licensing settings are used to point EdgeSightagents on Presentation Server to a custom license server if needed


Agent Configuration Basic Settings

• Key settings include…• Days to keep in database• Max days to keep in database• Data collection start/end days and times


Agent Configuration Advanced Settings

• Only modify under proper guidance!

• Key settings include…• Process count and session count thresholds• Executable exclusion list


Agent Configuration Considerations

• Agent Configurations should be different for Endpoint and Presentation Servers agents• Differences in Hours of Operation• Use default Agent Configurations as starting point

• Agent configurations not applied to device until:• They have been assigned to a department • The device checks its configuration on the server on a scheduled

basis (default is once a day)

• Departmentalize Agents• Allows different data collection schedule• Use default agent configurations or create custom ones



Department

Workers

Alerts

Agent

Controls when the agent will do its scheduled operations including configuration checks and data uploads


Worker Configuration

• Define when the agent should perform tasks• When to upload data?• When to download configurations?• When to collect asset history of device?• When to cleanup files for fault reports?• When to calculate drive space?• When to perform local database maintenance tasks?

• Six customizable workers


Worker Configuration

• Each worker has one or more worker schedules• Worker schedules define the times for performing tasks• Default schedules are provided & can be modified

• Configuration Download & Performance Upload• Unique workers - run on randomized schedule• Specify time range for worker to run (e.g. 7pm – 11pm)• Run when machine is idle for 2 minutes • Will force themselves to run after 2 days (if there is no idle time)

• Pre-configured worker configurations for Endpoints and Presentation Server


When Do Workers Run By Default?Worker Name Endpoint Default worker

configurationPresentation Server Default worker configuration

Asset History Every 10 hours between 7am to 7pm

Every 10 hours between 7am to 7pm

Configuration Check

Once a day at 6:30am Once a day at 6:30am

Database Maintenance

Twice a day at 5am and 6:30pm

Twice a day at 4am and 6:30pm

Drive Space Calculation

Once a day at 4pm Once a day at 4pm

Fault Report Cleanup

Once a day at 11:45pm Once a day at 11:45pm

Performance Upload

Once a day between 7 –11pm

Once a day between 5 – 9 am

Once a day between 7 – 11pm


Worker Configuration Considerations

• Worker Configurations should be different for Endpoint device versus Presentation Servers• Inherent scheduling differences

• Schedules should be tailored towards when…• Devices are operating• Users are on and off the device• Presentation Server is being utilized by users

• Configurations not applied to device until:• They have been assigned to a department • The device checks its configuration on the server on a scheduled

basis (default is once a day)



Department

Workers

Alerts

Agent

Specifies which metrics to send immediate notification to EdgeSightserver and corresponding response action.


Alerts

• Provides immediate notification of agent events• When did the CPU spike over 80%?• When did a certain error appear in the event viewer?• When did a process hang on a device?

• Alert “Rules”• Defines the events that should trigger as alerts• Four types: Application, System, Network, & Presentation Server

• Alert “Actions”• Send email to an administrator or send SNMP trap to 3rd party tool• Is fired when an alert is received by the EdgeSight server


Alert Configuration Settings

• Select the alert rule and Define the conditions


Without planned response, agent works for no other reason than to generate the alertHave console Administrators focus on problem, not wading through alerts to find the problemDetail data is groomed on the agent in approximately 4 hour chunksForces database to perform extra table scans, equating to extra CPUDuplicate rules are not combined and must each be evaluated

Alert Rules Considerations

• Minimize use of “Not Like” in performance alerts

• Avoid creating duplicate rules

• Consider historical reports for performance alerts

• Don’t create alert rules without a planned response

• Don’t create blanket alert rules

• If response slower than 4 hours, consider reports instead

Use performance alerts only for actionable conditions


Agent Deployment Considerations

• Deployment challenges• Agent installations require both Company and Department settings• Agents with improper Company settings placed in Unmanaged

Devices • Agents require a reboot after installation

• Department structure within Web Console can be synchronized with Active Directory• If endpoint devices are organized within Active Directory OUs, agents

can be organized within same structure• Use SYNC_AD_TREE=1 in agent command line installation• Departments do not need to be pre-configured within the Web

Console



• Command Line Installations• Essential for SMS / IM deployments• Sample agent installation on endpoints (with AD Sync)

• msiexec /i EdgeSightEPAgent.msi /q COMPANY=“Citrix" SYNCH_AD_TREE=1 SERVER_NAME=CES45

• Sample agent installation on Presentation Server• msiexec /i EdgeSightPSAgent.msi /q

COMPANY=“Citrix" DEPARTMENT=“NYC\Presentation Servers" SERVER_NAME=CES45



• Ensure project success factors• Stagger agent rollout!• Prior to agent deployment, ensure Anti-Virus is correctly

configured on both the EdgeSight server and agent devices• Agent installations require a reboot, keep this in mind to

minimize impact on user

BreakBreak

How to Successfully Implement an EdgeSight POCHow to Successfully Implement an EdgeSight POC


Successful EdgeSight POCs

• Who has already run a POC

• Introduction to an EdgeSight POC• Success Criteria• Console Reviews

• EdgeSight Quick Start Guide• Basic Setup• AV Configuration• Alerts

EdgeSight Console Review and GuidelinesEdgeSight Console Review and Guidelines


Objectives for next 45 minutes

• Pass on experiences of Console Reviews• What goes well• What goes wrong

• GotoMyPC Session

BreakBreak


C:\ES45W…

EdgeSight Use CasesEdgeSight Use Cases


EdgeSight Use Cases

Accelerated Application Support

Device Health & Capacity Planning

Presentation Server Farm Health

Issue Resolution

EdgeSight Use Cases –Issue ResolutionEdgeSight Use Cases –Issue Resolution


Issue Resolution Key Scenarios

• “What just happened?”

• Device status at time of issue

• Asset change description

• Resource intensive processes

• Troublesome servers


• Remember! Users see the effects, not the cause

• Consider the analogy:• You throw a rock (the root cause) into a lake• The rock creates ripples (the symptoms) which has impact on the lake• End-users notice the ripples but not the rock• EdgeSight will be able to detect the ripples and filter through the ripples

to find the rock

Issue Resolution Understanding reported issues


• First focus on real-time data• Obtain the name of device the issue is reported on• Use remote reports to look at “point in time” environment state• Key starting places are:

• Real-time Remote Alerts• Real-time Remote Network• Real-time Remote System

• Use these “peripheral metrics” for further troubleshooting research

• Next focus on historical data• Is symptom one time event or reoccurring (two weeks data)• Analyze asset reports to discover environment changes

Issue Resolution Report Analysis


• Leverage Remote Reports

• Drill down into process reports to determine the “point-in-time” of the symptom (i.e. a specific application error)

• What you will find:• Real-time access to “What

just happened?”• Complete error message and

metrics on what happened leading to the event

• Complete information gathered, no need to try and reprobduce the problem

Issue Resolution Remote “point in time” sample

EdgeSight Use Cases –Accelerated Application Support

EdgeSight Use Cases –Accelerated Application Support


Accelerated Application Support Key Scenarios

• EdgeSight can provide detailed insight into applications• Application performance trends, usage, network impact• Determine when applications launch, hang, terminate,

and fault• Crash analysis for faulting applications

• EdgeSight provides re-active and pro-active measures for supporting application issues


• Users report application issues to Help Desk which need to be reacted to

• Application issues are typically with…• Device (low CPU, RAM, etc.)• Network (congestion or un-responsive backend servers)• Application (error, fault, hang, crash)

• What can I do?• Use real time reports to view data on device directly

• Real-time > Remote > Reports, focusing on System / Processes in a “where-is-the-issue-not” approach to troubleshoot the scenario

• Real-time > Remote > Alerts, to obtain recent alerting events on the device

• For application crashes, look at the crash analysis reports

Accelerated Application Support Reactive Measure


• Run-time crash analysis for any windows application in the environment

• Easy access to standard mini-dump file which can be forwarded to application developers

• Complete information gathered, no need to try and reproduce the problem

Accelerated Application Support Application Crash Analysis


• Administrators can provide pro-active support for an application by using historical reports for trend analysis

• What can I do?• Focus on historical process reports

• Performance summary for a process• Stability summary for a process• Network summary for a process

• Analyze “TopN” type report categories for processes• Drill down for more details

Accelerated Application Support Proactive Measure


• Actual end-user application usage for any application running in the environment, not just where it is installed.

• Administrators can now make purchasing decisions based on actual usage information.

• Long-term records can be kept to make sure that the organization has maintained compliance with various license agreements.

Accelerated Application Support Application monitoring sample

EdgeSight Use Cases –Device Health and PlanningEdgeSight Use Cases –Device Health and Planning


Device Health & Capacity Planning Key Scenarios

• Can hardware support new technologies, i.e. Vista

• Application rollout support

• Ongoing device stability

• Device upgrades and planning


• Misconception – Good performance = solid health

• Performance metrics determine physical strain …• A Presentation Server operates consistently at 30% CPU utilization

when hosting 40 users• With pilot testing, load is increased to 60 users and CPU utilization

only jumps to 50%• … BUT the number of process faults and errors on the device triples• Device handles the load, but not operating nominally• Device is not healthy!

• General practice …• Review device stability reports AND• Device CPU/Memory performance reports

Device Health & Capacity Planning Device Stability is Great Health Gauge


• Leverage real-time dashboard• Identify device group:

• Devices exhibiting issues – (Troubleshooting)• Devices undergoing testing – (Health Check)• Devices queued for optimization – (Capacity Planning)

• Identify metric set for examination• Select among key performance and CPS session count metrics• Only choose metrics that are needed

• Review historical summary reports• Focus on Device / Process / Presentation Server Reports• Focus on Stability reports• Focus on TopN report types

Device Health & Capacity PlanningReport Analysis


• Weigh in performance metrics to balance physical strain for health and capacity planning considerations

• Measure “operational consistency” across key groups of devices

• Leverage the utility as a “initial investigation” point - Further drill down into metrics rooted from the dashboard

Device Health & Capacity PlanningReport Analysis – Real-time dashboard sample


• Overall view of endpoint performance across the environment

• Proactively find problems instead of waiting for users to call

• Drill though to find problematic devices

• Determine if devices are capable of supporting additional software or upgrades (such as Windows Vista)

Device Health & Capacity PlanningReport Analysis – viewing historical summaries

EdgeSight Use Cases –Presentation Server HealthEdgeSight Use Cases –Presentation Server Health


• Infrastructure Health• Key Processes - IMA, XTE, Winlogon, etc.• Network communication, Application issues, Event Log issues

• Login Time Issues• Understand where in the chain bottleneck is occurring• Client and/or server side details

• Slow ICA sessions• Process hogging CPU• Low RAM/CPU on servers• Network bottleneck

• Printing Issues• Printer Auto-Creation issues• Spoolsrv resource consumption

• Capacity Planning• Are servers adequately handling the user load?

Defining “Presentation Server Health”


• Real-time Dashboard• View graphical snapshot of key Presentation Server metrics• Data updated every minute

• Remote reports• Access agents directly on Presentation Server devices• Analyze detailed EUEM metrics for logons and sessions

• Historical reports• Allows for Post Mortem, Impact and Trend analysis

• Alerts• Provides immediate notification to core Presentation Server issues• Any CPS event log entry can be sent as an alert • Use Alerts Console to gain graphical depiction of alerts

How to Monitor Presentation Server Farm Health


• What to Monitor• Windows Logon Service – winlogon.exe• Windows Print Service – spoolsrv.exe• Citrix IMA – imasrv.exe• Citrix XTE Service – xte.exe• Citrix Print Manager Service – cpsvc.exe• Citrix License Server Service – lmgrd.exe, citrix.exe

• How to Monitor it• Real-time reports provide detailed data on these processes• Historical reports provide performance trends on these processes• Alerts can indicate when certain events written to the Event Log

• TSCal Compliance - Event ID 1003/1004 TS Licensing Errors • Licensing Errors – “No licenses installed …”

• Alerts can also indicate when core processes have spike, hang, or terminate

Presentation Server Farm HealthMonitoring Infrastructure Health - Processes


• What to Monitor• Citrix IMA Service – Port 2512• Citrix License Server – Port 27000• Citrix XTE Service – Port 2598• Data Store – MSSQL, Oracle, ODBC

• How to Monitor it –• Use real-time reports on how server utilizes network• Use alerts to determine when network events occur in real-time

• IMA – Port 2512 – Host Unavailable 10060• License Server – Port 27000 – Host Unavailable 10060• Citrix XTE Service – Port 2598• Data Store – MSSQL, Oracle, ODBC – Port/Server name

Presentation Server Farm HealthMonitoring Infrastructure Health - Network

EdgeSight Custom Reporting GuidelinesEdgeSight Custom Reporting Guidelines


Understanding the Components

• Historical Reports in EdgeSight are generated by Reporting Services• Report Definition Language (RDL) files is the medium in which

Reporting Services outputs reports

• RDL File Modification = Custom Reports!

• RDL Files Consists of Two Knowledge Sets:• XML Formatting – governs how data is displayed to the page

• i.e. charts, graphs, tables, etc.• SQL Queries – governs what data is displayed to the page

• i.e. specific metrics, filtered data, data types etc.


Starter Steps for Creating Custom Reports

• Modify an existing report• Navigate to any report within• the EdgeSight Console• Select Properties > Download• Make modifications as needed

• Create a new report with Reporting Services• Possible after EdgeSight Reports have been uploaded into Reporting

Services• Conducted during initial console configurations

• Templates available via Reporting Services Web Console to generate reports and modify later


Report Customization Methodology: Analysis and Design

• Define requirements for report modifications• Report modification should always be based off of reoccurring

business needs• The Question: What data needs to be displayed?• Processes? Devices? Network? Stability? Performance?

• Once identified, determine data aggregation and graphical representation to meet that need• The Question: How the data needs to be displayed?• By Day? By Hour? TopN? Chart? Summary?


Report Customization Methodology:Build / Test and Rollout

• Obtain RDL File for Customization• From EdgeSight Console – Leverage existing reports• From Reporting Services – Leverage existing templates

• Apply Design Changes• XML Formatting changes – Requires understanding of how RDL file

XML layout is structured• SQL Query modifications – Requires understanding of the SQL

Query

• Upload Report• Administrative permissions required• Run report to test customization


Report Customization Tips and Tricks

• Key RDL File Tags for Customization:• Locate the <CommandText> tag in the query section

• This section contains the SQL query used to populate the report with data.

• Edit the SQL query based on the previously defined requirements.• Locate the <Fields> section and edit the field names• Locate the <DataField> values as required to match the data fields

specified in the query• Locate the <Description> tag and edit the report name.

• The report name should be unique


Report Customization Tips and Tricks

• EdgeSight Schema Vs. Views• Do not query against the EdgeSight Schema• Querying against the EdgeSight Schema may result in improper

database calls which can damage the EdgeSight database• EdgeSight Schema is not consistent between versions – a custom

report in 4.2 will most likely not work in 4.5• Leverage EdgeSight Views instead• EdgeSight Views are stored procedures and will protect private

components to the EdgeSight database• EdgeSight Views ensures consistency between versions

BreakBreak

EdgeSight Troubleshooting TipsEdgeSight Troubleshooting Tips


Common Troubleshooting Tips

• Cannot upload reports• Using the “RSUSER” account, try to login directly to the Report

Manager. http://<servername>/reports• Verify Group Policy and Reporting Services permissions for the

account• http://support.citrix.com/article/CTX111313

• Agent does not register with server• Verify Software Requirements

• Ensure SQL Client Tools are installed for Dual Server Deployments

• Verify Server Name and Company name• http://support.citrix.com/article/CTX111043

• Remote Functions do not work• Verify correct Remote Security options have been set

• http://support.citrix.com/article/CTX111046

http://support.citrix.com/article/CTX111313





• License Server Issues• Log into the License Server Management Console and verify licenses

are correctly installed.• http://support.citrix.com/article/CTX111870

• EdgeSight Agent consuming high resources• Ensure that Anti-Virus configuration is correctly set, then re-check it


• EdgeSight Agent Worker Function Log Files• Understand worker functions







• Real-Time Alerts Not Reporting Up• Ensure the Real-Time Alert in question has been properly configured

and applied to its respective department• Ensure ASP.NET 2.0 is installed and designated as the primary

version in the IIS Manager• Ensure that Microsoft Message Queuing has been installed and its

service is enabled. If this service is disabled via a Group Policy, Real-Time Alerts will not function even if you enable the service manually!

• EdgeSight Server Compatibility Considerations• Isolate EdgeSight Server by installing it on a server without other web

applications

citrix edgesight 4.5 poc workshop - amazon web...

Documents