scom 2012 r2 update rollup 9 · to start a new instance of microsoft silverlight, clear the browser...

SCOM 2012 R2 UPDATE ROLLUP 9

Installation Guide

Waleed Mostafa [email protected]

http://waleedmostafa.wordpress.com

http://waleedmostafa.wordpress.com/

Waleed Mostafa Blog: http://waleedmostafa.wordpress.com

table of contents

1 Introduction .................................................................................................. 2

2 Issues that are fixed in this update rollup 9 ............................................................ 3

3 How to obtain and install Update Rollup 9 .............................................................. 4

4 Before you start .............................................................................................. 5

5 Installation Steps ............................................................................................ 6

5.1 Update Management servers ....................................................................................................... 6 5.2 Update Gateway servers............................................................................................................ 10 5.3 Update the Web Console ........................................................................................................... 13 5.4 Update Operations console role computers ............................................................................... 15 5.5 Apply the SQL Scripts to SCOM OperationsManager database. ............................................... 17 5.6 Apply the SQL Scripts to SCOM OperationsManagerDW database. ......................................... 19 5.7 Manually import the management packs ................................................................................... 21 5.8 Update Agents ........................................................................................................................... 25

5.8.1 Agents not manually installed ................................................................................... 25 5.8.2 Update Manually installed agents ............................................................................. 27 5.8.3 Update Unix/Linux MPs and Agents .......................................................................... 30



1 Introduction

This Document describes the issues that are fixed in Update Rollup 9 for Microsoft

System Center 2012 R2 Operations Manager. It also includes the step by step

installation for the update rollup 9.



2 Issues that are fixed in this update rollup 9

SharePoint workflows fail with an access violation under APM

Application Pool worker process crashes under APM with heap corruption

Some Application Pool worker processes become unresponsive if many applications are started under APM at the same time

MOMAgent cannot validate RunAs Account if only RODC is available

Missing event monitor does not warn within the specified time range in SCOM 2012 R2 the first time after restart

SCOM cannot verify the User Account / Password expiration date if it is set by using Password Setting object

SLO Detail report displays histogram incorrectly

APM support for IIS 10 and Windows Server 2016

APM Agent Modules workflow fails with Null Reference exception during workflow shutdown

AEM Data fills up SCOM Operational database and is never groomed out

The Downtime report from the Availability report does not handle the Business Hours settings

Adding a decimal sign in an SLT Collection Rule SLO in the ENU Console on a non-ENU OS does not work

SCOM Agent issue while logging Operations Management Suite (OMS) communication failure

Issues that are fixed in the UNIX and Linux management packs

Discovery of Linux computers may fail for some system locales

The UNIX/Linux Agent intermittently closes connections during TLS handshaking

Symptoms include the following:

1. Failed heartbeats for UNIX or Linux computers, especially when the SSLv3

protocol is disabled on the Management Servers.

2. Schannel errors in the System log that contain text that resembles the following:

A fatal error occurred while creating an SSL client credentials. The

internal error state is 10013.

3. WS-Management errors in the event log that contain text that resembles the

following:

WSManFault

Message = The server certificate on the destination computer

(<UNIX/LINUX-COMPUTER-NAME) has the following errors:

Encountered an internal error in the SSL library.

Error number: -2147012721 0x80072F8F

A security error occurred



3 How to obtain and install Update Rollup 9

This update package is available for manual download and installation from the

Microsoft Update Catalog on this link.


http://catalog.update.microsoft.com/v7/site/Search.aspx?q=3129774


4 Before you start

You must run this update rollup as an administrator.

If you do not want to restart the computer after you apply the console update, close the console before you apply the update for the console role.

To start a new instance of Microsoft Silverlight, clear the browser cache in Silverlight, and then restart Silverlight.

Do not install this update rollup package immediately after you install the System Center 2012 R2 server. Otherwise, the Health Service state may not be initialized.

If User Account Control is enabled, run the .msp update files from an elevated command prompt.

You must have System Administrator rights on the database instances for the Operational Database and Data warehouse to apply updates to these databases.



5 Installation Steps

