Microsoft App-V loadbalancing with F5

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