The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. © 2009 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, ActiveSync, Internet Explorer, JScript, SharePoint, SQL Server, Visio, Visual Basic, Visual Studio, Win32, Windows, Windows PowerShell, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies. All trademarks are property of their respective owners. Revision History Release Date Changes May 2009 The Operations Manager 2007 R2 release of this guide contains the following updates and additions: Added procedures for upgrading to Operations Manager 2007 R2 Added procedures for upgrading from SQL Server 2005 to SQL Server 2008 for Operations Manager database components
 Whether this task interferes with the service  Risk (to the stability of your data and monitoring environment)  Mitigation (of downtime, interference, or risk) Step-by-step information for each of the pre-upgrade is available in the topic. Task Downtime Interference Risk Mitigation Back up database No No Low Back up encryption key No No Low Export unsealed management packs No No Low Remove agents from pending No No Low Increase space available for data and log files on OperationsManager database. Not required if the database free space available exceeds 50%. Transaction logs should be 50% of the total size of the OperationsManager database No No Low Remove agents from computers with Operations consoles No No Low Disable notification subscriptions No No notifications are sent during the upgrade. Low After upgrade, check for any alerts that were missed. Disable Connectors Yes. Event states and alerts are not Yes. states and alerts are not Low Verify with EMC that events and
synchronized with EMC Smarts. synchronized with EMC Smarts. alerts are cached. Upgrade agents Yes, if you upgrade 300 agents or more at one time Yes, agents can be down for approximately and hour and no monitoring information will be gathered during this time. Medium Do not upgrade more than 299 agents at one time Upgrade Order The following shows the Operations Manager components to upgrade in the order in which they should be upgraded. This table provides the following information:  Component  Whether upgrading this component results in the service being completely unavailable  Whether upgrading this component interferes with the service  Risk (to the stability of your data and monitoring environment)  Mitigation (of downtime, interference, or risk) In an environment composed of connected management groups, first upgrade the Operations Manager 2007 components in the top tier and then upgrade the components in bottom tier. Step-by-step procedures for completing each of the upgrade tasks are available in either the or topics. Component Downtime Interference Risk Mitigation Root management server Yes. The SDK and Console will be unavailable. Yes. The management group will be unavailable. Data will not be and management servers will queue the data. Medium Read all upgrade and troubleshooting documentation before you start. Make sure you follow the exact instructions. If possible, have a Cluster SME or Operations
(http://go.microsoft.com/fwlink/?LinkID=167911) if you are upgrading from SQL Server 2005 to SQL Server 2008 with Operations Manager 2007 SP1. Use the following steps. Caution These steps apply to upgrading to the RTM version of SQL Server 2008. Do not upgrade to SQL Server 2008 with SP1 or to SQL Server 2008 with SP2 until after you have completed all of these steps. To upgrade from SQL Server 2005 to SQL Server 2008 1. Run the SRSUpgradeTool program. This tool and restores three configuration files that were modified during Operations Manager 2007 Reporting installation. Run the following command from a command prompt: SRSUpgradeTool.exe /InstanceName:<InstanceName> /Action:PreSQLUpgrade Where <InstanceName> is the name of the SQL instance that houses the SQL Reporting Services database. If you used the default instance name, you can use MSSQLSERVER. 2. Restart the SQL Server Reporting Services service, and verify the configuration by using Reporting Services Configuration Manager. 3. Upgrade the SQL Server 2005 installation to SQL Server 2008, using the procedures outlined in the SQL Server 2008 product documentation. Caution Do not upgrade to SQL Server 2008 SP1 until after you have completed these steps. 4. Run the SRSUpgradeTool program to update the registry entries for Operations Manager 2007 Reporting to point to the new SQL Server Reporting Services location. Run the following command: SRSUpgradeTool.exe /InstanceName:<InstanceName> /Action:PostSQLUpgrade 5. Run the SRSUpgradeHelper program to move the Operations Manager Reporting files to the new SQL Server Reporting Services directory and to set the SQL Server Reporting Services configuration. Run the following command: Msiexec /i SRSUpgradeHelper.msi DATAREADER_DOMAIN=Lab DATAREADER_USER=momsdk MGSERVER=cRMS SRS_SERVER=cRMS\instance1 Important After you complete the upgrade to SQL Server 2008 you must apply SQL Server 2008 SP1. Operations Manager 2007 R2 requires SQL Server 2008 SP1.
Completing the Post-Upgrade Tasks After you finish upgrading your computers to Microsoft System Center Operations Manager 2007 R2, go through this checklist and perform the following tasks before you resume monitoring. Post-Upgrade Checklist 1. After you upgrade agents, check the Health Service Watcher state view and compare the number of agents that are listed and that are in a healthy state with the same count and health state from the pre-upgrade checklist. 2. Review the event logs on the RMS and all management servers for new errors. 3. Perform a test failover and failback of all clustered components. 4. Sort alerts by the last-modified column to review new alerts. 5. Check the CPU utilization and disk I/O on your database servers that support Operations Manager 2007 R2 components to ensure that they are functioning normally. 6. In the Operations console, open the state, alert, and performance views to note the latency when you open these views. 7. If you have Reporting installed, open the reporting view and run a generic performance report to ensure that reporting is functioning correctly. 8. In the Operations console, open the Authoring view to ensure that it populates correctly. 9. If you did not upgrade your sealed management packs before the upgrade, do so now. 10. Re-enable notifications and connectors and then test them. 11. Review My Workspace to ensure that it has populated as expected. 12. Re-deploy any agents that you uninstalled during the upgrade process. 13. Run the following SQL query to clean up the localizedtext and publishmessage tables. -- Create temp to speed up looking for a PublisherId when we know the MessageId TRY CREATE TABLE #PublisherMessageReverseIndex(MessageStringId UNIQUEIDENTIFIER, MessageId INT) CREATE CLUSTERED INDEX #PublisherMessageReverseIndex_CI ON #PublisherMessageReverseIndex(MessageStringId) INSERT INTO #PublisherMessageReverseIndex (MessageStringId, MessageId) SELECT MessageStringId, MessageId FROM dbo.PublisherMessages