Microsoft recommend install this update rollup package by following these steps in this

particular order:

1. Management servers.

2. Gateway servers.

3. Web console server role computers.

4. Operations console role computers.

5. Apply SQL scripts (see installation information).

6. Manually import the management packs.

7. Apply the agent update to manually installed agents, or push the installation from

the Pending view in the Operations console.

5.1 Update Management servers

If you don’t apply the fix for the data warehouse BULK insert commands time out

issue described in Update Rollup 1, you need to run the following PowerShell

command to create the Key to set the time-out value (in seconds) for the data

warehouse BULK insert commands.

Right click to the PowerShell Icon the run as administrator

Copy and paste the following command:

PowerShell Command

$registryPath = "HKLM:\Software\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse" $Name = "Bulk Insert Command Time Out Seconds" $value = "40" IF(!(Test-Path $registryPath)) { New-Item -Path $registryPath -Force | Out-Null New-ItemProperty -Path $registryPath -Name $name -Value $value ` -PropertyType DWORD -Force | Out-Null} Else{ New-ItemProperty -Path $registryPath -Name $name -Value $value ` -PropertyType DWORD -Force | Out-Null}

Notes:

You need to apply the above steps on each Management server which you want to

override the default BULK insert command time out.



MSP files are included in the update rollup package. Apply all MSP files that relate to a specific

computer.

For example, if the web console and console roles are installed on a management server, apply

the MSP files on the management server. Apply one MSP file on a server for each specific role

that the server holds.

Graphical Interface

1. Login to the first Management Server using local and SCOM admin account.

2. Extract the needed MSP file from the downloaded CAB file.

3. All the needed MSP files extracted from all the CAB Files.

4. Right click on the Start Menu and click to command prompt (admin)



5. On the command Prompt type Cd <the MSP file location>

6. Type KB3129774-AMD64-Server.msp

7. Wait Until the setup Complete.

8. On the reboot popup click no.

9. Open the location “C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server” and insure that there are 2 folders name end with “Update Rollups”



10. Open the location “C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server” make sure that the DLL file version changed to 7.1.1026.1177.

11. Open application log and find event ID 1036 source MsiInstaller to show completion

12. Repeat the Steps from 4 to 11 for all the Management servers that you have

Repeat the Steps from 4 to 11 for all the Management servers that you have



5.2 Update Gateway servers

Graphical Interface

1. Open the GW Server with full admin account to the local server and the SCOM.

2. Open the location of All the needed MSP files extracted from all the CAB Files.



5. Type KB3129774-AMD64-Gateway.msp the press enter.




2. Click finish

3. On the reboot popup click Yes.



4. Wait until the server back online then check for the DLL “NetworkDiscoveryModules.dll” version should be “7.1.1026.1177”

5. Repeat the same step for each gateway you have

Repeat the same step for each gateway you have



5.3 Update the Web Console

Graphical Interface

6. Login to the web console server open file location “C:\windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG” and find web.config file

7. Open the file and find <system.web> tag add the following line “<machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>” save the file

8. Right click to start then click on Run type “iisreset” and press enter

9. Test the SCOM web console before you start.






13. Type KB3129774-AMD64-ENU-WebConsole.msp




7. Open the location “C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\ WebConsole” make sure that the DLL file version changed to “7.1.1026.1177”

8. Reboot the server Reboot the server and test the SCOM web console

5.4 Update Operations console role computers

Graphical Interface

1. Open the Operations Console Computer with full admin account to the local server and the SCOM.





4. On the command Prompt type Cd <the MSP file location> type KB3129774-AMD64-ENU-Console.msp the press enter.


6. Open file location “C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Console” make sure that the DLL file version changed to “7.1.1026.1177”

7. Repeat the steps for each SCOM console computer role.

Repeat the steps for each SCOM console computer role.



5.5 Apply the SQL Scripts to SCOM OperationsManager database.

Graphical Interface

1. Open

“%SystemDrive%\Pr

ogram

Files\Microsoft

System Center 2012

R2\Operations

Manager\Server\SQ

L Script for Update

Rollups” open the

SQL script with

