1	  
2	  
3	  
4	  
5	  
6	  
7	  Note:	  Exis2ng	  A&O	  network	  based	  on	  backbone	  between	  UK	  &	  Singapore	  with	  other	  offices	  connec...
8	  
9	  
10	  
11	  
12	  
13	  
14	  
15	  
16	  
17	  How	  do	  we	  route	  people	  to	  their	  “home”	  NetScaler?	  	  Scenario:	  User	  from	  Australia	  travels	...
18	  How	  do	  we	  route	  people	  to	  their	  “home”	  NetScaler?	  	  Scenario:	  User	  from	  Australia	  travels	...
19	  
20	  
21	  
22	  
23	  
24	  
25	  
26	  
27	  
28	  
Upcoming SlideShare
Loading in …5
×

Architecting a global XenApp farm with regional users using Netscaler and Storefront

2,214 views

Published on

This session documents challenges and solutions when designing an environment that allowed employees to connect from anywhere in the world to applications and data located in a specific region. This project’s objectives were replacing Secure Gateway, improving the user experience and building a future-proof environment. Learn about the use of NetScaler global server load balancing and StoreFront customization, and how they were architected to balance cost and functionality.

Published in: Travel, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,214
On SlideShare
0
From Embeds
0
Number of Embeds
41
Actions
Shares
0
Downloads
84
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Architecting a global XenApp farm with regional users using Netscaler and Storefront

  1. 1. 1  
  2. 2. 2  
  3. 3. 3  
  4. 4. 4  
  5. 5. 5  
  6. 6. 6  
  7. 7. 7  Note:  Exis2ng  A&O  network  based  on  backbone  between  UK  &  Singapore  with  other  offices  connec2ng  into  backbone.  Result  is  no  direct  connec2on  between  sites  like  North  America  &  Australia.  
  8. 8. 8  
  9. 9. 9  
  10. 10. 10  
  11. 11. 11  
  12. 12. 12  
  13. 13. 13  
  14. 14. 14  
  15. 15. 15  
  16. 16. 16  
  17. 17. 17  How  do  we  route  people  to  their  “home”  NetScaler?    Scenario:  User  from  Australia  travels  to  US  Accesses  global  URL  Gets  directed  to  US  NetScaler  Logs  in  but  then  traverses  our  WAN  to  Australia    Result:  Unacceptable  performance    
  18. 18. 18  How  do  we  route  people  to  their  “home”  NetScaler?    Scenario:  User  from  Australia  travels  to  US  Accesses  global  URL  Gets  directed  to  US  NetScaler  Logs  in  but  then  traverses  our  WAN  to  Australia    Result:  Unacceptable  performance    
  19. 19. 19  
  20. 20. 20  
  21. 21. 21  
  22. 22. 22  
  23. 23. 23  
  24. 24. 24  
  25. 25. 25  
  26. 26. 26  
  27. 27. 27  
  28. 28. 28  

×