There are several default settings in the SCOM Web Console, that are done to increase the speed and performance of the Web Console. There are times, however, where you might want to change these.
One of the most common complaints, is that the Web Console doesn’t show the same Alerts as the regular console, or that the State views in the web console are limited to 200 items.
CAUTION: The Default settings are configured for best performance reasons. Making changes to these settings can slow down your web console when interacting with views, and potentially increase the load on the SCOM SDK. However, these will vary wildly with each customer management group and how many items they are trying to look at.
Here is an example of a state view in the console with more than 200 objects:
In the Web Console:
Alerts in the console:
Alerts in the Web Console:
Here is why, and how to change these defaults:
On your web console server, you can find a Web.Config file in the folder where SCOM is installed: \Program Files\Microsoft System Center\Operations Manager\WebConsole\MonitoringView\
Open this folder and FIRST make a backup copy of this file:
Next – open the Web.Config file using an *elevated* text editor.
Find the default <appSettings> section:
<appSettings> <add key="ManagementServerName" value="localhost"/> <add key="SessionTimeout" value="1440"/> <!-- <add key="setting" value="value"/> --> </appSettings>
Above that – you will see an explanation for the applicable configuration settings. I will summarize them below:
AlertsDaysBefore [default=7] (days) How long to look back for alerts based on time created AlertSeverity [default=1] 0-Critical only, 1-Critical and Warning, 2–Critical, Warning, and Information. LimitMaxViewRows [default=200] The max number of results displayed in the monitoring views. ViewAutoRefresh [default=5] (minutes) The auto-refresh timeout for the monitoring views. PerformanceLegendMax [default=45] Performance views only. Defines the max number of counters displayed in the Performance Legend. PerformanceCookieExp [default=2] (months) Performance View only. The performance counter selection cookie expiration timeout. PerformanceHoursBefore [default=24] (hours) Performance View only. Defines the max number of past hours from the current time to show the performance data for. MaxNonVGChildCount [default=50] Diagram View only. Defines the max number of child nodes in the Diagram View. ConsoleRoot [default="/MonitoringView"] The server relative URL to the OperationsManager application. DefaultErrorHandling [default="false"] ASP.NET error handling. When set to "True", the exception will be displayed according to the system.web/customErrors/@mode setting.
Here is my new <appSettings> section:
<appSettings> <add key="ManagementServerName" value="localhost"/> <add key="SessionTimeout" value="1440"/> <add key="LimitMaxViewRows" value="300"/> <add key="AlertsDaysBefore" value="60"/> <!-- <add key="setting" value="value"/> --> </appSettings>
Now my web console matches my regular console:
The changes take place immediately – no restart of the server nor IIS is required. However, any active users will need to sign out and back into the Web Console or they might see an error until they do.