The Citrix EdgeSight product line provides the real-time visibility necessary to test, deliver, and monitor the performance of Web, desktop, and virtualized applications.
EdgeSight for XenApp and EdgeSight for Endpoints provide centralized monitoring and proactive management of XenApp servers and desktops in the enterprise. EdgeSight Active Application Monitoring (AAM) is a component that provides the ability to sample and monitor the responsiveness of virtualized applications in XenApp environments.
This article contains frequently asked questions about EdgeSight 5.0, divided into following listed sections.
Q: What versions of EdgeSight for XenApp and EdgeSight for Endpoints are currently being sold and supported?
A: For Citrix product lifecycle phases (including other Citrix products) see the Citrix Product Matrix Table at Product Matrix.
Q: Are there any known 64-bit operating system support issues in EdgeSight 5.0?
A: Microsoft’s 64-bit operating systems are supported by both server and agent installations. Refer to CTX117594 –Citrix EdgeSight Active Application Monitoring Installation Guide for details.
Note: The Active Application Monitoring (AAM) component of the EdgeSight product line will run in a 64-bit operating system. This component does not have a 64-bit installer.
Exceptions/Known problems: Refer to CTX114466 – Adobe Flash 9 Not Currently Available on 64-bit Browsers.
Q: Can EdgeSight server scale up using multiple EdgeSight Web servers across many machines?
A: You can only use one EdgeSight server to manage a set of devices (composed of an unspecified number of “XenApp farms” and endpoints).
After properly sizing the EdgeSight server, you can configure additional EdgeSight servers (with distinct separate EdgeSight components and database per server) to manage another set.
Each EdgeSight server must have a distinct set of components—Web server, database, and so on. For instance, you cannot operate two EdgeSight servers to use the same database.
Q: What is the EdgeSight server’s high availability strategy?
A: EdgeSight server is designed to not require active or passive backup in a high availability (HA) environment.
The EdgeSight agents that transfer data to the EdgeSight server contain logic to retry the data transfer. This way you can transparently recover from an EdgeSight server outage. As long as the agent data is retained (that is, not purged by the EdgeSight agent) in the various devices, no data loss occurs.
Q: The EdgeSight for XenApp farm devices cannot be moved to another department in the EdgeSight console?
A: EdgeSight 5.0 mirrors the XenApp farm structure (in Configure (tab) > Company Configuration > Device Management > Departments, department named “PS Farms”).
To maintain the same farm structure, EdgeSight does not allow the users to move a XenApp farm device.
Users who have upgraded from earlier releases of EdgeSight for XenApp (or EdgeSight for Presentation Server) can use the “Department Cleanup Wizard” to remove departments without devices. While the wizard is self-explanatory, read the online help on the page where you see the wizard for additional information.
Q: What are the Microsoft ASP.NET and Active Server Pages (ASP) requirements for the EdgeSight Web server?
A: The EdgeSight 5.0 (and EdgeSight 4.5) Web server component only requires Internet Information Services (IIS) to enable (i.e. “allow”) the ASP.net 2.0 Web service extension. The IIS setting can be found in the setting for IIS Manager’s Web Service Extension.
There is no requirement for “Active Server Pages” in IIS.
For details on other requirements, consult the Server Requirements section of CTX117594 – Citrix EdgeSight 5.0 Installation Guide.
Q: Are there any special requirements for EdgeSight 5.0 with SQL Server 2008?
A: Yes. EdgeSight requires the installation of the SQL-DMO Object component, which is deprecated in SQL Server 2005. SQL Server 2008 does not ship with this object component, therefore EdgeSight users must download it from Microsoft.
Search for “Microsoft SQL Server 2008 Feature Pack.” Usually Microsoft allows you to download a specific component in the feature pack. Look for “Microsoft SQL Server 2005 Backward Compatibility Components” within the feature pack page (for example, SQLServer2005_BC.msi for 32-bit operating systems).
This requirement is documented in the Obtaining SQL-DMO Objects for SQL Server 2008 section of CTX117594 – Citrix EdgeSight 5.0 Installation Guide
Q: Are there any special requirements for EdgeSight 5.0 if it is installed on Microsoft Windows Server 2008?
A: Yes. You must install the IIS 6 backwards compatibility component when using IIS 7. In the Window Server 2008’s Server Manager console, locate the Web server (IIS, under Roles) and select “Add Role Service.” There are specific role services that must be enabled for EdgeSight 5.0 to function properly.
Specifically, the following role services should be installed for the Web server (IIS):
Under “Management Tools” IIS 6 Management Compatibility (composed of IIS Metabase Compatibility, IIS 6 WMI Compatibility, IIS 6 Scripting, and IIS 6 Management Console).
This requirement is documented in the IIS 7.0 Components Required on Windows Server 2008 Systems section of CTX117594 – Citrix EdgeSight 5.0 Installation Guide.
Q: Which operating systems are supported by EdgeSight for Endpoints?
A: EdgeSight 5.0 for Endpoints can be installed on any Microsoft “non-server” operating systems with the appropriate minimum service pack level. In particular, the current requirement is Windows XP Service Pack 2 (or later) or Windows Vista Business Edition (or above).
Installing EdgeSight 5.0 for Endpoints on a server operating system generates a warning (or an installation failure in silent mode) and an option to continue. The supported server operating systems are Windows Server 2003 and Windows Server 2008.
EdgeSight provides targeted agent Windows (MSI) installers for 32-bit and 64-bit operating systems.
Q: Which operating systems are supported by EdgeSight for XenApp?
A: EdgeSight 5.0 for XenApp can be installed on any Windows server running XenApp.
Q: Does the EdgeSight agent installer require a restart after the installation?
A: Yes. A device restart is required after the EdgeSight installation to complete the installation process.
You can choose to delay the device restart. However, EdgeSight data is not collected until the device restarts.
Q: What happens to the EdgeSight agent data if the device crashes? Do you lose the complete five-minute snapshot or just the data collected up to that point?
A: No. The EdgeSight agent is very resilient and much has been put in place to prevent, as well as recover from behavior like this (that is, crashes). An EdgeSight for Endpoints agent maintains five-second level detail and an EdgeSight for XenApp agent maintains 15-second level detail for the most recent four hours. Data is regularly aggregated into five-minute slices. If the agent does happen to crash, it recovers and/or restarts reliably and quickly. The nature of the crash affects this whole scenario (bad spot on disk, disk full, and so on). A crash may result in a missing data sample (or two), which in effect is seconds worth of data.
Q: Does the agent monitor itself?
A: Yes. The agent does monitor its own individual processes (fbserver.exe, rscorsvc.exe, and so on) so that you can understand the impact and performance of EdgeSight itself.
Q: How often does the agent check or query the EdgeSight server for configuration changes?
A: The default configuration for XenApp agents is to run the Configuration Check worker once per hour. Endpoint agents run this worker once per day.
Q: When will the EdgeSight server recognize a newly installed EdgeSight agent?
A: Assuming that the EdgeSight server was installed prior to the installation of the EdgeSight agent, the agent must perform a number of steps before it performs its initial communication action. On most computers, these steps are completed within 10 minutes of the agent startup. These steps are only performed on the initial installation, not on upgrades.
Note: While it is possible to “force” an upload to occur during this initialization phase, doing so is not recommended. Depending on the phase of the startup, the agent may not yet have collected required configuration data. Any configuration of the agent the server may wish to make is based in part on the configuration the agent. An example of this type of configuration data is the version of XenApp an EdgeSight for XenApp agent is running on.
Q: How do you know that an agent has contacted its EdgeSight Server Web Console for the first time?
A: When the EdgeSight agent performs its initial communication with the EdgeSight server, the EdgeSight server requests a data payload from the agent. This data payload contains a number of collected data items that the EdgeSight server loads into its database and effectively registers the agent to the server. As a final step, it sends a “New Instance” email to the EdgeSight Server administrator and adds an entry to a status table that can be viewed from Configure (tab) > Server Status > Messages. If an error occurs while processing the payload, these entries are also written. The entries include potentially useful information for resolving the problem.
Q: The agent has successfully contacted its EdgeSight Server Web Console, but the agent is not in the device list. Why?
A: When the agent uploads its data, one piece of the data is the company the agent is configured with at installation time. If this company name does not match the name of the company on the EdgeSight server, the agent is listed as an unmanaged device. Unmanaged devices are listed under Configure (tab) > Server Configuration > Unmanaged Devices. You can then locate the agent device by name and manually assign it to the proper department.
Note: Company names cannot contain any of the following characters: @#$%
Q: The agent does not contact its EdgeSight Server Web Console as expected. What should be verified?
A: The agent keeps a series of detailed logs about its execution. When it performs an upload, it is doing so using a function known as a worker. Each worker has its own log, which provides detailed information about worker execution.
As a first step in validating agent communication, the network settings should be verified. One of the most common issues occurs when the EdgeSight server name is not specified as a Fully Qualified Domain Name (FQDN), but the network requires FQDN, or the server must be specified using an IP address.
Another common configuration problem is a proxied network where proxy configuration is automatic. The EdgeSight agent supports a fixed proxy server, if proxies are required on the network. If network changes are required, they can be made while the agent is running. The agent retries the communication every two minutes.
If the network settings appear correct and the agent is still unable to communicate, the next step is to inspect the various log files.
The SYS_EVENT_TXT.txt file is located in C:Documents and SettingsAll UsersApplication DataCitrixSystem MonitoringData for Windows Server 2003 and Windows XP by default. This file is sorted in C:UsersAll UsersApplication DataCitrixSystem MonitoringData for Windows Server 2008 and Windows Vista. Open the file and look for the last entry for Worker 104 running with trigger 24. The entry provides a status; if it is all zeros, the communication was successful from the perspective of the agent. If it is not all zeros, the last sentence of the error message provides the most relevant information. Under certain circumstances, the message directs you to look in the script log file. The log file for this worker is located in the EdgeSightlog subfolder, and is called Worker104_Trigger24_Inst0.log. Very detailed information can be found in this log.
If the communication was successful from the perspective of the agent, you must inspect the IIS logs to determine if there is a Web server error in processing the request. All other upload processing errors are logged in the EdgeSight server database and are viewable from the Configure (tab) > Server Status > Messages page.
Q: The agent is not reporting to the EdgeSight console. Can you force an update so the agent registers right away if it has not done so?
A: The initial EdgeSight agent upload should not be forced. The agent automatically uploads its data within 10 minutes of the initial agent startup. Any problems with the initial upload prevent any forced upload from completing. Additionally, the initial upload has “retry upon failure” logic to ensure that uploads proceed automatically once network and configuration problems preventing uploads from occurring are resolved.
Note: During the initial 10-minute period, various configuration changes are made. The agent determines its Active Directory membership and operating environment. If an upload is attempted prior to these items being processed, the agent may not register correctly with the server, or it may receive an incorrect configuration. There is also the potential for incomplete data to be associated with the agent device.
Q: Which XenApp versions are supported by EdgeSight for XenApp?
A: The XenApp Agent is supported on Presentation Server 4.0 or later, including Presentation Server 4.5 on a 64-bit Windows Server 2003 platform.
Q: Are the Endpoint or XenApp agents supported on Windows 2000 Server or Windows Server 2003 running Active Directory, SQL, Exchange, IIS, or other roles?
A: No. The XenApp agent is designed to monitor and report on XenApp functions only. The agent is designed to monitor and report on end-user systems only.
Q: How does the agent collect data on the device it is monitoring?
A: The agent runs as a service and collects performance and reliability data from a number of sources, including (but not limited to) performance counters and Windows Management Instrumentation (WMI). The data is persisted to a local database and periodically uploaded to the centralized EdgeSight server database.
Q: How does the agent send data to the EdgeSight server?
A: The agent periodically uploads a payload of data to the EdgeSight server using standard HTTP protocol. It can also be configured to use SSL. The agent can be configured to immediately send real-time alerts to the server.
Q: Which ports need to be open on the firewall between the agent and the EdgeSight server?
A: By default, port 80 (or port 443 for SSL) is used by the agent when sending its data payload.
Q: Which ports need to be open on the firewall between the EdgeSight Server Console and the agent?
A: Port 9035 is used to make a remote device connection to the agent. This includes running the Dashboard, Real Time reports, Remote Workers, or using the new Device and User Troubleshooters.
Q: How often is performance data collected and sent to the EdgeSight server?
A: The Endpoint agent collects performance data every five seconds and periodically consolidates this data into five-minute samples. The XenApp agent collects performance data every 15 seconds and periodically consolidates this data into five-minute samples. The data uploaded to the EdgeSight server is consolidated into an hourly granularity. By default, this data is uploaded to the EdgeSight server once a day.
Q: Are these data collection and payload intervals configurable?
A: No, the 5/5/60 and the 15/5/60 data persistence schedules are not configurable. The data upload schedule can be configured in the Configure (tab) > Company Configurations > Agents > Workers page in the EdgeSight Web Console.
Q: How much CPU and memory does the agent consume on the remote devices?
A: Although there may be CPU spikes, the average CPU use is only 1 or 2 percent. The Endpoint agent typically consumes 20 to 30 megabytes (MB) of RAM. The agent for XenApp varies based on the number of concurrent connections to the server.
Q: How much disk space does the agent consume on the remote devices?
A: The client-side database typically uses anywhere from 50 to 250 MB of disk space.
Q: How much network traffic is generated between the agent and the EdgeSight Server?
A: The data payload is typically 35 to 100 kilobytes (KB). The real-time alerts are approximately 200 bytes.
Q: What is required to make a remote device connection from the EdgeSight Web Console?
A: The Remote Data Viewer ActiveX control is used to connect from the browser to the remote device running the agent. ActiveX controls must be enabled in the browser. Microsoft Excel 2000, XP, 2003, or 2007 must be installed on the console computer to view the data. Port 9035 must be opened in your firewall, inbound on the client. It is possible to set up a remote security group to allow access to a remote device. Refer to CTX117593 – Citrix EdgeSight 5.0 Administrator’s Guide for details.
Q: Where does the agent store its configuration information locally? Is it in the registry, or a file?
A: The EdgeSight agent stores configuration data in three locations. The Windows registry is used to store configuration items that are machine specific and are required for successful communication with the EdgeSight server. Examples of this are the name of the company the agent belongs to, the name of the server to contact, and any proxy information required to perform the communication. All other configuration items are stored in the EdgeSight agent database or the EdgeSight.ini file. The items stored in the Windows registry are typically set once, and are supplied during the agent installation. All other configuration items are sourced from the EdgeSight server the agent is configured to communicate with, and any configuration is performed using the EdgeSight server console. By default, the EdgeSight agent obtains its initial dynamic configuration within 10 minutes of the initial run of the agent. The Configuration Check worker runs once per hour by default.
Q: When Active Directory is chosen as the authentication provider, what is the proper logon format?
A: Domainusername must be used.
Q: How do you export reports that you have pulled out from the local agent database?
A: Press the F12 key on the keyboard and it gives you an option to save reports into various formats, including Excel.
Q: Where do you find a list of default set of reports?
A: A complete list of reports can be seen from the Browse tab of the EdgeSight Web Console. Refer to CTX118497 – List of Standard Reports Included in EdgeSight 5.0 for more information.
Q: How do you find out the version of the report services you are using?
A: To identify which version of Reporting Services you have installed, type the URL of the report server (for example, http://<exampleWebServer>/reportserver). Version information is located at the bottom of the page.
Q: Can custom reports be created from the EdgeSight database?
A: It is possible to create custom reports using Microsoft Reporting Services and SQL technologies. The EdgeSight database schema and the relevant views are available in the product documentation. Custom reports can be uploaded to the EdgeSight Server using the Upload a Report page and can be viewed in the Custom Reports node in the EdgeSight Console. The maintenance and accuracy of the custom reports are the responsibility of the customer.
Q: Does EdgeSight 5.0 support SQL Express 2005?
A: No. All SQL server versions required “Standard editions or better.”
This requirement is documented in the Server Requirements section of CTX117594 – Citrix EdgeSight 5.0 Installation Guide.
Q: What is the process of upgrading the EdgeSight for XenApp and EdgeSight for Endpoints Agents? Is it an in-place upgrade or an uninstall/reinstall?
A: It is an in-place upgrade.
Q: Does a version 4.x agent work with a 5.0 EdgeSight server? What limitations come with this scenario?
A: Version 4.x agents work with 5.0 EdgeSight servers as expected. This has been thoroughly tested and is fully supported.
The only limitation is that you cannot set up any Citrix XenApp alerts for a version 4.2 agent running on XenApp.
Q: What is the migration/upgrade process for 4.x EdgeSight server implementations to version 5.0?
A: Make sure to back up the existing database prior to the upgrade installation.
All EdgeSight servers must be upgraded from the proper release level. You must not skip an upgrade. Here are the order of upgrades to complete: 4.1 to 4.2, 4.2 to 4.5, and lastly 4.5 to 5.0. Most customers are currently on the previous release, which means a simple upgrade installation from 4.5 to 5.0.
Make sure to choose the existing database (the other option is a new database) in the installation.
Note: Starting with version 4.5, EdgeSight uses SQL file groups and requires a substantial amount of space during the upgrade from the previous release. As a best practice, allow 100 percent free space of the current size of the EdgeSight database. For example, if the current database is 70 gigabytes (GB) in size, have another 70 GB available. This does not include the size of the transaction logs, which can grow to more than 100 percent of the database size. In addition, back up the current database, and restart the EdgeSight server just prior to the upgrade to free any running processes from memory.
This requirement is documented in the Server Requirements section of CTX117594 – Citrix EdgeSight 5.0 Installation Guide
Q: Can the early release program (ERP) version of EdgeSight 4.5 be upgraded to the release to manufacturing (RTM) version?
A: By design, the ERP server cannot be upgraded to the RTM server. You should completely uninstall the ERP server and agents and then reinstall the 4.5 RTM version.
Q: What about Microsoft licensing for the SQL server? Do you need a client access license (CAL) for every agent?
A: CALs are not required for every agent. EdgeSight only requires a SQL license on the EdgeSight server when using the per-processor license model. The amount of full SQL licenses depends upon your implementation of SQL Server and SQL Reporting Services. If you have a single-server architecture for the EdgeSight server, a single full SQL license is required.
Single-server architecture is when IIS, SQL Server, SQL Reporting Services and EdgeSight are installed all on one physical server. If IIS and SQL Reporting Services are installed on one physical server and SQL Server is installed on a second physical server, two separate and full SQL licenses are required. If you use a per-device model for SQL, a CAL is needed for every agent.
Q: When is the endpoint license released from the license server?
A: The endpoint license is “released” on the EdgeSight server when the device is deleted or removed from the server. This is done automatically and by default if a device has not reported up to the server for 30 days or more. You can also manually remove them in the Configure (tab) > Company Configuration > Device Management > Devices page.
Q: How is the client identified for licensing? Does it use a Media Access Control (MAC) address, unique identifier (UID), NetBIOS, or host name?
A: The client uses these device characteristics in addition to a UID to correctly identify each device. This helps to uniquely identify each device and merge duplicates if they occur. This may happen if a device is re-imaged and re-deployed.
Q: How is EdgeSight 5.0 licensed?
A: See CTX126059 – Citrix EdgeSight for XenApp Licensing.
Q: Is a full version of Microsoft Excel required on the EdgeSight server? Could the Microsoft Excel Viewer or Open Office be used instead?
A: The Excel Viewer has been tested and it does not work because EdgeSight requires full write permissions to update the spreadsheet. Hence, EdgeSight requires Excel 2000 or later.
Q: Can the 64-bit Internet Explorer access the EdgeSight Web Console?
A: No. Customers running 64-bit operating systems must use a 32-bit Internet Explorer. Refer to CTX114466 – Adobe Flash 9 Not Currently Available on 64-bit Browsers.