Microsoft Remote Desktop Session Host servers iApp template - Release Candidate
Problem this snippet solves:
f5.microsoft_session_host.v1.0.2:
This is the fully supported version of the iApp template, now on downloads.f5.com. It contains the fix described in the release candidate below. For the associated deployment guide, see http://www.f5.com/pdf/deployment-guides/microsoft-rds-session-host-dg.pdf
f5.microsoft_session_host.v1.0.2rc1:
Resolves import error seen when importing current iApp release (f5.microsoft_session_host.v1.0.1) similar to:"Loading configuration... /tmp/upload_template.tmpl 01070712:3: ERROR app_template - /Common/f5.microsoft_rds_session_host.v1.0.1 definition: /Common/f5.microsoft_rds_session_host.v1.0.1 definition:20: error: [script "f5.iapp.1.3.0.cli"......"
Problem this snippet solves:
You can use this F5-supported iApp template to help you configure the BIG-IP Local Traffic Manager (LTM) to direct traffic and maintain persistence to Microsoft Remote Desktop Services Session Host servers. You can also use the iApp template for configuring the BIG-IP Advanced Firewall Manager (AFM) to provide a sophisticated layer of security for your Remote Desktop Session Host deployment.
Remote Desktop Services enables users to remotely access full Windows desktops, or individual Windows-based applications, on Remote Desktop Session Host computers. In an environment that uses a BIG-IP LTM system, a farm of Remote Desktop Session Host servers has incoming connections distributed in a balanced manner across the members of the farm.
For instructions on downloading and installing the template, see SOL16335. For the associated deployment guide, see http://www.f5.com/pdf/deployment-guides/microsoft-rds-session-host-dg.pdf
Code :
https://support.f5.com/kb/en-us/solutions/public/16000/300/sol16335.html
Published Mar 14, 2016
Version 1.0
Flo_115Nimbostratus
Hello, we just installed this template for Terminalserver 2012R2 environment and discovered some configurations that don't match the configurations from the following guide https://www.f5.com/pdf/deployment-guides/microsoft-rds-session-host-dg.pdf in the Manual configuration table. TCP Profile: $Name_wan-optimized-tcp Keep Alive Interval is set to default, guide recommendation is 75 Nagle's Algorithm is enabled, guide recommendation is disabled TCP Profile: $Name_lan-optimized-tcp Idle Timeout is set to default, guide recommendation is 1200 Keep Alive Interval is set to default, guide recommendation is 75 The guide also recommends to configure a gateway ICMP montitor for the virtual UDP server. This is also missing in the template.- Thanks Flo, I have made a note to have this corrected in future iApp release.
rickh_387562so we are using 8 rsh and 2 cb's and a gateway and webaccess. Without F5 the session collection works great I can launch the .rdp app and connect to the session host within the collection.Whenwe use F5 the app then connects to any session host in the farm and not the correct ones assigned in the session collection how do we resolve this
