SYSTEM CENTER OPERATIONS MANGER 2012 ......NTERNAL O NOT SHARE I DO UMENT,D Spring 2011 SYSTEM CENTER OPERATIONS MANGER 2012 UPGRADE DOCUMENT” FOR SCOM 2007 R2 DISTRIBUTED MANAGEMENT

INTERNAL DOCUMENT, DO NOT SHARE

Spring 2011

SYSTEM CENTER

OPERATIONS MANGER

2012 UPGRADE

DOCUMENT”

FOR SCOM 2007 R2 DISTRIBUTED MANAGEMENT

GROUP THAT MEETS THE SUPPORTED

CONFIGURATION REQUIREMENTS FOR SCOM

2012 RC **Covers lessons learned during our upgrade Process for a specific scenario in

the lab**

Author: Satish Pandita Gurdeep Dutta The issues we experienced during upgrade are highlighted in “red” in this document


Spring 2011

Contents

Current SCOM 2007 infrastructure for satishdomain.com ............................................................ 4

Business justification for implementing SCOM 2012 ..................................................................... 5

Challenges with current SCOM 2007 R2 infrastructure for SATISSHDOMAIN.COM .............. 5

Single Root Management Server is handling multiple services/workload ................................. 5

High Availability ...................................................................................................................... 5

SCOM 2012 Features ...................................................................................................................... 7

High Availability .......................................................................................................................... 7

Performance and Scalability bottleneck ................................................................................. 7

SCOM 2012 in place Upgrade Process at SATISHDOMAIN.COM .................................................... 9

Prerequisites ............................................................................................................................... 9

Software Requirements (verify Pre-requests) ............................................................................ 9

Database Considerations ........................................................................................................ 9

Steps For Upgrade Process from SCOM 2007 R2 TO SCOM 2012 ................................................ 10

Step by Step Instructions on Upgrade Process ............................................................................. 12

1. Import the Upgrade Helper management pack ................................................................... 13

2. Move all agents that report to the RMS to a secondary management server. ....................................................................................................................................... 20

3. Back up the encryption key ............................................................................................... 20

4. Review the Operations Manager 2007 R2 event logs .......................................................... 24

5. Remove agents from pending management if any ........................................................... 25

6. Verify that you have a supported SQL Server collation on all databases and instances of databases .............................................................................................................................. 25

7. Upgrade the manually installed agents ............................................................................. 26

8. Upgrade the secondary management servers .................................................................. 27


Spring 2011

9. Upgrade gateways, if present ............................................................................................... 59

10. Upgrade the push-installed agents .................................................................................... 59

11. Check for any active, connected consoles to the root ....................................................... 63

Management server .................................................................................................................. 63

12. Disable all notification subscriptions .................................................................................. 64

13. Stop services or disable any connectors that are installed ................................................ 70

14. Verify that your operational database has enough free space .......................................... 70

15. Back up the databases ........................................................................................................ 70

Use Backup methodology you have ......................................................................................... 70

16. Restore the encryption key on secondary management server ........................................ 70

17. Run management group upgrade on the root management server ................................. 70

Restarted the Server and verify upgrade status under “Operations Manager Upgrade MP” ........................................................................................................................... 85

18. Upgrade or install the optional features, such as the web consoles and........................... 85

Reporting server ....................................................................................................................... 85

19. Re-enable notification subscriptions .................................................................................. 85

20. Restart or re-enable the service for any connectors that are installed ............................. 87

21. Distribute the Run As account ............................................................................................ 87

22. Update overrides ................................................................................................................ 87

23. Restart RMS Server ........................................................................................................... 101

24. Verify the success of the upgrade ..................................................................................... 101


Spring 2011

CURRENT SCOM 2007 INFRASTRUCTURE FOR SATISHDOMAIN.COM

SATISH100COPY2Root Management Server

SATISH200Management Server

SATISH200COPY1Management Server

SQL Server

Agent Agent

Automatic Failover

Agent Agent

One Root Management Server SATISH100COPY2.

Two Management Servers SATISH200 and SATISH200COPY1

SCOM databases are hosted SATISH100COPY2

NO VM’s


Spring 2011

BUSINESS JUSTIFICATION FOR IMPLEMENTING SCOM 2012

Challenges with current SCOM 2007 R2 infrastructure for SATISSHDOMAIN.COM

Single Root Management Server is handling multiple services/workload

o In SCOM 2007 R2, Root Management Server (RMS) provided following

services/workload, and thus a single point of failure, and Performance and scalability Bottleneck

