Recently, I was contacted by Squared Up and asked if I would do a review of their product. Since I’ve reviewed other third-part products in the past, of course I would be willing to review this one.
For reference, although not SCOM-based, here are some other products that I have reviewed:
- ITQ’s End User Portal for System Center Orchestrator
- SCSM 2012 Dashboard by Signature Consultancy
- SMTrak Enterprise Dashboard by Signature Consultancy
- Advanced Portal for SCSM 2012 by CodeCraft-Solutions
- SCSM Dashboard by Expit Ensight
- SCUtils Knowledge Base For SCSM 2012
So let’s get started. This series will cover the Squared Up HTML 5 Dashboard and Web Console.
- Squared Up’s HTML5 Dashboards & Web Console for SCOM – Part 1: Introduction
- Squared Up’s HTML5 Dashboards & Web Console for SCOM – Part 2: Prerequisites
- Squared Up’s HTML5 Dashboards & Web Console for SCOM – Part 3: Installation
- Squared Up’s HTML5 Dashboards & Web Console for SCOM – Part 4: Activation
- Squared Up’s HTML5 Dashboards & Web Console for SCOM – Part 5: Configure the SCOM Data Warehouse
- Squared Up’s HTML5 Dashboards & Web Console for SCOM – Part 6: Customize Dashboards
In order to install this product, there are a few things we need in place.
System Center Operations Manager
As of the time of this writing, the Squared Up dashboards support the following versions of System Center Operations Manager (SCOM):
- Operations Manager 2007 R2
- Operations Manager 2012
- Operations Manager 2012 SP1
- Operations Manager 2012 R2
Squared Up Web Server
- Windows Server 2008 R2 SP1 or later
- Windows Server 2012
- Windows Server 2012 R2
- Squared Up v1 .NET Framework 4.0 or later
- Squared Up v2 .NET Framework 4.5 or later
- Can be installed on Operations Manager management server or root management server
- Can be installed on the same web server as the Operations Manager web consoles (2007 R2 or 2012)
Internet Information Services (IIS) Features
Web Server (IIS)
- Common HTTP Features
- Static Content
- Default Document
- HTTP Errors
- Application Development
- .NET Extensibility
- ISAPI Extensions
- ISAPI Filters
- Health and Diagnostics
- HTTP Logging
- Windows Authentication
- Request Filtering
- Static Content Compression
- Dynamic Compression
- Management Tools
- IIS Management Console
- IIS 6 Management Compatibility
- IIS 6 Metabase Compatibility
NOTE: Even though the prerequisite supported platforms lists Windows Server 2012 R2 as the highest OS level supported, since I am performing other testing with Windows Server 2016 Technical Preview, and System Center 2016 Technical Preview, I decided to attempt the installation using these vNext platforms.
UPDATE: The product installation did not detect IIS correctly, and although it was installed, seemed to think it did not meet the minimal requirements of “IIS 7.5 or later”. I encountered the following error message.
I have since contacted the company with this information, in hopes that they are currently developing compatibility with Windows Server 2016.
As was listed in the Prerequisites, Internet Information Services (IIS) is a required feature.
There are several options for installing this requirement. Per the Squared Up website:
The following actions are taken by the Squared Up setup application.
- Requests acceptance of license agreement
- Checks operating system is Windows Server 2008 R2 SP1 (equivalent to version 6.1.7601.17514)
- Checks .NET 4 ‘Full profile’ is installed
- Checks IIS role and features are installed (see IIS Features)
- If required, executes dotNetFx40_Full_setup.exe
- If required, executes C:\Windows\System32\ServerManagerCmd.exe -install Web-Static-Content Web-Default-Doc Web-Http-Errors Web-Asp-Net Web-Net-Ext Web-ISAPI-Ext Web-ISAPI-Filter Web-Http-Logging Web-Windows-Auth Web-Filtering Web-Stat-Compression Web-Dyn-Compression Web-Mgmt-Console Web-Metabase
- If required, executes C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis -ir
- Extracts and installs Installer.msi
Note, I noticed that when I attempted to perform the IIS installation via the command line detailed above, it didn’t work. If you plan to do this via PowerShell (which is the fastest option), you need to put a comma (,) between each Windows Feature. Also, some of the features may no longer be present in newer versions of Windows Server (see my article on Windows Server 2016 TP2, specifically the “Removed Windows Server Technical Preview 2 – Roles and Features” section).
As long as you have at least some of the Prereqs prepared (i.e. SCOM, Web server OS), you can continue with the installation. Remember that the product installer will actually install the .NET Framework, and Internet Information Services (IIS) with the required features, before installing the product itself.
Now that we’re prepared, we can now move onto Part 3: Installation.