notepad the copy the

content.

2. Open SQL Server 2014 Management Studio

3. Right click to the

OperationsManager

database select new

query then past the

file

“update_rollup_mom

_db.sql” content to

the query window.

4. Click execute.



5. Wait until the query finished and you should have result as the print screen.



5.6 Apply the SQL Scripts to SCOM OperationsManagerDW database.

Graphical Interface

1. Open

“%SystemDrive%\Pr

ogram

Files\Microsoft

System Center 2012

R2\Operations

Manager\Server\SQ

L Script for Update

Rollups” open the

SQL script with

notepad the copy the

content.

2. Open SQL Server 2014 Management Studio

3. Right click to the

OperationsManager

database select new

query then past the

file

“UR_Datawarehouse

.sql” content to the

query window.

4. Click execute.



5. Wait until the query finished and you should have result as the print screen.



5.7 Manually import the management packs

Before you start you need to read the following Notes:

1. The Advisor MP’s are only needed if you are using Microsoft Operations

Management Suite cloud service, (Previously known as Advisor, and Operation

Insights).

2. The APM MP’s are only needed if you are using the APM feature in SCOM.

3. Note the APM MP with a red X. This MP requires the IIS MP’s for Windows

Server 2016. Only import this if you are using APM *and* you need to monitor

Windows Server 2016.

4. The TFS MP bundle is only used for specific scenarios, such as DevOps

scenarios where you have integrated APM with TFS, etc. If you are not currently

using these MP’s, there is no need to import or update them

5. The Visualization libraries deal with Dashboard updates, and these always need

to be updated.

Graphical Interface

1. Login to the Management Server using local and SCOM admin account.

2. Open the SCOM console. 3. Got to Administration tape

and select Management packs.



4. Right click select import management pack.

5. Click Add then add from disk

6. Click No.



7. Browse to location “C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups” and select all then click open.

8. Remove all the other languages that is not needed.

9. Remove all the management packs that is not dependency implemented.



10. Click yes.

11. Wait until the management pack implementation finished.

12. Click close.



5.8 Update Agents

There are 2 types of agents needed to be updated

5.8.1 Agents not manually installed

Agents should be placed into pending actions by this update for any agent that was not

manually installed.

Graphical Interface

1. Login to the Management Server using local and SCOM admin account.

2. Open the SCOM console.

3. Got to Administration tape and select pending management.

4. Select the server and right click select approve.

5. Enter the information needed to install the update.



6. Wait until the agent updates finished.

7. The result should be like the print screen, click close.



5.8.2 Update Manually installed agents

Graphical Interface

1. Open the Operations Console Computer with full admin account to the local server and the SCOM.



4. On the command Prompt type Cd <the MSP file location> type KB3129774-AMD64-Agent.msp the press enter.



5. Wait until the setup finished …..

6. Insure that the setup completed successfully then click finish.

7. Click No if you don’t want to reboot the servers Or yes if you can reboot it



8. In case of no at the same cmd window type “net stop HealthService” then type “net start HealthService”

9. On the SCOM console -- > Operations Manager MP view --- > Agent Details --- > Agents by Version ---- >make sure that you see UR9 on the patch list.

10. Repeat the steps from step 1 to 9 for all the Manually installed agents

Repeat the steps from step 1 to 9 for all the Manually installed agents



5.8.3 Update Unix/Linux MPs and Agents

The current Linux MP’s link here.

Graphical Interface

1. Take care when downloading – that you select the correct download for SCOM 2012 R2.

2. Download the MSI and run it. It will extract the MP’s to C:\Program Files (x86)\System Center Management Packs\System Center 2012 R2 Management Packs for Unix and Linux\

3. Update the MP that you are using by importing the Mp’s from the location above.

4. Now you can you would upgrade your agents on the Unix/Linux monitored agents


https://www.microsoft.com/en-us/download/details.aspx?id=29696


5. You can input implementation user account or use existing RunAs accounts.

6. Insure that the upgrade completed successfully.


scom 2012 r2 update rollup 9 · to start a new instance of microsoft silverlight, clear the browser...

Documents