Alert Notifications Distribution of Configuration to agents Role based account Control Connector to other Management Systems Availability Dependency Monitor DB Grooming Health Aggregation

All the above services happen at the Root Management Server If we lose the Root Management Server none of the above services are going to work.

High Availability

High Availability for RMS (SATISH100COPY2) requires Clustering

Solves single point of failure, however o Complex to setup o Difficult to Patch/Upgrade o Do not have this implemented in our environment


Spring 2011

Our current option to recover from RMS is to promote another Management server as RMS

o Requires Manual Steps, so no high availability o Currently we do not have a hot standby Management Server o It is not a best practice/recommended approach to promote existing

Management Server to RMS.

Performance and Scalability bottleneck

Whether we add more agents and even though they report to secondary management servers, the health availability is still done at RMS Level

Because the SDK Service is running only on RMS, all workflows e.g. group membership calculation, health aggregation, Console access is still tied to RMS Server only.

Configurations

All overrides by default are saved to “Default Management Pack” and if proper attention is not paid, it leads to administrative burden

Limited options in Network Monitoring


Spring 2011

SCOM 2012 FEATURES

High Availability

High Availability is out of the Box

o For all Windows Agents o For Cross Platform Monitoring (by creating custom resource pools) o There is no RMS, All Management Servers are in peers, It is a simple peer to

peer topology, If we lose one, It will still work o You can easily start small and Scale out o Network Load balancer can be used to point consoles to a single host name,

which can further load balance to any Management Server

Performance and Scalability bottleneck

Resource Pool o Ability to distribute workloads across multiple Management Servers

Any Management Server can do following tasks

Group Calculation

Availability

Distributed Monitor Health Roll up

DB Grooming

Notification

Management Server Changes that improves performance

o Configuration Service Runs on all Management Servers Store config data in DB instead of Memory and thus faster start up

o SDK Service

Runs on all Management server and thus provides high availability for agents, consoles

Console can use any management Server to connect and we can now put a Load Balancer to connect to Console


Spring 2011

Network Monitoring

Network Monitoring out of the box

Port/Interface Monitoring o Up/Down (Operational & Admin status) o Volumes of inbound/outbound traffic o %Utilization o Drop and Broadcast rates o Processor %Utilization o Memory Counters (Cisco) o Free Memory

Reporting

Multi-vendor Support

Multi-Protocol support o SNMP V1/V2/V3 o IPv4 and IPv6

Dashboards

New Service Level Dashboard

Widgets o Alerts o Performance o State

Multi-vendor Support

Multi-Protocol support o SNMP V1/V2/V3 o IPv4 and IPv6

.Net Application Monitoring

Server Side and Client Side Perspectives

Performance of Web Apps

Application Monitoring Tools


Spring 2011

o Application Advisor o Application Diagnostics

SCOM 2012 IN PLACE UPGRADE PROCESS AT SATISHDOMAIN.COM

Prerequisites

Software Requirements (verify Pre-requests) Server:

.NET 3.5 or 4.0 (all server roles) **Note in my test lab the setup asked for .NET4.0 for all management Servers**

Cumulative Update 4 (all server roles ) ** We have CU5**

Management Server, Reporting Server, Web Console, Gateway Server (OS)

Windows Server 2008 R2 (64 bit) Agent

Windows Server 2003 SP2 and above

Windows Server 2008 SP2 and above

Windows Server 2008 R2

Windows XP Professional SP3 and above

Windows Vista SP2 and above

Windows 7

Database Considerations

SQL 2008 SP1 and above

No 32 Bit

SQL Server Agent Service must be started


Spring 2011

Full Test Search enabled

DB 75GB

DW 1TB

DB_Owner role must be a domain account

If SQL Server authentication is Mixed Mode

Add a local SQL Server Login to the Operational

Else Data Access Service will not start

For detailed Hardware Requirements use Operations Manager Sizing Helper tool

STEPS FOR UPGRADE PROCESS FROM SCOM 2007 R2 TO SCOM 2012

1. Import the Upgrade Helper management pack No downtime or inference; low risk

2. Move all agents that report to the RMS to a secondary management server.

No Agent is reporting to RMS in our scenario

3. Back up the encryption key. No downtime or inference; low risk

4. Review the Operations Manager 2007 R2 event logs No downtime or inference; low risk

5. Remove agents from pending management Review, Verify and troubleshoot if required

6. Verify that you have a supported SQL Server collation on all databases and instances of databases Review, Verify and troubleshoot, if required

7. Upgrade the manually installed agents

