What Does RFMS Recommend for Remote Connections

RFMS recommends one of the following deployments, but is not limited to:

1. RemoteApp deployment with a custom RDP Port (other than port 3389)
2. RDS or Terminal Server via a VPN Connection (No public connection)

NOTE: Running RFMS Program Files over a Direct/Site-to-Site/IPSEC VPN connection is NOT supported and will cause a large amount of latency in the program. For example: 

[Server with RFMS Program Files located in Office A] <---- IPSEC VPN Tunnel ----> [Office B Users access RFMS Program files from Office A]

In this scenario, the latency from the VPN encryption will cause the response time from RFMS to drop and become unusable. However, RFMS could be deployed in the following way (but is not limited to):

[Server with RFMS Program Files shared via RemoteApp and custom port] <-------- Public Internet --------> [All Remote users]
[RDS with RFMS Program Files] <-------- SSLVPN Connection --------> [Remote user RDP'ing to the RDS server over SSL VPN]

RFMS does NOT recommend opening an RDS server to the public internet with the default RDP port of 3389. You MUST change this to a custom port, or you will risk your server being compromised from the internet. If you feel this is an issue, please contact your IT Technician to perform a security audit to see if your server is at risk.


As with any remote deployment, The correct choice for your business should be discussed with your IT Technician for future support, growth, and maintenance