Some of you want to change this so that you get the same experience as in Windows Server Essentials 2012R2. The idea is then that we would change the Physical Path in the Advanced settings of the Default Website and set this to the Physical path value from the ‘\Remote’ application is IIS which is ‘C:\Program Files\Windows Server\Bin\WebApps\RemoteAccess’. This is a bad idea. Now why is this a bad idea? Well, if you look at the Application Pool of each application you will see that the default web site in Windows Server Essentials 2016 has DefaultAppPool set as application Pool. In the below screenshot you see that the \Remote application has RemoteAppPool set as the application Pool. Application Pools are used to isolate applications in IIS band thus creating a more secure environment. The Remote app runs under Remote Apppool with identity NetworkService and the Default Website as DefaultAppPool with identity ApplicationPoolIndentity. Those identities have different permissions set. Technet has more information on this subject IIS Application Pool . A much better way is to use a http redirect as in the below screenshot. But if you really want to do it as Microsoft has intended this you change nothing and from a client that is connected to the WSE 2016 server you use the Launchpad because that always connects to https://remote.yourdomain.com.