8. Upgrade the secondary management servers


Spring 2011

Upgrading a secondary management server is just one phase of the distributed upgrade process. Upgrade is not completed until you have upgraded all of the other features in your management group.

9. Upgrade gateways, if present

No Gateways in our scenario

10. Upgrade the push-installed agents Review, Verify and troubleshoot if required

11. Check for any active, connected consoles to the root management server

12. Disable all notification subscriptions Downtime: Notification won’t be sent

13. Stop services or disable any connectors that are installed

Not applicable in our environment

14. Verify that your operational database has enough free space

15. Back up the databases

Use Backup methodology you have

16. Restore the encryption key on secondary management server (not reqd in this scenario)

No downtime or interference; low risk. Required only if the root management server (RMS) does not meet the supported configuration requirements for System Center 2012 – Operations Manager. This should be performed just prior to management group upgrade

17. Run management group upgrade on the root management server Downtime Required

18. Upgrade or install the optional features, such as the web consoles and Reporting server

19. Re-enable notification subscriptions

20. Restart or re-enable the service for any connectors that are installed

21. Distribute the Run As account

22. Update overrides

23. Restart RMS Server


Spring 2011

24. Verify the success of the upgrade

STEP BY STEP INSTRUCTIONS ON UPGRADE PROCESS The following step by step instructions are performed in the test LAB and same procedures can be applied for the above scenario, all software prerequisites are already met. CU5 is already implemented Lab Configuration is defined the following screen captures Management Servers

Agents Managed

State View showing CU5


Spring 2011

Web Console

1. Import the Upgrade Helper management pack The objective of “Upgrade Helper Management Pack “is to track/ review which servers and agents are next to be upgraded to SCOM 2012 as per the upgrade best practices. To install the Upgrade Helper Management Pack, download the SCOM 2012 RC (in this case)

Extract the Bits

Go to Management server (SATISH200)

Launch SCOM Console ->Administration->Management Pack->Import Management Pack


Spring 2011

Clock No (in the following screen)

Browse to the folder in which you extracted SCOM 2011RC bits and go to Management Pack folder and double click “OperationsManager.Upgrade.MP” as shown below


Spring 2011

Click on install (as shown below, make sure the screen looks like the following and no error is shown)


Spring 2011

Once the import/Install is completed, following screen should appear and then click on close.

Next on any one of the Management Servers go to Monitoring Tab ->Operations Manager Upgrade MP You will see the steps to be completed for each Upgrade Process (see screen captures below)


Spring 2011


Spring 2011


Spring 2011


Spring 2011

2. Move all agents that report to the RMS to a secondary management server.

No Agent is reporting to RMS in our scenario

3. Back up the encryption key

Log on to the secondary Management Server with account that has local administrator rights (SATISH200 in this case)

