This is the second of a five part series discussing lessons learned when installing System Center Operations Manager onto a fully Windows 2008 environment (DC, RMS, SQL, and Reporting servers). Since we now have a functional Windows 2008 domain controller (see Part 1 of this series at https://opsmgrunleashed.wordpress.com/2010/02/12/opsmgr-by-example-building-and-tuning-in-an-all-in-one-environment-for-operations-manager-in-windows-7/), our next step is installing and configuring the Operations Manager database server.
Installation prerequisites for the Operations Manager database components included first performing a standard SQL 2005 installation, and then installing SQL 2005 SP2.
Windows Server 2008 adds the Web Server as a role. If you have not the Web Server and the asp.net option, this shows as a warning during the SQL Server installation. Since this server will not provide reporting services or other web based features, we can ignore those warnings during our installation process. We installed SQL Server using default configurations, with the exception of choosing a domain user account to be the SQL Server service account.
Hotfixes for OpsMgr 20007 – Windows 2008 Servers with Agents
Each of the servers in this configuration needed to have three hotfixes applied:
After applying these hotfixes, you will need to reboot the system.
Additional OpsMgr Prerequisites
The database server for this environment will host both the Operations Manager database and the Data Warehouse functions. After installing SQL 2005 and patching it with SQL 2005 SP2, a prerequisites check indicated the server was ready for installing both the Operational Database and Data Warehouse OpsMgr components.
The next step was installation of the Operations Manager database. We used the default configurations, as shown in the video below.
To allow the SQL Server to communicate on the default port we need to create a new inbound rule to allow SQL Server port TCP port 1433. This assumes of course that you are using the default port, if you use a different port (such as installing a second instance), you will need to change the firewall to allow that port to communicate.
After installing this rule, log into another system in your environment and validate that telnet can connect to the SQL server on port 1433. Windows Server 2008 does not install the telnet client by default in Windows Server 2008, so you must add that feature prior to testing the ability to connect to the SQL Server.
Installing the Operations Manager database components is straightforward as long as you remember to install the appropriate hotfixes and create a firewall rule to allow inbound communication to port 1433.
Some great blogs have been covering information on Windows 2008. Definitely look into:
- http://blogs.technet.com/kevinholman/archive/2008/08/05/my-experience-installing-a-scom-management-server-on-windows-server-2008.aspx– a great write-up on installing OpsMgr on Windows Server 2008
- http://blogs.technet.com/kevinholman/archive/2008/07/29/how-do-i-know-if-i-have-all-the-required-hotfixes-on-windows-server-2008-to-be-supported-for-a-opsmgr-agent.aspx – write-up on required hotfixes