Do I need to use SSL on the Remote Desktop Gateway in Windows Server 2008 R2? Let's say I am willing to take the security hit of not having SSL, can I still use the Remote Desktop Gateway for other management features? The reason I am thinking of this is that after looking into Remote Desktop Gateway it seems that in order for me to get redundancy so that if the Gateway goes down our remote users can still work it gets pretty complicated if not expensive with all kinds of redundant high end elements. In my current situation clients have primary and backup secondary Terminal servers they can directly log into based on different icons on their desktop - there is no single point of failure like the Gateway - we even have dual ISP's. What I want to do is install the Remote Desktop Gateway for its management features and if it is out of commission I want folks to use the old direct icons they used before the Gateway to access their target TS directly. It seems to me that if I get into the certificates business and port changing I will need to fix the Gateway problem pretty quick as if I don't users won't be able to access the gateway and as well won't be able to access their target Terminal Servers directly because I no longer have simple port forwarding in place - the Gateway replaced all of that.
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!