Run or Copy file “securestoragebackup.exe” from SCOM 2007R2 installation media on the local drive (in my scenario I copies the folder supporttools from SCOM 2007 R2 installation media on local drive, I also created a folder called RMSKEYBACKUP on local drive to store the RMSEncryptionKey

Open a command prompt window by using the Run as Administrator option.

Run the following command (e.g.)

Following screen will appear


Spring 2011


Spring 2011

Specify the path including filename (see below)


Spring 2011

Click Next and specify the password


Spring 2011

Click “Next” and then click “finish "

4. Review the Operations Manager 2007 R2 event logs Review the event logs for Operations Manager 2007 R2 on the root management server (RMS) and on the management servers to look for recurring warning or critical events. Address them and save a copy of the event logs before you perform your upgrade


Spring 2011

See example below ( RMS)

5. Remove agents from pending management if any

6. Verify that you have a supported SQL Server collation on all databases and instances of databases

SQL Server collation for all databases and database instances must be SQL_Latin1_General_CP1_CI_AS; no other collation configurations are supported. You must ensure that all databases and database instances have the correct collation before you run upgrade on the management group.

To determine the SQL Server collation of a database, you can check the database properties.

On the SQL Server that hosts SCOM databases, open SQL Server Management Studio, right-click the database you want to check, and then click Properties. The collation is listed under Maintenance See screen captures below


Spring 2011

7. Upgrade the manually installed agents

http://technet.microsoft.com/en-us/library/305994ab-5f0f-425b-918e-1935864214ab#BKMK_UpgradingManualAgents


Spring 2011

8. Upgrade the secondary management servers

Log on to the secondary management server with an account that is a member of the Operations Manager Administrators role for your Operations Manager 2007 R2 management group and a local administrator on the computer

In this scenario, first we will upgrade Management Server “Satish200” and then Management Server “satish200copy1”

SCOM 2012 RC was already copied on the local drive on all management servers including .NET 4.0 on all management servers

Launch “setup.exe” see screen captures below

Click on Install (see screen below)


Spring 2011

Click “Next” in my case following warning appeared as 2007R2 Web Console was also installed on this server


Spring 2011


Spring 2011


Spring 2011


Spring 2011


Spring 2011

Following screen will appear, click on “Upgrade” see picture below


Spring 2011


Spring 2011

During above upgrade process got error “when the upgrade was happening for the Management Server” for server SATISH200, as a result I had to exit from the “setup” process (See above highlighted in yellow)

Next if I ran install again, it did not give me the upgrade option, instead tries to do a clean install.

Even though SCOM 2007 R2 bits were uninstalled during upgrade, I do see this server under management servers and the agents under “Agent Management” that reports to this MS in the SOCM 2007 R2 Console

In the OpsmgrSetup log I see “OMSERVER.MSI returned error 1603” see below

Error: :Error:User 'satishdomain\scomadmin' is Administrator on the management server SATISH100Copy2.satishdomain.com ebug: :Condition wasnt defined for rule 'Select_UI_UpgradeRules'. [10:18:27]: Info: :Beginning evaluation of rule '' [10:18:27]: Debug: :Condition wasnt defined for rule ''. [10:18:27]: Warn: :Rule '' failed.


Spring 2011

[10:18:27]: Info: :Finished evaluation of rule '' [10:18:27]: Info: :Finished evaluation of rule 'Select_UI_UpgradeRules' [10:18:27]: Debug: :Action UpgradeMGPreprocessor will not be needed. [10:18:27]: Always: :Done validating action list; now running individual actions. [10:18:27]: Always: :Current Action: InitializeServerPreprocessor [10:18:27]: Debug: :Setting Install State to the InstallItem Management Server [10:18:27]: Debug: :Setting Target Directory for this msi [10:18:27]: Debug: :Set the OpsMgr Install directory to: C:\Program Files\System Center Operations Manager 2012 [10:18:27]: Debug: :Setting Error Reporting bit for this msi lways: :LaunchMSI: Setting rollback to true [10:18:31]: Error: :LaunchMSI: MSI C:\SCOM2012RC\RCBITS\Setup\AMD64\Server\OMServer.msi returned error 1603 [10:18:31]: Error: :ProcessInstalls: Install Item Management Server failed to install. We did not launch the post process delegate. [10:18:31]: Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Management Server [10:18:31]: Info: :SetProgressScreen: FinishMinorStep. [10:18:31]: Always: :!***** Installing: OMDATAWAREHOUSE *** [10:18:31]: Info: :ProcessInstalls: Rollback is set and we are not doing an uninstall so we will stop processing installs [10:18:31]: Always: :**************************************************************** [10:18:31]: Always: :****Starting*RollBack******************************************* [10:18:31]: Always: :**************************************************************** [10:18:31]: Info: :SetProgressScreen: StartMinorStep. [10:18:31]: Always: :ProcessRollback: Skipping rollback for install item Management Server as it was not successfully installed. [10:18:31]: Info: :SetProgressScreen: StartMinorStep. [10:18:31]: Debug: :ProcessInstalls: Install Item Database Configuration has a Preprocessing delegate of RunXamlPreProcessor. Launching it now. [10:18:31]: Always: :LaunchExeSetup: Launching C:\SCOM2012RC\RCBITS\Setup\AMD64\SetupInstallItem.exe with arguments: [10:18:31]: Info: :SetProgressScreen: Init Exe Install progress. [10:18:31]: Always: :LaunchExeSetup: Install return value was: 0 [10:18:31]: Info: :CheckPointPassed is removing the Rollback property as this is an uninstall. [10:18:31]: Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Database Configuration [10:18:31]: Always: :ProcessInstalls: Install Item Database Configuration was successful. We will launch the post process delegate. [10:18:31]: Always: :Determining actions to be run.

At this point I decided to move the management server for all the agents that report to SATISH200.

Moved the agents to another Management Server to SATISH2OOCOPY2.

Deleted SATISH200 MANAGEMENT SERVER

Installed SCOM 2007 R2 Management Server role on SATISH200 Again and no web console

Installed CU5 Again Launched SCOM 2012 again, Click on setup (see picture below)


Spring 2011

Next Click on “Install”


Spring 2011

As you can see from the following screen did not get the warning that “Web console is installed and will be uninstalled” as I had to reinstall SCOM 2007 R2 on this due to some issues and did not choose web console to install


Spring 2011


Spring 2011


Spring 2011

The installation was successful Next we need to verify the upgrade was successful go to any of SCOM 2007 Management servers/console, launch console, go to monitoring, Operations manager upgrade MP, step1 Upgrade secondary management servers” It should show the newly upgraded Management server as “Healthy”, see picture below


Spring 2011

Next we need to upgrade the agents that report to this Management Server (satish200), that I upgraded to SCOM 2012 Launch SCOM 2007 Console from a different SCOM 2007 Management Server, go to “Administration”, go to “Pending Management”, Select the “agents” and Click on “Approve”

Once you click on “Approve” and then click on “Update” as shown below


Spring 2011


Spring 2011


Spring 2011

Next go to “Administration”, “Management Servers” and see the new Version See pictures below Note: you cannot launch SCOM 2012 Console till all Management Servers are upgraded to SCOM 2012”


Spring 2011

Next we need to upgrade remaining Management Servers In this case I will be upgrading server (SATISH200COPY1) Before I upgrade this server, I will uninstall SCOM 2007 WEB CONSOLE Server as I had experienced the above issue (see above, my comments in Red) Uninstall SCOM 2007 Web Console (launch SCOM 2007 SETUP.exe) See picture below


Spring 2011

Click next


Spring 2011

Reinstall SCOM 2007 R2 CU5, by clicking repair


Spring 2011

Restart the Server (SATISH200COPY1) Note: Next when I tried to install SCOM 2012, it error out that SCOM 2007 CONSOLE OR WEBCONSE needs to be uninstalled and reinstalled. Finally after some troubleshooting, I launched SCOM 2007 R2 Setup again and clicked on modify and noticed that <User Interface >,<Command Shell> was not installed Installed the same

Next restart the computer again, else during SCOM 2012 upgrade you will get warning about “pending reboot” Next install SCOM 2012


Spring 2011


Spring 2011


Spring 2011


Spring 2011


Spring 2011


Spring 2011


Spring 2011


Spring 2011


Spring 2011

Click on “Close” and “Exit” At this point both secondary Management Servers are upgraded Go to SCOM 2007 R2 RMS( SATISH100COPY2) And verify 2

nd Management Server (Satish200copy1) that we upgraded is shown as health

See picture below


Spring 2011

9. Upgrade gateways, if present

(No gateways, in our scenario, skipped this step)

10. Upgrade the push-installed agents Next go to RMS/SCOM 2007 Console ->Monitoring-> Operations Manager Upgrade MP->Step 3a and upgrade the following agents (shown is warning) Note: we had already upgraded satish100 that is why it is shown as healthy) See picture below


