Installing Operations Manager 2007 R2
As discussed in the previous section, Operations Manager 2007 R2 is a multitier and multi-component application that can be deployed in a variety of architectures. This allows OpsMgr to support scaling from a small organization to a very large enterprise.
For the purposes of this chapter, an all-in-one single-server install is used. This allows for monitoring of small- to medium-sized Windows Server 2008 R2 organizations spanning a handful of servers to up to 250 servers.
Single-Server OpsMgr 2007 R2 Install
This section steps through the install of OpsMgr and Reporting on a single-server configuration. The specification for a single-server configuration to support up to 250 agent systems is as follows:
- 2 x 2.8GHz Cores
- 8GB RAM
- 4 Drive RAID 0+1 Disk (200+GB Space)
These hardware requirements ensure that the system can perform to specification.
If the configuration were to be virtualized on a Windows Server 2008 Hyper-V host or a VMware ESX host, a single-server configuration is not recommended. Instead, a two-server configuration is recommended and SQL Server 2008 should be installed on the second server to balance the load.
The steps in this section assume that the single server has been prepared with the following:
- Windows Server 2008 R2 operating system installed
- Web role with the appropriate features installed
- SQL Server 2008 with Reporting Services installed
- An OpsMgr service account with local administrator rights to the server and system administrator rights to SQL Server 2008
To install SQL Reporting Services and the Web components of OpsMgr 2007 R2, the following Windows Server 2008 Web role features need to be installed: Static Content, Default Document, HTTP Redirection, Directory Browsing, ASP, ASP.NET, ISAPI Extension, ISAPI Filters, Windows Authentication, IIS Metabase, and IIS 6 WMI.
This prepares the system for the install of OpsMgr 2007 R2. See the following prerequisite checker information for additional requirements and how to check them.
Before installing, it is important to run the built-in prerequisite checker. This utility is available on the OpsMgr installation media and confirms a host of software prerequisites before attempting the actual installation. This gives the administrator time to download and install the necessary software, rather than have the installation bomb out in the middle after entering a lot of configuration information.
This section assumes a Windows Server 2008 and SQL Server 2008 server will be used for the single-server installation, but the prerequisite checker looks at more general requirements based on the OpsMgr supported platforms. The prerequisite checker looks for the following software on a single-server configuration:
- Windows Server 2003 Service Pack 1 or Windows Server 2008 Service Pack 1
- Microsoft SQL Server 2005 Service Pack 1 or SQL Server 2008 Service Pack 1
- Microsoft SQL Server 2005 Reporting Services Service Pack 1 or SQL Server 2008 Reporting Services Service Pack 1
- World Wide Web Service is running and set for automatic startup
- WS-Management v1.1
- MDAC version 2.80.1022.0 or higher
- ASP.NET AJAX Extensions 1.0
- .NET Framework 2.0 and .NET Framework 3.0 components
- Windows PowerShell
- Key hotfixes
To use the Prerequisite Viewer for a single-server configuration, run the following steps:
- Log on with an account that has administrator rights.
- Insert the Operations Manager 2007 R2 installation media.
- The setup will start automatically or launch the SetupOM.exe.
- Click Check Prerequisites to start the Prerequisite Viewer.
- Select Operational Database, Server, Console, PowerShell, Web Console, Reporting, and Data Warehouse, and then click Check.
- When you are finished with the Prerequisite Viewer, click Close.
The prerequisite checker findings will be displayed and will have active links that can be clicked to get specific guidance, as well as links to download software and hotfixes.
Follow the corrections in the prerequisite checker to resolve any problems before proceeding to the installation. Some of the guidance will be warnings, particularly with some of the hotfixes. Leaving out hotfixes might allow the installation to proceed, but might make the OpsMgr application less stable. It is highly recommended that all the recommendations be applied to ensure the most stable platform possible. If any of the installations require a reboot, it is recommended to run the prerequisite checker again.
Once the server meets all the prerequisites and is ready for installation, the steps to run the install are as follows:
- Logon with the OpsMgr service account.
- Launch SetupOM.exe from the OpsMgr installation media.
- Click Install Operations Manager 2007 R2.
- Click Next.
- Accept the license agreement and click Next.
- Enter the CD key if required and then click Next.
- When the Custom Setup page displays, leave the components set to their defaults, and then click Next.
- Type the management group name in the Management Group text box and click Next.
- Select the instance of SQL Server on which to install the Operations Manager 2007 R2 database (the local system because this is a single-server install), and then click Next.
- Leave the default database size of 1,000 MB, and then click Next.
- Select Domain or Local Computer Account, type the user account and password, select the domain or local computer from the list, and then click Next.
- On the SDK and Config Service Account page, select Domain or Local Account, type the user account and password, select the domain or local computer from the list, and then click Next.
- On the Web Console Authentication Configuration page, select Use Windows Authentication and click Next.
- On the Operations Manager Error Reports page, leave the Do You Want to Send Error Reports to Microsoft option cleared and click Next to not send Operations Manager 2007 R2 error reports to Microsoft.
- On the Customer Experience Improvement Program page, leave the default option of I Don't Want to Join the Program Selected, and then click Next.
- On the Ready to Install page, click Install.
- When the Completing the System Center Operations Manager 2007 R2 Setup Wizard page appears, leave the Backup Encryption Key check box selected to back up the encryption key.
- Leave Start the Console selected to open the Operations Console.
- Click Finish.
A copy of the encryption key is needed to promote a management server to the role of the Root Management Server in the event of a failure of the RMS.
Operations Manager 2007 R2 is now installed in a single-server configuration. This configuration can manage up to 250 servers.
Importing Management Packs
After the initial installation, OpsMgr only includes a few management packs. The management packs contain all the discoveries, monitors, rules, knowledge, reports, and views that OpsMgr needs to be able to effectively monitor servers and applications. One of the first tasks after installing OpsMgr 2007 is to import management packs into the system.
There are a large number of management packs in the Internet catalog on the Microsoft website. These include updated management packs, management packs for new products, and third-party management packs. It is important to load only those management packs that are going to be used, as each additional management pack increases the database size, adds discoveries that impact the performance of agents, and, in general, clutters up the interface.
The key management packs for a Windows Server 2008 R2 environment are as follows:
- Windows Server Operating System MPs
- Active Directory Server MPs
- Windows Cluster Management MPs
- Microsoft Windows DNS Server MPs
- Microsoft Windows DHCP Server MPs
- Microsoft Windows Group Policy MPs
- Microsoft Windows Hyper-V MPs
- Windows Server Internet Information Services MPs
- Windows Server Network Load Balancing MPs
- Windows Server Print Server MPs
- Windows Terminal Services MPs
- SQL Server MPs (to monitor the OpsMgr database roles)
There might be other management packs that are appropriate for the environment, depending on the applications that are installed. For example, if the organization has deployed Exchange Server 2010 and HP Proliant server hardware, it would be good for the organization to deploy the Exchange management packs and the HP Proliant management packs.
For each of these management packs, it is important to load the relevant versions only. For example, if the environment includes Windows Server 2008 only, only load the Windows Server Core OS 2008 management pack. If the environment includes both Windows Server 2003 and Windows Server 2008, load both the Windows Server Core OS 2003 and the Windows Server Core OS 2008. In addition, a number of language packs don't need to be loaded unless those particular languages are supported by the organization at the server level.
Some collections of management packs require that all versions be loaded, but the Management Pack Import Wizard will check and warn if that's the case.
In versions of OpsMgr prior to R2, the management packs had to be downloaded from the Microsoft website one by one, the MSI installed one by one, and the management packs imported one by one. Dependencies would not be checked unless additional steps were taken to consolidate the management pack files prior to importing. This was a very labor-intensive process. Also, there was no easy way for checking for updates to already installed management packs.
In OpsMgr 2007 R2, a new Management Pack Import Wizard was introduced. This wizard connects directly to the Microsoft management pack catalog and will download, check, and import management packs. It even does version checks to ensure that the management packs are the latest versions. This is a huge improvement over the old method of importing management packs.
To import the key management packs, use the following steps:
- Launch the Operations Console.
- Select the Administration section.
- Select the Management Packs folder.
- Right-click the Management Packs folder and select Import Management Packs.
- Click the Add button and select Add from Catalog.
- Click the Search button to search the entire catalog.
- Select the key management packs from the previous bulleted list and click the Add button for each of them. Each of the major management packs might include a number of submanagement packs for discovery, monitoring, and other breakdowns of functionality.
- When done adding management packs, click OK.
- The wizard now validates the added management packs, checking for versions, dependencies, and security risks. It allows problem management packs to be removed and dependencies to be added to the list.
- Click Install to begin the download and import process. Progress will be shown for each of the management packs being imported.
- After all the management packs are imported, click Close to exit the wizard.
The View pull-down menu in the Management Pack Import Wizard includes four options, which are All Management Packs in the Catalog, Updates Available for Installed Management Packs, All Management Packs Released in the Last 3 Months, and All Management Packs Released in the Last 6 Months. The Updates option checks against the already installed management packs and allows the download of updated versions of those.
After the import completes, the management packs take effect immediately. Agents will begin discovering based on the schedule specified in the management packs and monitors and rules will begin deploying.
Deploying OpsMgr Agents
OpsMgr agents are deployed to all managed servers through the OpsMgr Discovery Wizard, or by using software distribution mechanisms such as Active Directory GPOs or System Center Configuration Manager 2007. Installation through the Operations Console uses the fully qualified domain name (FQDN) of the computer. When searching for systems through the Operations Console, you can use wildcards to locate a broad range of computers for agent installation. Certain situations, such as monitoring across firewalls, can require the manual installation of these components.
The Discovery Wizard can discover and configure monitoring for Windows computers, UNIX/Linux computers, and for network devices. It will push agents to Windows and UNIX/Linux computers, as long as the proper rights are provided, such as an account with local administrator rights or a root account.
To install domain member agents using the Discovery Wizard, run the following steps:
- Launch the Operations Console and select the Administration section.
- Right-click the top-level Administration folder and select Discovery Wizard.
- Select the Windows computers and click Next.
- Select Automatic Computer Discovery and click Next. This scans the entire Active Directory domain for computers.
- Leave the Use Selected Management Server Action Account and click Discover. This starts the discovery process.
- After the discovery process runs (this might take a few minutes), the list of discovered computers is displayed. Select the devices that should have agents deployed to them, as shown in Figure 23.7.
- Click Next.
- Leave the Agent Installation Directory and the Agent Action Account at the defaults, and then click Finish.
- The Agent Management Task Status window appears, listing all the computers selected and the progress of each installation. As shown in Figure 23.8, the agent installation task started for the selected computers.
- Click Close when the installation completes.
The list only includes systems that do not already have agents installed. If a computer has an agent installed, the wizard excludes it from the list of devices.
FIGURE 23.7 Discovered computers.
FIGURE 23.8 Agent installation progress.Even if the window is closed before the installs complete, the results of the installs can be viewed in Task Status view in the Monitoring section of the Operations Console.
The agent deployment is very efficient and a large number of computers can be selected for deployment without any issues. The agents will start automatically and begin to be monitored as they are discovered.
After installation, it might be necessary to wait a few minutes before the information from the agents will be sent to the management server.
During the next few minutes after installation, the agent contacts the management server and establishes a mutually authenticated, encrypted communication channel with the assigned management server. If the agent was pushed through a software delivery system such as System Center Configuration Manager 2007 R2, the agent determines the management server through Active Directory--integrated discovery.
The agent downloads rules to discover the various applications and components it's hosting, allowing the correct application-specific management packs to be applied. This discovery process runs periodically to ensure the correct rules are always applied to the server.
Integrating System Center Operations Manager 2007 R2 with Windows Server 2008 R2
Using OpsMgr 2007 R2 to monitor Windows Server 2008 R2
OpsMgr 2007 R2 hardware, software, security requirements
OpsMgr 2007 R2 installation steps
Operations Manager 2007 R2 configuration
Operations Manager 2007 R2: Using alerts, running reports
Printed with permission from Sams Publishing. Copyright 2010. Windows Server 2008 R2 Unleashed by Rand Morimoto, Michael Noel, Omar Droubi and Ross Mistry. For more information about this title and other similar books, please visit Sams Publishing.
This was first published in May 2010