Operations
Manager 2007 R2 is a multitier and multicomponent application that can
be deployed in a variety of architectures. This enables OpsMgr to
support scaling from a small organization to a large enterprise.
For the purposes of thisarticle , an all-in-one single-server install is used. This allows for
monitoring of small- to medium-sized Exchange Server 2010 organizations
spanning a handful of servers to up to 50 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 50 Exchange Server 2010 servers would be
- 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. Note
that the Exchange Server 2010 servers generate a heavier load than other
server types such as domain controllers or web servers. This
configuration can support 50 Exchange Server 2010 servers or 250 servers
of other types.
Note
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 would be recommended, and the 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 operating system installed.
- Web role with the appropriate features installed.
Note
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.
- Windows PowerShell feature installed.
- SQL Server 2008 with Reporting Services installed.
- Create
an OpsMgr service account with local administrator rights to the server
and system administrator rights to the SQL Server 2008.
This prepares the
system for the install of OpsMgr 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 perquisites 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
Microsoft SQL Server 2005 Service Pack 1 or SQL Server 2008
Microsoft SQL Server 2005 Reporting Services Service Pack 1 or SQL Server 2008 Reporting Services
World Wide Web Service running and set for automatic startup
WS-MAN v1.1
.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:
1. | Log on with an account that has Administrator rights.
|
2. | Insert the Operations Manager 2007 R2 installation media.
|
3. | The setup starts automatically or launches the SetupOM.exe.
|
4. | Click Check Prerequisites to start the Prerequisite Viewer.
|
5. | Select Operational Database, Server, Console, Power Shell, Web Console, Reporting, and Data Warehouse, and then click Check.
Note
The prerequisite
checker findings display and have active links that can be clicked to
get specific guidance, and links to download software and hotfixes.
|
6. | When you finish with the Prerequisite Viewer, click Close.
|
Remediate all
the guidance in the prerequisite checker before proceeding to the
installation. Some of the guidance will be warnings, particularly with
some of the hotfixes. Leaving out hotfixes might enable 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.
When the server meets all the prerequisites and is ready for installation, the steps to run the install are as follows:
1. | Log on with the OpsMgr service account.
|
2. | Launch SetupOM.exe from the OpsMgr installation media.
|
3. | Click Install Operations Manager 2007 R2.
|
4. | Click Next.
|
5. | Accept the license agreement and click Next.
|
6. | Enter the CD key if required and then click Next.
|
7. | When the Custom Setup page displays, leave the components set to their defaults, and then click Next.
|
8. | Type the management group name in the Management Group box and click Next.
|
9. | 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.
|
10. | Leave the default database size of 1,000MB, and then click Next.
|
11. | 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.
|
12. | 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.
|
13. | On the Web Console Authentication Configuration page, select Use Windows Authentication and click Next.
|
14. | On
the Operations Manager Error Reports page, leave Do You Want To Send
Error Reports to Microsoft cleared and click Next to not send Operations
Manager 2007 R2 error reports to Microsoft.
|
15. | 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.
|
16. | On the Ready to Install page, click Install.
|
17. | When
the Completing the System Center Operations Manager 2007 R2 Setup
Wizard page appears, leave the Backup Encryption Key box selected to
back up the encryption key.
Note
A copy of the
encryption key is needed to promote a management server to the role of
the Root Management Server if a failure of the RMS occurs.
|
18. | Leave Start the Console selected to open the Operations console.
|
19. | Click Finish.
|
Operations
Manager 2007 R2 is now installed in a single-server configuration. This
configuration can manage up to 50 Exchange servers or 250 non-Exchange
servers.