Spring 2011

To Upgrade the above Agents

Go to Administration workspace, in the navigation pane under Device Management, click Pending Management.

In the Pending Management pane, under Type: Agent Requires Update, highlight and right-click each agent-managed computes listed, and then click Approve, see picture below Note: if you do not approve more than 200 agents at a time


Spring 2011



Spring 2011

Click on update (see above screen)


Spring 2011

In my scenario, I rejected the agents that failed upgrade

11. Check for any active, connected consoles to the root

Management server

Consoles that are connected to the Operations Manager 2007 R2 RMS might lose connectivity during the upgrade of the management group. Before you perform the upgrade of the management group, you should notify anyone who has a connected console to close the connection


Spring 2011

12. Disable all notification subscriptions Expect Downtime as Notification won’t be sent

You should disable notification subscription before you upgrade the management group to

ensure that notifications are not sent during the upgrade process.

To disable subscriptions

Go to SCOM 2007 R2 Console (in our scenario Server Satish200copy1)

In the Operations console, select the Administration view.

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

Select each subscription, and then click Disable in the Actions pane

See Screen Captures below

After you click on properties, following screen will appear


Spring 2011

Click Next


Spring 2011

Click Next


Spring 2011

Click Next


Spring 2011

Make sure you uncheck “Enable this Notification subscription” (see screen capture above) Click Finish and closed Next you should see the following screen e.g. “Exchange Notifications”: are not now shown as “Enabled=False” see below


Spring 2011

Repeat same steps for other subscriptions, should show as “Fasle” for all subscriptions, see below


Spring 2011

13. Stop services or disable any connectors that are installed Not applicable in my scenario

14. Verify that your operational database has enough free space

15. Back up the databases

Use Backup methodology you have

16. Restore the encryption key on secondary management server Did not do this step

