Remote Web Access login page Redirect
October 31, 2016 4 Comments
This post comes courtesy of Susan Bradley, in that she highlighted the issue to me. In turn it was highlighted to her via TechSpeeder.
The issue is a relativley simple one, in previous versions of Essentials, visiting http://server or http://server.remotewebaccess.com it would automatically redirect you to the RWA Login page at /remote. In 2016 this is not occurring.
In 2012 R2 this behaviour is controlled via default.aspx in particular, this line.
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="Microsoft.WindowsServerSolutions.Web.RootSite._Default" %>
Looking at the Content of the Default Web Site in 2016, we can see the standard IIS InetPub wwwroot folder. This is odd because usually in Essentials that path has been updated to C:\Program Files\Windows Server\Bin\WebApps\Site.
Luckily we can simply amend that path to restore the functionality, right click the Default Web Site, go to Manage Website and then Advanced Settings.
Update the Physical Path to the ‘correct’ path, then restart the DefaultAppPool and the Default Web Site.
Your site will now correctly redirect you to the login page.
This thread and answer from flyingMagnus confirm that changing the path ‘repairs’ the remote redirect with the side effect that the page reports ‘Remote Web Access is Turned Off’. I have opened a support case with Microsoft for this issue. In the meantime you can use the redirect method posted by TechSpeeder.
I just got off the phone with Microsoft, who informed me that this behaviour is ‘by design’. I’m pretty annoyed to say the least, if you include the Azure ASR Dashboard ‘bug’ it amounts to a pretty poor product. I’m not sure where that leaves me, i certainly don’t feel any passion towards the product any more. I’ll see if i can find _anyone_ at Microsoft who wants to communicate on this. For now at least, I think it is time to find a new solution.