Branch Repeater 5.6, 5.7 & VPX

1. Branch Repeater 5.6, 5.7 & VPX Technical Presentation

2. High Definition Experience Needs Optimization and Orchestration Across the Entire Delivery System 2 3 Client Server HDX 1 Network Repeaters Gateways Controllers Receivers Citrix Confidential - Do Not Distribute Citrix Confidential - Do Not Distribute

3. Our Arrow ECS Labs Setup RouterWAN emulator 1Mbps Client Server WANem Repeater VPX172.32.1.250 Repeater VPX192.168.1.254 XenDesktopXenAppCIFS HTTP MAPI192.168.0.0/20 ReceiversonWifi Network172.32.1.0/24 XenServer Citrix Confidential - Do Not Distribute Citrix Confidential - Do Not Distribute

4. Citrix Branch Repeater | The Big Picture Citrix Repeater Plug-in for Citrix Receiver Tele-workers Mobile Users Branch Offices Data Center Applications: XenApp XenDesktop File Servers Exchange Email SharePoint ERP/CRM Branch Repeater Repeater Redundant Datacenter or Disaster Recovery Site Repeater

5. Acceleration for any user, anywhere Repeater appliances Repeater Plug-in Branch Repeater with Windows Server, and Branch Repeater

6. What’s new in Branch Repeater 5.x & VPX

7. Exchange (MAPI) Acceleration • Features • Protocol acceleration (similar to CIFS) • Compression & de-duplication of attachments • Cross-application and multi-user optimization • Supports Exchange Server 2003 and 2007 • Supports MS Outlook 2003 and 2007 • Available on all appliances and Repeater Plug-in • Benefits • Up to 50 times faster sending/receiving emails • Reduces bandwidth consumption Outlook Exchange

8. Branch Repeater running Windows Server 2008 • Features • Natively integrated Windows Server 2008 Standard Edition OS • File, print, DHCP, DNS, WINS, DFS • Read-only Domain Controller (RODC) • MMC, WMI, SCOM manageability • Benefits • Simplify IT by consolidating servers in the branch • Leverage existing Windows management tools and expertise WAN Optimization

9. Read-Only Domain Controller (RODC) • Features • Read-only AD DS database • Unidirectional replication • Credential caching • Administrator role separation • Read-only Domain Name System (DNS) • Benefits • Securely deploy a local DC in any branch location • Faster authentication and logon times for branch users • Centralized IT management and control

10. Command Center Enhancements • Features • Now supports all Branch Repeater appliances (Linux and Windows) • Benefits • Easy and cost-effective management of large number of remote sites

11. Citrix Branch Repeater Key Features

12. HDX Broadcast &HDX IntelliCache

13. HDX IntelliCache and HDX Broadcast HDX Broadcast HDX IntelliCache • Branch Staging of • Offline Apps • Adaptive TCP Flow Control • Adaptive Compression • Adaptive Protocol Acceleration • Prioritization & QoS WAN • Branch Caching of • Online Apps Repeater Branch Repeater

14. Branch Repeater Technology – HDX Broadcast • Adaptive Protocol Acceleration (Improve inefficient protocols) Adaptive Compression (Reduce application turns and data) Adaptive TCP Flow Control (Overcome loss/latency penalties) Prioritization and QoS (Prioritize critical traffic)

15. Example: CIFS Adaptive Protocol Acceleration Intelligently accelerates common application protocols Mitigates latency by reducing round trips (chatty protocols) • CIFS (File Sharing) • MAPI (Exchange) Makes compression engine application-aware • Separates headers from payload • ICA, CIFS, MAPI, HTTP, FTP, NFS

16. CIFS: Common Internet File System Most common file sharing protocol Microsoft Office, Linux Open Office, etc. Windows XP/Vista, Windows Server 2003/2008, Mac OS X NetApp Filers, EMC File System Access Drag/Drop, Read/Write, Copy, Directory Browsing CIFS

17. I want to open a file Which file? \\dog\bone\blue Who are you? John Whomever Password? “Whatever” OK, It’s open! Example: CIFS – without Branch Repeater 250ms 250ms 250ms 250ms 1000 ms

18. I want to open a file I want to open a file Which file? Which file? 1 ms \\dog\bone\blue \\dog\bone\blue OK, It’s open! OK, It’s open! Who are you? Who are you? 125 ms John Whomever John Whomever 1 ms Password? Password? 125 ms “Whatever” “Whatever” Example: CIFS – with Branch Repeater Open \\dog\bone\bluefor John Whomever,password “Whatever” 252 ms

