BUG in the installation process of SCOM 1801 Web Console (WORKAROUND)
again there is a bug in the Web Console, this time in SCOM 1801.
I installed SCOM 1801 Web Console using "Enable SSL" option. But if I browse on Internet Explorer, or Firefox, etc. https://<WEB CONSOLE>/OperationsManager gives the following error:
"The remote server returned an error: (404) Not found".
I figured out the issue
If I install SCOM Web Console without "Enable SSL", then the access to Web Console works.
SCOM Web COnsole installation process with "Enable SSL" does not set in IIS "SSL required" option, and does not set any Web Console registry parameter value automatically. I could reproduce this behaviour many times.
1) Set "SSL Reuired" manuals in IIS:
After the installaion of Web Console with "Enable SSL" set following:
"Default Web Site > SSL Settings", and enable "SSL required"
2) Set Registry parameter values manually:
"HKLM\SOFTWARE\Microsoft\System Center Operations Manager\Setup\Web Console"
That is definetly a bug in the installation process of SCOM 1801 Web Console. This instasllion BUG must be fixed by SCOM developer team.
[Deleted User] commented
Hi, i ran into a similar error. I installed scom 2019 webconsole, with ssl. In IIS everything was corrent, but ran into the same, not found error. Craigs solution works for me to. *:443. Very strange behavior and never seen this before in other websites.
In the registry i manually changed all entries: APM_AVISOR:URL, APM_DIAGNOSTICS_URL and of course WEB_CONSOLE_URL to the correct value. from localhost to <servername>
I had a similar issue
This article describe it:
Craig Wilson commented
I got a similar issue with the web console over SSL
I could access it fine over HTTP:// but got "Underlying connection was closed" error when trying over HTTPS://
After much investigation I managed to fix it by changing my IIS Binding for HTTPS
Not sure as to the reason why as this was fine in SCOM 2016...
Microsoft customer responsible controverts this bug.
I can reproduce the isntallation issue with "Enable SSL" many times.
How about with your experiences with this option? Does this installation set all necessary parameters correctly (registry, IIS, etc.)?
I am sure not.