Microsoft App-V loadbalancing with F5

I'm not familiar with App-V, but these links might help you:

 

 

http://technet.microsoft.com/en-us/library/ee354207.aspx Click Here

 

http://support.microsoft.com/kb/932017 Click Here

Hi igorm

 

 

This is James Hendergart from the F5 Business Development group. We are working on some additional guidance to assist with App-V deployments. I'll post a note about it in the next few days. Feel free to post any requirements you have such as numbers of simulteious App-V sessions, numbers of App-V servers, how many data center sites and your scalability objectives.

 

 

Thanks!

 

 

James

James -

 

 

Do you happen to have the App-V F5 deployment assistence stuff ready? I'm also in the process of configuring our F5 to load balance our 2 App-V servers and I'm having difficulty find detailed information on what needs to be done. Thanks in advance!

 

 

Ben Parker

Hi Ben!

 

Thanks for following up. We're still working on the official deployment guidance. Based on your request I asked the engineering team if we could get you something "rough" to tide you over.

 

I hope to have something for you in 1-2 days. Stay tuned here, thanks!

 

James Hendergart

 

F5 BDM for F5 partnership with Microsoft

 

Here is a quick summary of port/protocols to configure to handle App-V traffic. F5 recommends configuring traffic to and from App-V servers through LTM instead of using direct server return.

 

 

LB App-V Management Servers TCP 80/443 for the Management Service RTSP 554 + two high TCP ports (in this range: 49152-65535) or just RSTPS 332 SW streaming uses the same ports as the desktop refresh action. For OSD and ICO files (which are pulled down from HTTP or UNC path during "desktop refresh) ports HTTP(s) 80/443 and [UNC/CIFS] TCP 139, 445 and UDP 137, 138 must be opened.

 

If using RTSPS (TLS encryption, then 332). Affinity is just needed and even Source IP is OK if it works. Any other successful method would also be OK. Extra information about App-V: RTSP 554 (554 can be changed). It controls the transport, session build-up and tear down. RTP transports the media RTCP controls streaming for QoS Delivers sequenced applications to clients. Here is the connection process: App-V client sets up a connection with the server. Server sends port numbers for media and control to client. Client opens 2 sockets for media and control. RTSP is used to discover available apps on the server and one socket is used for all streamed apps. But new sockets for RTP and RTCP are opened from client, one pair for each streamed app.

 

 

Thanks,

 

James Hendergart

 

F5 Business Development Manager

 

Hi James,

 

 

As luck would have it I also need to deploy an App-V infrastructure with F5 load balancer. It will have two management servers talking to the same SQL database and two IIS servers for streaming. So load balancing needs to apply to the pair of management servers and then the pair of IIS servers. Do you have a more complete guide forthcoming? I'm not even entirely sure where to put the periods in your paragraphs, so a little more exposition would be much appreciated. ;)

 

 

Pete

Hello? Bueller?

James,

 

 

Do you have any tutorials/how-to's on how to set up App-v with LTM? We are also in need of setting this up on our BigIP.

 

 

Regards,

 

I'm also very interested in information on this. As I just got a request from a major customer that need help configuring LTM in a Microsoft App-V Environment.