19. Branch Repeater CIFS Performance

20. Windows 2003/2008 Server : • Set “Microsoft network client: Digitally sign communications (always)” to “Disabled” • Set “Microsoft network server: Digitally sign communications (always)” to “Disabled” Windows 2000 Server : • Set “Digitally sign server communication (always)” to “Disabled” • Set “Digitally sign client communication (always)” to “Disabled” For Windows 2008 Server Disable SMB 2.0See : http://www.petri.co.il/how-to-disable-smb-2-on-windows-vista-or-server-2008.htm CIFS Acceleration Requirements

21. Why accelerate MAPI? • Faster sending/receiving of email attachments • Lessen MAPI-related bandwidth requirements • Increase mail system responsiveness for branch office users • Help enable Exchange server consolidation • Drastically reduce idle time in sending/receiving emails • Iterations of same or similar messages by email • Optimization when different users, different applications access similar files

22. What is MAPI Acceleration? • MAPI Acceleration is: • The pipelining of MAPI-based traffic between Microsoft Outlook and Exchange. • Acceleration of the uploading and downloading of email attachments made to email messages. • The compression of message attachments.

23. What is MAPI Acceleration? • MAPI Acceleration is: • The pipelining of MAPI-based traffic between Microsoft Outlook and Exchange. • Acceleration of the uploading and downloading of email attachments made to email messages. • The compression of message attachments.

24. How does MAPI Acceleration work? • Branch Repeater detects the Outlook to Exchange handshake. • If an accelerated connection is allowed the native Exchange compression is decompressed on the server-side Repeater. • No acceleration = native compression only • The Repeater/Branch Repeater pair then apply compression to subsequent MAPI traffic. • The Outlook client initiates a MAPI connection to Exchange on TCP port 135. • User authentication and mailbox enumeration occurs.

25. How does MAPI Acceleration work? • A compression bit is flipped in the packet prior to reaching the client, notifying Outlook not to decompress the native Exchange compression. • The downloading and uploading of message attachments (messages larger than 32k) is then accelerated. • Appropriate compression is applied to obtain a higher compression ratio. • Packet header : Memory-based history • Packet payload: Disk -based history • Outlook then creates multiple connections the to Exchange server and message requests are exchanged simultaneously among the connections

26. How does MAPI Acceleration work?

27. Exchange (MAPI) Acceleration • Requirements • Microsoft Outlook/Exchange Server 2003 and 2007. • Outlook must use normal Exchange mode (no HTTP or HTTPS proxy), without encryption • To disable encryption manually on a single Outlook 2007 client, go to the menu shownuncheck the box, “Encrypt data between Microsoft Office Outlook and Microsoft Exchange’. • To disable encryption for multiple users via group policies, follow the instructions at http://support.microsoft.com/default.aspx/kb/924617 .Change the Properties for “Enable RPC Encryption” to “Disabled” under “User Configuration: Administrative Templates: Microsoft Office Outlook 2007: Tools: Advanced Settings: Exchange.

28. Branch Repeater Technology – HDX Broadcast • Adaptive Protocol Acceleration (Improve inefficient protocols) Adaptive Compression (Reduce application turns and data) Adaptive TCP Flow Control (Overcome loss/latency penalties) Prioritization and QoS (Prioritize critical traffic)

29. Disk DRAM Access Time Cache History Length Adaptive Compression Sensing real-time network and traffic conditions First pass compression • In L2 cache and memory • Various algorithms (ZLIB, LZS) Byte Caching • In memory or on disk De-Duplication • Across workflows • Across applications • Across users

30. Adaptive Compression First Pass Compression History Compression History

31. A Small Token Replaces Thousands of Bytes Adaptive Compression Second Pass Compression History Compression History

32. Branch Repeater Technology – HDX Broadcast • Adaptive Protocol Acceleration (Improve inefficient protocols) Adaptive Compression (Reduce application turns and data) Adaptive TCP Flow Control (Overcome loss/latency penalties) Prioritization and QoS (Prioritize critical traffic)

33. With Branch Repeater Throughput AverageUtilization Time Adaptive TCP Flow Control Sensing and responding to latency and packet loss Without Branch Repeater Throughput Link Speed AverageUtilization Time Slow Start Slow Ramp

