Operations Manager 2007 R2 Quick Start Guide

Applies To: Operations Manager 2007 R2

Did you know that System Center 2012 is available? System Center 2012 offers you a single, flexible platform to manage traditional datacenters, private and public clouds, and client computers and devices. Learn more about System Center 2012.

This Quick Start Guide is designed to help you quickly deploy Microsoft System Center Operations Manager 2007 R2 for evaluation purposes on a single computer that is running Windows Server 2003 and SQL Server 2005. For information about deploying the product in a production environment, see Deploying Operations Manager 2007 at https://go.microsoft.com/fwlink/?LinkId=90673.

System Requirements for Operations Manager 2007 R2

Make sure that the computer you use to evaluate Operations Manager 2007 R2 meets the hardware and software requirements of the product. For the complete list of supported configurations, see Operations Manager 2007 R2 Supported Configurations at https://go.microsoft.com/fwlink/?LinkId=90676.

Create the Accounts Necessary to Deploy Operations Manager 2007 R2

The following group and accounts must be created prior to deploying Operations Manager 2007 R2:

  • Domain security group for the administrators group of the management group.

  • Action Account for the management server. It must have User privileges on the management server.

  • SDK and Config Service accounts. They can use the same account. It must have administrative privileges on the management server and system administrator privileges on the instance of SQL Server that will host the Operations Manager 2007 R2 database.

For more information about Operations Manager 2007 R2 accounts, see Account Information for Operations Manager 2007 in the Operations Manager 2007 Security Guide at https://go.microsoft.com/fwlink/?LinkId=64017

Run the Operations Manager 2007 R2 Prerequisite Viewer

Verify that the computer meets the software requirements of Operations Manager 2007 R2 by using the Prerequisite Viewer.

To use the Prerequisite Viewer single server configuration

  1. On the server that you are going to install Operations Manager 2007 R2 on, log on with an account that has Administrator rights.

  2. On your installation media, start SetupOM.exe. This starts the System Center Operations Manager 2007 R2 Setup on the Start page.

  3. Under the Prepare heading, click Check Prerequisites to start the Prerequisite Viewer.

  4. In the Components box, select all options, which are Operational Database, Server, Console, Power Shell, Web Console, Reporting, and Data Warehouse, and then click Check.

    Note

    When all components are selected, the Prerequisite Viewer checks for the presence of Windows Server 2003 SP1, SQL Server 2005 SP1 or higher, SQL Server Reporting Services SP1, MDAC version 2.80.1022.0 or higher, .NET Framework version 2.0, .NET Framework 3.0 components, WS-MAN v1.1, and Windows Power Shell. It then checks to ensure that the WWW service is running and set to automatic startup mode.

    Note

    The results are displayed at the bottom of the Prerequisite Viewer. If there are any deficiencies, they are marked either as a Warning or as Failed. Warnings can be ignored at the risk of degraded performance; Failed prerequisites must be fixed before the installation can proceed. You can close the Prerequisite Viewer, fix the items, and rerun the Prerequisite Viewer checks as many times as necessary until a Pass evaluation is achieved on all items. You can click any row for more details and for remediation steps.

  5. When you are finished with the Prerequisite Viewer, click Close.

For the all-in-one installation, the Operations Manager 2007 R2 Prerequisite checker will confirm the presence of the following components:

The Operations Manager 2007 R2 Prerequisite checker does not confirm the presence of the following items and you must install them manually if you want the named functionality or if necessary

Deploy an Operations Manager 2007 R2 Management Group on a Single Computer by Using the Setup Wizard

Use the following procedure to deploy the Operations Manager 2007 R2 server components required for a management group on a single computer by using the Setup Wizard. The required server components for a management group are the OperationsManager database, a management server, and an Operations console.

