- New Features for EdgeSight 5.4
- Known Issues and Fixed Issues in EdgeSight 5.4
The following is a list of known issues in this release. Read it carefully before installing the product.
Incompatibility Between McAfee Host Intrusion Protection (HIPS) V7.0 and the EdgeSight Agent
There is a known incompatibility with the McAfee Host Intrusion Protection (HIPS) V7.0 and the EdgeSight Agent.
Workaround: Do not install the agent on devices where this McAfee firewall is running. If McAfee HIPS is required on a computer running the EdgeSight Agent, please contact McAfee support for details on how HIPS can be configured to avoid this issue.
EdgeSight Agent Should Not Be Installed on Same Machine as the EdgeSight Server
The EdgeSight Agent should not be installed on the same machine hosting the EdgeSight Server. Problems with opening and saving payloads will occur on the server if the agent is subsequently uninstalled. Re-installing the server fixes this problem.
EdgeSight Agent Should Not Be Installed on Same Machine as the EdgeSight Agent Database Server
The EdgeSight Agent should not be installed on the same machine hosting the EdgeSight Agent Database Server due to registry issues. Uninstalling the agent and re-installing the server fixes this problem.
EdgeSight Web Server Only Website on Selected Machine
As a best practice, the EdgeSight Web Server should be the only website on the selected machine. Hosting multiple websites on the EdgeSight Web Server machine is not recommended and may cause the EdgeSight installation or update to fail.
EdgeSight Server Installation Fails If Database Name Contains a Dot (.)
The EdgeSight Server install fails if there is a dot (.) in the database name. See Installing EdgeSight Server and Microsoft SQL Server documentation for information on valid database naming.
EdgeSight Server Should Be Installed Before the License Administration Console in a Single Machine Installation
If the License Administration Console and EdgeSight Server are installed on the same machine, install the EdgeSight Server before installing the License Administration Console. Installing the License Administration Console before installing the EdgeSight Server will result in the inability to access the EdgeSight Server web site.
Uninstalling EdgeSight Server on Windows Server 2008 When Using Non-Standard IIS Web Port
Attempting to uninstall EdgeSight Server on Windows Server 2008 through Add/Remove Programs when using a nonstandard IIS Web port (for example, port: 94) will fail.
Workaround: Run setup.exe and select Remove, or change the Web port to the default of 80, uninstall using Add/Remove Programs, then change the port back to the original setting.
Japanese Character Display Issues
Japanese window title strings are not displayed correctly in Active Application Monitoring controller scripts when used together with XenApp 5.0 and XenApp Plug-in 11.000. If you wish to use this configuration, please update the Plug-in version to 11.100 or higher, by downloading Desktop Receiver - Version 11.100 or higher.
Recording or Editing Scripts to Replay Input of Japanese Characters Not Supported
Active Application Monitoring does not support recording or editing scripts to replay input of Japanese characters. This is a design limitation. For more information, please see http://support.citrix.com/article/CTX119267.
Desktop Not Properly Sized When Using ICA Client 11 and Windows 2008
When using the ICA version 11 client to connect to Windows 2008, the display of the desktop is not properly sized. This is a known ICA version 11 client issue and is currently being investigated.
Only ASCII ICA File Names are Supported
Only ICA files with ASCII names should be used for EdgeSight Active Application Monitoring connections. ICA files with non-ASCII character names may prevent users from recording and replaying scripts.
Only ASCII Launcher Names are Supported
Only ASCII Launcher names are supported. If you enter a non-ASCII Launcher name, the Could Not Connect to Launcher message box is displayed.