34. Branch Repeater Technology – HDX Broadcast • Adaptive Protocol Acceleration (Improve inefficient protocols) Adaptive Compression (Reduce application turns and data) Adaptive TCP Flow Control (Overcome loss/latency penalties) Prioritization and QoS (Prioritize critical traffic)

35. With Branch Repeater ICA (Interactive) 20% Recreational 20% Bulk Transfers 60% Traffic Prioritization and QoS Adaptively allocates bandwidth across different applications and ICA virtual channel types Without Branch Repeater Bulk Transfers 1.5 Mbps Recreational ICA (Interactive)

36. Quality of Service (QoS) prioritizes applications • 5 traffic classes (or QoS queues) • Each queue assigned a min % of the link bandwidth • If queue bandwidth is unused, other traffic can use it • QoS is Citrix ICA aware • Dynamic mapping based on ICA priority bits • Queue specific reporting

37. Quality of Service Scheduling Class A – 50% Flow (Partner unit) Class B – 25% Flow (Partner unit) Adapter (NIC) Class C – 25% Class D – 0% Flow (Partner unit) Class E – 0%

38. QoS and ICA Priority Tags • Default Priority bits and ICA virtual channels: • ICA packet with data from multiple channels gets the priority bit associated with the highest level Virtual Channel • ICA Priority bits can be changed via the registry of the Presentation Servers.

39. Branch Repeater Technology – HDX IntelliCache Branch Staging of Offline Apps Pre-positions streamed applications locally for rapid delivery to branch users Local caching and de-duplication across multiple XenApp user sessions Branch Caching of Online Apps

40. Accelerating XenApp Offline Apps • Stages and accelerates Offline apps to branches • Deliver LAN-like performance • Branch remains productive even during WAN outages • Reduce management complexities of services in the branch • Transparent, instant-on service to the user

41. Branch Staging Pre-positioning of Offline applications locally in the branch XenApp Application Profiler File Share (Application Hub) Branch Users WAN Branch Repeater with Windows Server

42. When do .CAB stream over the WAN? • User accesses an app for the first time • Get updated or patched applications • After users download the app, it is saved to the local PC cache

43. 1 2 Pre-positioning .CAB files XenApp Profiler Citrix Branch Repeater Citrix Repeater Client WAN XenApp5 .cab File store • Very automatic and transparent to client • Can be done anytime • QoS administration of both DFS replicated traffic and other traffic to branch • Tip: Make sure that the Branch Repeater and the XenApp Server have domain permissions.

44. 1 2 Client accessing the files via DFS Namespace XenApp Profiler and redirection (Authenticate / Download / Redirect) Citrix Branch Repeater Citrix Repeater Client WAN XenApp5 .cab File store • Designed based on DFS replication • Redirects client to closest DFS replication site the local BR • No client changes required

45. Client accessing the files via DFS Namespace XenApp Profiler and redirection (Authenticate / Download / Redirect) Citrix Branch Repeater Citrix Repeater Client WAN XenApp5 3 .cab File store • Designed based on DFS replication • Redirects client to closest DFS replication site the local BR • No client changes required

46. Branch Repeater responds to client request XenApp Profiler Citrix Branch Repeater Citrix Repeater Client WAN XenApp .cab File store • LAN like performance • No need to go over WAN to get the LARGE .cab file • Results: Very HAPPY user!

47. Branch Repeater Technology – HDX IntelliCache Branch Staging of Offline Apps Pre-positions streamed applications locally for rapid delivery to branch users Local caching and de-duplication across multiple XenApp user sessions Branch Caching of Online Apps

48. Branch Caching Local caching and de-duplication across multiple sessions Data Center Branch Office Optimized TCP Connections Branch Repeater Repeater Infrastructure Servers XenApp Farm

49. Multi-user Optimization for XenApp • Delivers best performance for XenApp to branch users • 22-39% faster application start up per user • 2-6x faster bulk data transfer over ICA + up to 20x less bandwidth consumption • Up to 30x reduction for UPD print traffic over the WAN

50. Ideal Use Cases for Branch Caching • Multiple users accessing the same text heavy applications • e.g. Microsoft Word or Excel • Multiple users frequently accessing forms-based Web applications • e.g. Call center environment utilizing SAP • Multiple users printing similar files within ICA • i.e. Universal Print Driver (UPD) • Multiple users performing repetitive file transfers within ICA • i.e. Client drive mapping • Multiple users streaming the same media file within ICA • i.e. HDX MediaStream