To deploy an Operations Manager 2007 R2 Management Group by using the Setup Wizard

  1. Use local administrator privileges to log on to the computer. This account must have system administrator privileges on the instance of SQL Server that will host the Operations Manager 2007 R2 databases.

  2. On the Operations Manager 2007 R2 installation media, double-click SetupOM.exe.

  3. On the Start page, select Install Operations Manager 2007 R2.

  4. When the Welcome page appears, click Next.

  5. On the End-User License Agreement page, accept the agreement, and then click Next.

  6. On the Product Registration page, type the information in the text boxes (the CD key is required), and then click Next.

  7. When the Custom Setup page displays, leave the components set to their defaults, and then click Next.

  8. On the Management Group Configuration page, do the following:

    1. Type the name you want for the management group in the Management Group box. The name of a management group cannot be changed.

      Note

      The management group name cannot contain the following characters: ( ) ^ ~ : ; . ! ? " , ' ` @ # % \ / * + = $ | & [ ] <>{}, or have a leading or trailing space. It is recommended that the management group name be unique within your organization if you plan to connect Operations Manager 2007 R2 management groups.

    2. Click Browse and select the universal or global security group that you want added to the management group's administrator’s role, and then click OK.

      Important

      The person installing the management group must be a member of the specified universal or global security group to run the Operations console.

    3. Click Next.

  9. On the SQL Server Database Instance page, in the SQL Server Database Instance list, select the instance of SQL Server on which you want to install the Operations Manager 2007 R2 database and then click Next.

  10. On the Database and Log File Options page, in the Database size text box, type the initial size of the operational database or leave the default of 1,000 MB, and then click Next.

    Note

    To change the default database name or installation location of either the data file or the log file, click Advanced, make the changes, click OK, and then click Next to continue.

  11. On the Management Server Action Account page, do one of the following:

    • Select Local System, and 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. If User Account is provided in alias@contoso.com format, the value in Domain or local computer is ignored.

    Note

    If you plan to deploy agents to remote computers from the Operations Manager 2007 R2 Operations console, the management server action account (MSAA) must have administrative privileges on these remote computers.

  12. On the SDK and Config Service Account page, do one of the following:

    • Select Local System, and click Next.

    • Select Domain or Local Account, type the User Account and Password, select the Domain or local computer from the list, and then click Next. If User Account is provided in alias@contoso.com format, the value in Domain or local computer is ignored.

  13. On the Web Console Authentication Configuration page, select Use Windows Authentication if the console will be accessed only over an intranet. Select Use Forms Authentication if the console will be accessed over the Internet.

  14. On the Operations Manager Error Reports page, either 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, or select Do you want to send error reports to Microsoft and do the following:

    1. Select Automatically send error reports about this product to Microsoft without prompting the user, or leave the default option, Prompt the user for approval before sending error reports to Microsoft, selected.

    2. Click Next.

  15. On the Customer Experience Improvement Program page, do one of the following:

    • Leave the default option of I don't want to join the program selected if you do not want your organization to participate in the program, and then click Next.

    Or

    • Select Join the Customer Experience Improvement Program if you want your organization to participate in the program, and then click Next.
  16. On the Ready to Install page, click Install. The Installing System Center Operations Manager 2007 R2 page will appear and provide installation progress.

  17. When the Completing the System Center Operations Manager 2007 R2 Setup Wizard page appears, do the following:

    • Leave the Backup Encryption Key box selected to back up the encryption key.

      Note

      Without a backup of the root management server key, you would need to re-enter all of your Run-As accounts if you had to rebuild the root management server. In larger environments, this rebuild could involve hundreds of accounts. A copy of the encryption key is also necessary to promote a secondary management server to the role of the root management server in case RMS fails. For more information about the Encryption Key Backup or Restore Wizard, see: https://go.microsoft.com/fwlink/?LinkId=87387

    • Leave Start the Console selected to open the Operations console.

      Important

      To open the Operations console, you must be a member of an Operations Manager 2007 R2 role for the management group. For information about adding a user to a role, see Security Considerations in Operations Manager 2007 at https://go.microsoft.com/fwlink/?LinkId=90675

    • Click Finish.