This is the final of a five part series discussing lessons learned through installing System Center Operations Manager onto a fully Windows 2008 environment (DC, RMS, SQL, and Reporting servers). You can see previous posts in this series at:
- https://opsmgrunleashed.wordpress.com/2008/08/13/opsmgr-by-example-server-2008-poc-%e2%80%93-part-1-domain-controller/ OpsMgr by Example – Server 2008 POC – Part 1 (Domain Controller)
- https://opsmgrunleashed.wordpress.com/2008/08/18/opsmgr-by-example-server-2008-poc-%e2%80%93-part-2-database-server/ OpsMgr by Example – Server 2008 POC – Part 2 (Database Server)
- https://opsmgrunleashed.wordpress.com/2008/08/21/opsmgr-by-example-server-2008-poc-%e2%80%93-part-3-root-management-server/ OpsMgr by Example – Server 2008 POC – Part 3 (Root Management Server)
- https://opsmgrunleashed.wordpress.com/2008/08/25/opsmgr-by-example-server-2008-poc-%e2%80%93-part-4-data-warehouse-server/ OpsMgr by Example – Server 2008 POC – Part 4 (Data Warehouse Server)
At this time, we have successfully completed all of the required pieces of the environment other than the reporting components. This post discusses installing the Reporting Server on Windows Server 2008. The Reporting Server installation is definitely the most error-prone part of the entire OpsMgr installation, be it on Windows 2003 or Windows 2008.
Hotfixes for OpsMgr 2007 – Windows 2008 Servers with Agents
Each of the servers in this configuration needed to have three hotfixes applied to them:
After applying these hotfixes, you will need to reboot the system.
The .NET Framework 3.0 components are not installed by default. You can install these in the Server Manager by adding the Application Server role.
Prior to installing the reporting components for Operations Manager, follow the steps identified in KB article 938245 (http://support.microsoft.com/kb/938245/) to configure reporting services on Windows Server 2008.
Do not attempt to install the reporting components on a system until you can successfully browse to both http://localhost/reports and http://localhost/reportserver on the reporting server. Configuration is required within the Reporting Services Configuration. Browsing of either of the above URL’s will not work until the Reporting Services Configuration is working, we display a functional example below. During our configurations we needed to create a new Report Server Virtual Directory, configure the Database Setup section, and perform an IISReset of the website to get it to a green state for the first six items, as shown in this screenshot:
Do not pass go, do not collect $200/We spent several hours trying to resolve issues that were actually related to configurations necessary for SQL 2005 Reporting Services to work on Windows Server 2008. Installing the reporting components on a system that does not already have functional reporting services will just make the situation worse.
The prerequisites for the Reporting Server component include SQL Server 2005 with Reporting Services (which in turn requires the Web role, etc) with SQL 2005 Service Pack 2 applied.
OpsMgr Reporting Server installation
The installation of Operations Manager’s Reporting Server worked just the same as on a Windows 2003 platform (once the prerequisites had been configured correctly).
- Validate reporting functionality both from the existence of the reports and the ability to get valid data from the reports (the Management Pack ODR report is a simple one to validate this with).
- Deploy Operations Manager agents into the environment.
- Integrate additional management packs.
- Wait on official support for Windows Server 2008 as a platform for all of the Operations Manager components.
- It is possible you will get an error “Unable to connect to the remote server” when browsing to http://localhost/reports or http://<servername>/reports. For steps on how to address this, check out http://r0nwilliams.spaces.live.com/blog/cns!62A0019E9E556103!190.entry.
- Without question, getting SQL 2005 Reporting Services working on Windows 2008 was the most complex piece of the installation. Focus on getting a functional SQL Reporting server before continuing (see http://support.microsoft.com/kb/938245/ for details).