No downtime or interference; low risk. Required only if the root management server (RMS) does not meet the supported configuration requirements for System Center 2012 – Operations Manager. This should be performed just prior to management group upgrade

17. Run management group upgrade on the root management server

In our scenario “SATISH100COPY2” is the RMS and has databases including DW also installed on this server

Launch SCOM 2012 Setup.exe and Run as “Administrator See Picture below


Spring 2011

Click on Install (see screen capture below)


Spring 2011

After I clicked Install (see above) I got the following POPUP

Looks like we don’t do a case-insensitive compare and/or we don’t understand the fqdn is the same as the netbios name of the box

In the registry HKLM\Software\Microsoft\Microsoft Operations manager\3.0\Reporting , I tried changing the values for DWBInstance, DefaultSDKServiceMachine and SRSinstance to the fqdn


Spring 2011

Ran Seup again and did not get the popup “Unable to Proceed”, so no issues


Spring 2011


Spring 2011

Got following prerequisites errors on the RMS


Spring 2011

Installed all the prerequisites( in error)

Verified the prerequisites again


Spring 2011


Spring 2011

N

Click on Next


Spring 2011


Spring 2011


Spring 2011


Spring 2011


Spring 2011


Spring 2011

Note: you need to have some patience during RMS upgrade and can take significant time


Spring 2011

Restarted the Server and verify upgrade status under “Operations Manager Upgrade MP”

18. Upgrade or install the optional features, such as the web consoles and

Reporting server e.g. Web Console, Reporting Server if any http://technet.microsoft.com/en-us/library/hh454969.aspx

19. Re-enable notification subscriptions

Open the Operations console from any management server

In the Operations console, in the navigation pane, click the Administration button

In the Administration pane, under Notifications, click Subscriptions.

In the Actions pane, click Enable for each subscription listed.

http://technet.microsoft.com/en-us/library/hh454969.aspx


Spring 2011

See Screen Capture below

Once you click on “Ok”, the alerts will be enabled see picture below, do this for all subscriptions one by one


Spring 2011

20. Restart or re-enable the service for any connectors that are installed Not available/required in this scenario

21. Distribute the Run As account

http://technet.microsoft.com/en-us/library/f79a28c9-4ee5-440c-be5a-00e24986c4c9#BKMK_DistributeRunAs

22. Update overrides

http://technet.microsoft.com/en-us/library/8c2dbaf4-2966-45e3-a72d-5de90ff4f495#BKMK_UpdateOverrides From Console Go to Administration->Run As Configuration->Profiles->select “Data Warehouse Account”, double click or click on properties **See screen capture below**




http://technet.microsoft.com/en-us/library/8c2dbaf4-2966-45e3-a72d-5de90ff4f495#BKMK_UpdateOverrides

http://technet.microsoft.com/en-us/library/8c2dbaf4-2966-45e3-a72d-5de90ff4f495#BKMK_UpdateOverrides


Spring 2011

Click “ Next” and then again “Next” You will see the following screen


Spring 2011

Click on “Remove” and remove these Run As Accounts


Spring 2011

Click on “Add” button and add the following account


Spring 2011

Next Select check box “A selected class, group, or object” ” See picture below


Spring 2011

Click on Select button,

Click on Class, following screen will appear


Spring 2011

In the Class Search dialog box, under Filter by (optional) type Operations Manager APM Data Transfer Service, and then click Search. Select the result and click OK, then click OK in the Add a Run As Account dialog box to associate that item with the Run As account. Add three more Run As accounts for the Data Warehouse Action Account. This time search for and add the following classes: Data Warehouse Synchronization Server Data Set Collection Server See Screen Captures below


Spring 2011


Spring 2011


Spring 2011

Next you will see following screen and click on Save


Spring 2011

Next do the same for Datawarehouse Report Deployment Account See steps below and the screen captures at the end

In the Profiles list, double-click Data Warehouse Report Deployment Account.

In the Run As Profile Wizard, click Next twice, or click Run As Accounts in the left pane.

Select Data Warehouse Report Deployment Account, and click Remove. Then click Add to add a new Run As Account.

In the Add a Run As Account dialog box, under Run As account, select Data Warehouse Report Deployment Account and select A selected class, group, or object.

Click Select, and then click Class.

In the Class Search dialog box, type Data Warehouse Synchronization Server, then click Search.

Select the result and click OK, then click OK in the Add a Run As Account dialog box to associate that item with the Run As account.

Add another Run As account for the Data Warehouse Report Deployment Account. This time search for and add Collection Server to associate that item with the Run As account.


