Xenapps Troubleshooting Blog

http://citrixtips.com/xendesktop-farm-migration-utility/#

Slowness reasons what is your environment ? - Changes . check Last Application Change, Network changes, OS changes patches, updates -  Roaming profiles , local , hybrid ? -> check the profile server - Terminal server event ID -  Fileserver                -where is the fileserver with the profiles located. ((so it's profile size isn't very big)                - Process CPU utilization                 -Teaming and bonding are specific name for Ethernet network,                 -load balancing -   DC/ DNS  (domain controller) -  SAN ( disk responsive time) ,- User connections (Disk Queue Length ,Disk Transfer Time) -  Antivirus check Logs malware ...

Citrix Web Interface - Client Communications The diagram below shows the client communications when accessing Citrix XenApp via the Citrix Web Interface: Client device utilize a Web browser to authenticate to the Web Interface. 1. The Web server reads users’ credentials and forwards the information to the Citrix XML Service on servers in the server farms. The designated server configured with Web interface console acts as a broker between the Web server and the other servers in the farm. 2. The Citrix XML Service on the designated server retrieves from the servers a list of applications that users can access. These applications comprise the user’s application set. The Citrix XML Service retrieves the application set from the Independent Management Architecture (IMA) system. 3. The Citrix XML Service then returns the user’s application set information to the Web Interface running on the server. 4. The user clicks an application icon in the HTML page. 5. The C...

■Application Performance Monitoring (powered by Citrix EdgeSight) ◦EdgeSight Agent to Edgesight Server - TCP 80/443 (Payload and alerts) ◦EdgeSight Web console (non-IMA) to RSCorSvc on EdgeSight Agent - TCP 9035 ◦EdgeSight Agent internal communication - TCP 9036 (client-side database) NOTE: After EdgeSight 4.5, replaced with IPC) ◦EdgeSight database - SQL 1433 (configurable) ■Client-side Application Virtualization - ◦Streaming Client to Application Hub (File Server/Share) - SMB 445 ■EasyCall - ◦To client - HTTP(S)-TCP 8443 (PSync) ◦To Admin console (non-IMA) - TCP 443 ◦To LDAP Directory- TCP 389 ◦To PBX - port varies by vendor ■Independent Management Architecture (IMA) Services - TCP 2512, 2513 ■Licensing Service - TCP 27000, 27009 (configurable) ■Server-side Application Virtualization ◦Management Console (Using IMA) - TCP 2512, 2513 ◦Application requests - TCP XML 80, 8080 or 443 (configurable) ◦Access to Applications Virtualized on the Server - ICA-...

Troubleshooting Citrix Slow Performance Issues    Thursday, 29 May 2008 11:32 Chris Bradford Troubleshoot Citrix / Thin Client Performance'   After a long project that was aimed at improving Thin Client performance I though I would post my experiences and solutions in order to aid those in a similar situation.     Citrix Server Performance Improvement I was recently tasked with improving a Citrix XP and PS 4.5 Farm’s performance; by no means was this simple project which I could simply throw more servers at the farm hoping to resolve the issue.   By far, the most useful tool in diagnosing slow logons is the userenv.dll debugging available in your Windows out of the box. This will really spell out where your problem is coming from.   For further information read this link: http://support.microsoft.com/kb/221833   External File Server Performance External file servers, especially servers holding roaming user profiles can cause significa...

The Ultimate Guide to Terminal Server Printing - Design and Configuration Written on Feb 02 2004 Filed under: Third Party Software, Printing, White Papers 131,143 views, 86 comments ________________________________________ by Brian Madden This paper is excerpted from the book Terminal Services for Windows Server 2003:Advanced Technical Design Guide, by Brian Madden and Ron Oglesby. At some point during your Terminal Server system design you'll remember that your users will probably want to print something sooner or later. Printing is an important function to users within their Terminal Server sessions, yet it has traditionally been the biggest nightmare for administrators of server-based computing systems. Ideally, printing from applications via RDP sessions should be no different than printing from any other application. It should be relatively seamless to the users, allowing them to click the print button within their application, easily select a printer, and qu...