External Web Console Access SCOM 2012 R2 - An unexpected error has occured.

Question

Hello,
I have an issue when accessing the Web Console for our SCOM 2012 R2 environment - I have installed the web console on a standalone machine with mixed authentication - i have windows authentication enabled and NTLM is at the top of the providers list. I have
gone through the process of registering the SPN's and configuring constraint delegation. The SSL settings are ticked on the Default Web Site, the Monitoring View and the Operations Manager.
I have followed the article below when performing the install:
http://technet.microsoft.com/en-us/library/hh298606.aspx#bkmk_toconfigurepermissionsinheritanceforthewebconsole
I have also reviewed the information here and the information provided on the attached document on this page but the issue remains: http://blogs.technet.com/b/momteam/archive/2008/01/31/running-the-web-console-server-on-a-standalone-server-using-windows-authentication.aspx
When we try to log into the Web Console remotely it appears to load to 100% but then brings up the error:
An unexpected error has occured
Please provide the following information to the support engineer if you have to contact Microsoft Help and
Support :
System.ServiceModel.CommunicationException: [HttpWebRequest_WebException_RemoteServer]
Arguments: NotFound
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to
diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20913.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer ---> System.Net.WebException: [HttpWebRequest_WebException_RemoteServer]
Arguments: NotFound
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to
diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20913.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer ---> System.Net.WebException: [HttpWebRequest_WebException_RemoteServer]
Arguments: NotFound
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to
diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20913.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer
   at System.Net.Browser.BrowserHttpWebRequest.InternalEndGetResponse(IAsyncResult asyncResult)
   at System.Net.Browser.BrowserHttpWebRequest.<>c__DisplayClassa.<EndGetResponse>b__9(Object
sendState)
   at System.Net.Browser.AsyncHelper.<>c__DisplayClass4.<BeginOnUI>b__0(Object sendState)
   --- End of inner exception stack trace ---
   at System.Net.Browser.AsyncHelper.BeginOnUI(SendOrPostCallback beginMethod, Object state)
   at System.Net.Browser.BrowserHttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult
result)
   --- End of inner exception stack trace ---
   at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult
result)
   at System.ServiceModel.ClientBase`1.ChannelBase`1.EndInvoke(String methodName, Object[] args,
IAsyncResult result)
   at Microsoft.EnterpriseManagement.Presentation.Security.ServiceProxies.LogonServiceClient.LogonServiceClientChannel.EndGetConfiguration(IAsyncResult
result)
   at Microsoft.EnterpriseManagement.Presentation.Security.ServiceProxies.LogonServiceClient.Microsoft.EnterpriseManagement.Presentation.Security.ServiceProxies.ILogonService.EndGetConfiguration(IAsyncResult
result)
   at Microsoft.EnterpriseManagement.Presentation.Security.ServiceProxies.LogonServiceClient.OnEndGetConfiguration(IAsyncResult
result)
   at System.ServiceModel.ClientBase`1.OnAsyncCallCompleted(IAsyncResult result)

Answer 1

I can verify that this SCOM Web Console issue (System.ServiceModel.CommunicationException: [HttpWebRequest_WebException_RemoteServer]Arguments:
NotFound) was resolved in multiple instances simply by dropping and re-adding the IIS bindings for 80 & 443 (using Default Web Site for SCOM console) and restarting IIS.
John Joyner MVP-SC-CDM