Spring 2011

Click Save to create the Run As Profile.

Click Close.


Spring 2011


Spring 2011


Spring 2011

23. Restart RMS Server

24. Verify the success of the upgrade

Perform the following tasks to verify that the upgrade was successful.

Check the health state of the management servers and agents in the Health Service

Watcher state view. In the Administration workspace of the Operations console, ensure


Spring 2011

that the management servers and agents are healthy. In the Monitoring workspace, check

if there are any alerts related to the management group health.

Review the event logs of all the management servers for new errors.

Sort alerts by the last-modified column to review the new alerts.

Check the CPU utilization and disk I/O on your database servers to ensure that they are

functioning normally.

If the Reporting feature is installed, click Reporting, and then run a generic performance

report to ensure that Reporting is functioning correctly.

Re-deploy any agents that you uninstalled during the upgrade process

Run SQL Query on each Management Group

-- Create a temporary table to quickly find a PublisherId when you know the

MessageId.

BEGIN 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

-- Create a temporary table of message lengths, message IDs, and message

hashes with the

-- MessageStringId to quickly determine whether a message is duplicated.

Index the table.

CREATE TABLE #LTHashStrings (MessageStringId UNIQUEIDENTIFIER,

LTValueLen INT,

LTValueHash VARBINARY(32),

MessageId INT NULL)

CREATE CLUSTERED INDEX #LTHashStrings_CI ON #LTHashStrings(MessageStringId)

CREATE NONCLUSTERED INDEX #LTHashStrings_NCI1 ON #LTHashStrings(LTValueLen,

MessageId, LTValueHash)

-- Create a temporary table for the orphaned PublisherStrings that you find.

Orphaned PublisherStrings

-- are rows in PublisherMessages whose corresponding events have already been

groomed. They still

-- have corresponding rows in LocalizedText. Do not add rows for

PublisherMessages; they are not

-- for duplicated messages.


Spring 2011

CREATE TABLE #OrphanedPublisherStrings (PublisherId UNIQUEIDENTIFIER,

MessageStringId UNIQUEIDENTIFIER)

CREATE CLUSTERED INDEX #OrphanedPublisherStrings_CI ON

#OrphanedPublisherStrings(MessageStringId)

-- Create a temporary table so that you can determine whether a

PublisherMessages row still

-- has a corresponding event. These events do not have an index on the

PublisherId, so do

-- not query the EventAllView. If a PublisherId occurs multiple times in the

event tables,

-- it is only needed one time in the temp table; therefore, the unique

clustered index

-- must contain IGNORE_DUP_KEY. This keeps the temporary table relatively

small and saves

-- time when you want to see the orphaned PublisherMessages.

CREATE TABLE #EventAllPublishers (PublisherId UNIQUEIDENTIFIER)

CREATE UNIQUE CLUSTERED INDEX #EventAllPublishers_CI ON #EventAllPublishers

(PublisherId)

WITH (IGNORE_DUP_KEY = ON)

-- Populate the temporary table by scanning EventAllView one time.

INSERT INTO #EventAllPublishers(PublisherId)

SELECT PublisherId

FROM EventAllView

-- Populate the first temporary table to determine which messages are

duplicated.

INSERT INTO #LTHashStrings (MessageStringId, LTValueLen, LTValueHash,

MessageId)

SELECT LTStringId, len(LTValue), HashBytes('SHA1', LTValue), MessageId

FROM dbo.LocalizedText LT

JOIN #PublisherMessageReverseIndex PM ON PM.MessageStringId = LTStringId

-- Create the second table to determine which messages are duplicated.

CREATE TABLE #LTCountByMessage( LTValueLen INT,

MessageId INT,

LTValueHash VARBINARY(32),

MsgCount INT)

CREATE CLUSTERED INDEX #LTCountByMessage_CI ON #LTCountByMessage(LTValueLen,

MessageId, LTValueHash)

-- Populate second message for duplicate message detection by scanning the

INDEX of

-- the first one and by doing a grouped count.

INSERT INTO #LTCountByMessage (LTValueLen, MessageId, LTValueHash, MsgCount)

SELECT LTValueLen, MessageId, LTValueHash, COUNT(1)

FROM #LTHashStrings

GROUP BY LTValueLen, MessageId, LTValueHash


Spring 2011

-- You are now set up to detect both orphaned PublisherStrings and duplicated

messages

-- by joining to our relatively small (and correctly indexed) temporary

tables.

-- Determine the OrphanedPublisherStrings that have duplicate messages.

