Export (0) Print
Expand All

Preparing to Upgrade Operations Manager 2007

Updated: May 22, 2009

Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1

This section starts with a checklist of tasks to complete before you start your upgrade. Next, it provides step-by-step procedures for completing the most critical pre-upgrade tasks from the Pre-upgrade Tasks table.

Pre-Upgrade Checklist

  1. Get verified, recent backups of the OperationsManager, OperationsManagerDW, and Reporting databases.For information about how to back up and restore the Operations Manager database, see “How to Schedule Backups of Operations Manager Databases” at http://go.microsoft.com/fwlink/?LinkId=96638.

  2. Document the username and password for each service account that is used in your management group. At the least, this should include the following: the SDK and Config account, the management server action account (MSAA), the DWwriter account, and the DWreader account. These will be needed if you have to perform a recovery of Operations Manager 2007 components.

  3. Inspect state views, alert views, performance views, and note the latency when you bring up each view.

  4. Read the upgrade release notes.

  5. Plan the order in which you will upgrade Operations Manager 2007 components and write it down. Share your upgrade plans with all key stakeholders.

  6. Inspect the Discovered inventory for Health Service Watcher class. Record the number and the names of agents whose health state is not listed as healthy.  It is likely that these will not upgrade successfully.

  7. In SQL Server Management Studio, inspect the OperationsManager database. Check the database free space and transaction log size. The database should have more than 50% free space, and the transaction log size must be 50% of the total database size. Ensure that the disk drives that the databases and transaction logs are on are not nearing their capacity as the upgrade process might require TempDB, OperationsManager database or transaction log growth.

  8. Evaluate the performance of all the SQL Server servers in your management group. Check CPU utilization, disk I/O, and memory usage to make sure that the servers have sufficient capacity to support the upgrade procedure and ongoing operations.

  9. Review your sealed management packs and see if there are updates available for them. If there are updates available, consider updating them immediately before your upgrade, or immediately after you complete your upgrade.

  10. Perform test failovers of clustered components (especially the RMS) to ensure that each node can successfully run the component and to find and fix any issues with the cluster configuration.

  11. Make sure that the clustered RMS services are all set to manual, and that they are started only on the Active node.  If you have applied System Center Operations Manager hotfixes, they may have left the passive node services set to automatic and started.

  12. Review the Operations Manager 2007 event logs on the RMS and management servers; look for reoccurring warning or critical events. Address them and save a copy of the event logs before you perform your upgrade.

Pre-upgrade procedures

To back up the encryption key

  1. Log on to the computer that hosts the root management server by using an account that is a member of the Administrators group.

  2. Open a Command Prompt window as an administrator by using the Run as administrator option.

  3. At the command prompt, type cd\<path of Operations Manager>, and then press ENTER.

  4. To back up the encryption key, do the following:

    1. Type SecureStorageBackup Backup <BackupFile>, and then press ENTER.

    2. At the Please enter the password to use for storage/retrieval prompt, type a password that is at least eight characters long, and then press ENTER.

    3. At the Please re-enter your password prompt, type the same password, and then press ENTER.

For more information about how to back up the encryption key, see the “How to Back Up the Encryption Key” topic in Operations Manager 2007 Help.

To export unsealed management packs

  1. Log on to the Operations console with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 management group.

  2. In the Operations console, click Administration.

  3. In the Administration pane, click Management Packs to display the list of imported management packs.

  4. In the Management Packs pane, right-click the custom management pack that you want to export, and then click Export Management Pack.

  5. In the Browse For Folder dialog box, expand the path for the location to save the file, and then click OK.

To remove agents that are in the pending management container

  1. Log on to Operations console with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 management group.

  2. In the Administration pane, expand Device Management, and then click Pending Management.

  3. Right-click each agent, and then click Approve or Reject.

CautionCaution
When you are using an RDP connection to access a server remotely, use the command mstsc.exe /console (mstsc.exe /admin on Windows Vista, Windows Server 2008, or Windows 7) to launch the connection. Otherwise, the log files that are collected during setup will be lost when your system restarts. These log files might be critical to troubleshooting if the upgrade fails.

To increase the free space for the OperationsManager database and log files

  1. On the computer that hosts the Operations Manager database, open SQL Server Management Studio.

  2. In the Connect to Server dialog box, in the Server Type list, select Database Engine.

  3. In the Server Name list, select the server and instance for your OperationsManager database (for example, computer\INSTANCE1).

  4. In the Authentication list, select Windows Authentication, and then click Connect.

  5. In the Object Explorer pane, expand Databases, right-click OperationsManager, and then click Properties.

  6. In the Database Properties - OperationsManager dialog box, under Select a page, click Files.

  7. In the results pane, increase the Initial Size value for the MOM_DATA database by 50%.

    noteNote
    This step is not required if free space already exceeds 50%.

  8. Set the Initial Size value for the MOM_LOG to be 50% of the total size of the database. For example, if the OperationsManager database size is 100 GB, the log file size should be 50 GB. Then click OK.

To increase the free space for the OperationsManagerDW database and log files

  1. On the computer that hosts the Reporting data warehouse, open SQL Server Management Studio.

  2. In the Connect to Server dialog box, in the Server Type list, select Database Engine.

  3. In the Server Name list, select the server and instance for your Operations Manager database (for example, computer\INSTANCE1).

  4. In the Authentication list, select Windows Authentication, and then click Connect.

  5. In the Object Explorer pane, expand Databases, right-click OperationsManagerDW, and then click Properties.

  6. In the Database Properties - OperationsManagerDW dialog box, under Select a page, click Files.

  7. In the results pane, increase the Initial Size value for the MOM_DATA database file by 50%.

    noteNote
    This step is not required if free space already exceeds 50%.

  8. Increase the Initial Size value for the MOM_LOG database by 50%, and then click OK.

To remove agents from computers that have stand-alone Operations consoles

  1. Log on to the Operations console with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 management group.

  2. In the Operations console, select the Administration view.

  3. In the navigation pane, expand the Administration container, and expand Device Management, and then click Agent Managed.

  4. In the results pane, right-click the computers for which you want to uninstall the agent, and then select Uninstall.

  5. In the Uninstall Agents dialog box, either leave Use selected Management Server Action Account selected, or do the following:

    1. Select Other user account.

    2. Type the User name and Password, and type or select the Domain from the list. Select This is a local computer account, not a domain account if the account is a local computer account.

      noteNote
      The account must have administrative rights on the computer or the uninstall process will fail.

    3. Click Uninstall.

  6. In the Agent Management Task Status dialog box, the Status for each selected computer changes from Queued to Success.

  7. Click Close.

To disable subscriptions

  1. Log on to the Operations console account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 management group.

  2. In the Operations console, select the Administration view.

  3. In the navigation pane, expand Administration, expand the Notifications container, and then click Subscriptions.

  4. In the Subscriptions pane, right-click each subscription, and then click Disable.

    noteNote
    Multiselect does not work when you are disabling subscriptions.

To disable Connectors

  1. For Windows Server 2003, open Control Panel, click Administrative Tools, and then click Services.

  2. In the Name column, right-click the Connector that you want to control, and then click Stop.

  3. For Windows Server 2008, click Start, click Administrative Tools, and then click Services.

  4. In the Name column, right-click the Connector that you want to control, and then click Stop.

  5. For HP Operations Manager, a second service, System Center OpsMgr Event Consumer for HP OpenView, must be stopped by selecting it in the Name column, right-clicking it, and then selecting Stop.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft