How To: Install the Operations Manager Web Console

How To: Install the Operations Manager Web Console

by Nate Stammer3. December 2012 13:40

When you install System Center 2012 Operations Manager you can install the web console at the same time or you can install it separately. Today, I will walk cover how to install the Operations Manager Web Console in your System Center 2012 Operations Manager on a stand-alone server, separately.

NOTE: If you install a stand-alone web console on a server, you will not be able to add the management server feature. If you want to install the management server and web console on the same server, you must either install both features simultaneously, or install the management server before you install the web console.

When you install the web console, three components are installed: the Operations Manager web console itself, Application Diagnostics console, and Application Advisor console. If Application Diagnostics console is not installed when viewing APM alerts, you will not be able to use the link embedded in the alert description to launch the APM event details. To use this feature, install the web console within the management group.

The web console operates with sensitive data, such as clear text user credentials, server names, IP addresses and so on. If these are exposed on the network they can represent a significant security risk. I recommend, and it is best practice, you configure IIS to use SSL.

If the web console does not have sufficient access to the operational database or the data warehouse database, you will receive a warning during the web console configuration step. You can proceed with Setup, but the web console will not be configured correctly for .NET Application monitoring. To resolve this issue, you should have your database administrator run the following SQL Server statement on both the operational database and data warehouse database:
EXEC [apm].GrantRWPermissionsToComputer N'[LOGIN]
You will also need to make sure the server on which you are installing the Web Console feature meets the following prerequisites:

  • Operating System: Windows Server 2008 R2 SP1.
  • Processor Architecture: must be x64.
  • Web browsers: Internet Explorer 7, Internet Explorer 8, Internet Explorer 9
  • Internet Information Services (IIS) 7.5 and later versions, with the IIS Management Console and the following role services installed:
    • Static Content
    • Default Document
    • Directory Browsing
    • HTTP Errors
    • HTTP Logging
    • Request Monitor
    • Request Filtering
    • Static Content Compression
    • Web Server (IIS) Support
    • IIS 6 Metabase Compatibility
    • ASP.NET
    • Windows Authentication
  • Selected website for web console: requires a configured http or https binding.
    • Installing the web console on a computer that has SharePoint installed is not supported.
  • Both .NET Framework 3.5 SP1 and .NET Framework 4 are required for Setup to run.

To Install a Stand-Alone Web Console:

  1. On the Operations Manager installation media page, run Setup.exe > click Install.
  2. On the Getting Started: Select features to install page, select Web console > click Next.
  3. On the Getting Started: Select installation location page, accept the default location of C:\Program Files\System Center 2012\Operations Manager > click Next.
  4. On the Prerequisites page, review and address any warnings or errors that the Prerequisites checker returns > click Verify Prerequisites Again to recheck the system.
  5. Installation of the web console requires that ISAPI and CGI Restrictions in IIS be enabled for ASP.NET. To enable, select the web server in IIS Manager > double-click ISAPI and CGI Restrictions > select ASP.NET v4.0.30319 > click Allow.
  6. NOTE: You must install IIS before installing .NET Framework 4. If you installed IIS after installing .NET Framework 4, you must register ASP.NET 4.0 with IIS. Open a Command prompt window by using the Run As Administrator option and then run the following command: %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –r

  7. After, if Prerequisites checker does not return any warnings or errors, the Prerequisites: Proceed with Setup page will appear > click Next.
  8. On the Configuration: Specify a management server page, enter the name of a management server that only the web console uses > click Next.
  9. On the Configuration: Specify a web site for use with the Web console page, select the Default Web Site or the name of an existing website > select Enable SSL only if the website has been configured to use Secure Sockets Layer (SSL) > clickNext.
  10. NOTE: As mentioned earlier, enabling SSL is recommended as a best practice.

  11. On the Configuration: Select an authentication mode for use with the Web console page, select your options > click Next.
  12. NOTE: If you install the management server on a server using a domain account for System Center Configuration service and System Center Data Access service, and then install the Web console on a different server and select Mixed Authentication, you may need to register Service Principal Names and configure constraint delegations.

  13. The Configuration: Microsoft Update page appears. Select your options, and then click Next.
  14. Review the selections you made on the previous page on the Configuration: Installation Summary page > Install > setup continues.
  15. When Setup is finished, the Setup is complete page appears > click Close.
  16. The Operations Manager Web Console should look something like this:

    Almost done!  After you install the web console, you must configure permissions inheritance to allow users to view performance and diagram views.

To Configure Permissions Inheritance for the Web Console

1.   In Windows Explorer, navigate to the MonitoringView folder in the installation directory for the web console, by default:
C:\Program Files\System Center 2012\Operations Manager\WebConsole\MonitoringView >
right-click the TempImages folder > click Properties.
2.   On the Security tab, click Advanced.
3.   On the Permissions tab, click Change Permissions.
4.   Select the Include inheritable permissions from this object’s parent checkbox.
5.   In Permission entries, click Administrators > click Remove. Repeat for the SYSTEM entry > click OK.
6.   ClickOK to close Advanced Security Settings for TempImages > click OK to close TempImages Properties.

Congratulations! You have successfully deployed the Operations Manager Web Console to a stand-alone server. Now you have access to Monitoring and My Workspace via the Web Console on your stand-alone server.

Add comment

  Country flag

biuquote
  • Comment
  • Preview
Loading