INSERT INTO #OrphanedPublisherStrings (PublisherId, MessageStringId)

SELECT PM.PublisherId, PM.MessageStringId

FROM dbo.PublisherMessages PM

JOIN #LTHashStrings LTS ON (LTS.MessageStringId = PM.MessageStringId AND

LTS.MessageId = PM.MessageId)

JOIN #LTCountByMessage LTC ON (LTC.LTValueLen = LTS.LTValueLen AND

LTC.MessageId = LTS.MessageId AND LTC.LTValueHash = LTS.LTValueHash)

WHERE PM.PublisherId NOT IN (SELECT PublisherId FROM #EventAllPublishers) AND

LTC.MsgCount > 1

-- Deleting all the OrphanedPublisherStrings and all the corresponding

LocalizedText rows

-- at one time may be too large for the transaction log to handle. Create a

numbered

-- or ordered table so that you can delete them in relatively small batches

and not

-- overtax the transaction log.

CREATE TABLE #NumberOrphanPublisherStrings(OrphanNum INT IDENTITY,

PublisherId UNIQUEIDENTIFIER,

MessageStringId UNIQUEIDENTIFIER)

CREATE CLUSTERED INDEX #NumberOrphanPublisherStrings_CI on

#NumberOrphanPublisherStrings(OrphanNum)

-- Populate the numbered table.

INSERT INTO #NumberOrphanPublisherStrings (PublisherId, MessageStringId)

SELECT PublisherId, MessageStringId FROM #OrphanedPublisherStrings

END TRY

BEGIN CATCH

GOTO Error

END CATCH

-- Set up variables so that you can delete the orphaned rows.

-- If the transaction log fills up, try to reduce the @OrphanIncrement value,

-- which controls the number of rows that are delete at the same time.

DECLARE @OrphanNum INT

DECLARE @OrphanIncrement INT

DECLARE @OrphanLimit INT

SET @OrphanNum = 0

SET @OrphanIncrement = 10000

SELECT @OrphanLimit = MAX(OrphanNum) FROM #NumberOrphanPublisherStrings

BEGIN TRY

WHILE @OrphanNum < @OrphanLimit

BEGIN

DELETE dbo.LocalizedText FROM

#NumberOrphanPublisherStrings OPS JOIN dbo.LocalizedText LT

ON LT.LTStringId = OPS.MessageStringId


Spring 2011

WHERE OPS.OrphanNum >= @OrphanNum AND OPS.OrphanNum < @OrphanNum +

@OrphanIncrement

DELETE dbo.PublisherMessages FROM

#NumberOrphanPublisherStrings OPS JOIN dbo.PublisherMessages PM

ON PM.PublisherId = OPS.PublisherId

WHERE OPS.OrphanNum >= @OrphanNum AND OPS.OrphanNum < @OrphanNum +

@OrphanIncrement

SET @OrphanNum = @OrphanNum + @OrphanIncrement

END

END TRY

BEGIN CATCH

GOTO Error

END CATCH

Error:

IF @@ERROR <> 0

SELECT

ERROR_NUMBER() AS ErrorNumber,

ERROR_MESSAGE() AS ErrorMessage;

-- Try to drop all the temporary tables

BEGIN TRY

IF EXISTS (SELECT 1 FROM tempdb.INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME

LIKE '#PublisherMessage%')

DROP TABLE #PublisherMessageReverseIndex


LIKE '#OrphanedPublisherStrings%')

DROP TABLE #OrphanedPublisherStrings


LIKE '#LTHashStrings%')

DROP TABLE #LTHashStrings


LIKE '#EventAllPublishers%')

DROP TABLE #EventAllPublishers


LIKE '#LTCountByMessage%')

DROP TABLE #LTCountByMessage


LIKE '#NumberOrphanPublisherStrings%')

DROP TABLE #NumberOrphanPublisherStrings

END TRY

BEGIN CATCH

SELECT

ERROR_NUMBER() AS ErrorNumber,

ERROR_MESSAGE() AS ErrorMessage;

END CATCH


Spring 2011

For more details and updated information see link below http://technet.microsoft.com/en-us/library/hh476936.aspx

http://technet.microsoft.com/en-us/library/hh476936.aspx

SYSTEM CENTER OPERATIONS MANGER 2012 ......NTERNAL O NOT SHARE I DO UMENT,D Spring 2011 SYSTEM CENTER OPERATIONS MANGER 2012 UPGRADE DOCUMENT” FOR SCOM 2007 R2 DISTRIBUTED MANAGEMENT

Documents