You are browsing the archive for Operations Manager.

System Center Global Service Monitor: Installation Step-by-step

3:57 pm in Operations Manager by Christopher Keyaert

Hi Everyone,

As I’m currently rebuilding my lab with the R2 preview releases of System Center and Windows Server, I decided to write something about System Center Global Service Monitor.

What is System Center Global Service Monitor?

Global Service Monitor reports on availability, performance, and function of web applications by scheduling and executing synthetic transactions against the application from Windows Azure.
In other words, GSM (Global Server Monitor) will use Microsoft servers hosted in Azure to test the availability of your website from different part of the world. The best part is that GSM is fully integrated with System Center Operations Manager.

How to get GSM?

GSM is free only if you have subscribed to the Microsoft Software Assurance.
Now if you don’t have a SA, you could still test GSM with the 90 days Trial. For that, go on the official website of Global Service Monitor

http://www.microsoft.com/en-us/server-cloud/system-center/global-service-monitor.aspx

On the right, you could see Sign Up for Free Trial

Once your trail activated, you need to download the Management packs :
http://www.microsoft.com/en-us/download/details.aspx?id=36422

How to install GSM on Operations Manager?

The GSM management packs have three prerequisites:

  • The installation of the Alert Attachment Management Pack
  • The installation of the Windows Identity Foundation feature
  • The Management Servers need to have internet access

Alert Attachment Management Pack

You first need to install the Alert Attachment Management pack (Microsoft.SystemCenter.AlertAttachment.mpb)
Microsoft published a great post, with some print screens, about the installation of this MP. I invite you to read it carefully :
http://technet.microsoft.com/en-us/library/jj899889.aspx

Windows Identity Foundation feature

On the management server that you will use to configure GSM, install the Windows Identity Foundation Features from Server Manager.
Nothing special, just a next next setup.

Management Servers need internet access

As GSM is using Windows Azure, we need to provide a management pool where the management servers have access to internet.
If all your management servers have already internet access, you could you the All Management Servers Resource Pool.

Now if you are in a more secure environment where your MS don’t have internet access, you need to create a new management pool dedicated to GSM and build one or two new MS and add them to that pool.
Of course, these new MS will need to have access to internet.

GSM Management packs installation

Once the prerequisites are ok, you need to import the Global Server Monitor management packs.

In the Administration Pane, you have now access to the Global Service Monitor menu. (Personally, I had to restart my Operations Console to get it working correctly).

There, follow the wizard to connect your Operations Management environment with your GSM subscription.
Now that everything is ready to start the monitor of your website, click on Configure Web Application Availability Tests.

Click on Next.

Name the application/website that you want to monitor, select a management pack to store it and click on Next.

Specify your application website(s), and click on Next.

By clicking on the first Add button, you could choose from which external location (country/region) you want to monitor your website(s).
You could also monitor your website(s) from server(s) that are part of you SCOM infrastructure.

You could test if everything is well configured directly from the Wizard. You also have the possibility to change the configuration, customizing some threshold values by clicking on Change Configuration.
When done, click on Next.

Review the information, and finally, click on create.

 

Now, there is two different parts in the SCOM console where you could see information about GSM.
The first one is under Monitoring > Operations Manager > Global Service Monitor. This view give you the connection state between your SCOM infrastructure and the GSM service hosted at Microsoft.

The second part is under Monitoring > Application Monitoring > Web Application Availability Monitoring.
The state view shows the availability of your website from all the locations your configured.

From the action pane on the right, you have two more views available.

The Detailed Dashboard – List, give you detailed performance information.

The second one is a map with Status and Transaction Response time of your website from each locations.

I hope this help!

Christopher

How to access to SCOM 2012 SP1 Web Console from Windows Server 2003 SP2 / Windows Xp / …

2:18 pm in Operations Manager by Christopher Keyaert

Hello All,

I had a customer that is running SCOM 2012 SP1 as monitoring platform, but he is using a Windows Server 2003 SP2 Citrix image as terminal server, and he wants to be able to access to the SCOM Web Console from that terminal server.

The first time that you access to the SCOM Web Console, you have to configure the Silverlight installation.

But, when you tried that to configure it on a Windows XP SP3, Windows Server 2003 OS, it crashes with the following error:

The procedure entry point LocaleNameToLCID could not be located in the dynamic link library Kernel32.dll

The problem is explained on Mihai’s blog, but the proposed fix only works for SCOM 2012 and it doesn’t work anymore for SCOM 2012 SP1.
http://blogs.technet.com/b/mihai/archive/2012/05/08/making-the-om-2012-web-console-accessible-from-a-windows-xp-client.aspx

Now, how to get this working with SCOM 2012 SP1?

  1. Download the .reg file on Mihai’s blog
  2. Double click on it and accept the registry modification

  3. Start a MMC console and Add the certificates snap-in for the Local Computer store
  4. Expand Local Computer
    Certificates Store > Trusted Publishers > Certificates
  5. Remove all the Microsoft Corporation Microsoft Code Signing PCA certificates (the .reg file installed 3 certificates which are for SCOM 2012, in fact the one for SCOM 2012 SP1 is missing).
  6. Download the attached certificate http://scug.be/christopher/files/2013/03/SCOM.zip

  7. Import it to Local Computer
    Certificates Store > Trusted Publishers > Certificates

  8. Restart internet explorer and go to the SCOM Console Website
  9. Enjoy J

Tim has a really good solution to automate that task by GPO, just use the certificate that I provided in step 6.
http://www.scom2k7.com/scom-2012-web-console-configuration-no-longer-required/

Cheers
Christopher

SCOM 2012 SP1 : OMServer.msi returned error 1603

3:53 pm in Operations Manager by Christopher Keyaert

Hi all,

On Tuesday, I was at a customer location to install a new SCOM 2012 SP1 environment. I checked the requirement for SCOM 2012 SP1 on TechNet :
http://technet.microsoft.com/en-us/library/jj656654.aspx#BKMK_RBF_ManagementServer 

SCOM 2012 SP1 Management Server :

  • Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
  • Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012, or Windows Server 2012 Core Installation.
  • Processor Architecture: must be x64
  • Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell version 3.0.
  • Windows Remote Management: Windows Remote Management must be enabled for the management server.
  • .NET Framework 4 is required.

The prerequisites check passed without any problem
image

But the installation failed
image

With the following error :

11:11:16]: Always: :LaunchMsi: Launching C:\Infront\SCOM2012SP1RTM\Setup\AMD64\Server\OMServer.msi
[11:14:16]: Always: :MsiInstallProduct finished for msi C:\Infront\SCOM2012SP1RTM\Setup\AMD64\Server\OMServer.msi.
[11:14:16]: Always: :LaunchMSI: Setting rollback to true
[11:14:16]: Error: :
LaunchMSI: MSI C:\Infront\SCOM2012SP1RTM\Setup\AMD64\Server\OMServer.msi returned error 1603
[11:14:16]: Error: :ProcessInstalls: Install Item Management Server failed to install. We did not launch the post process delegate.
[11:14:16]: Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Management Server
[11:14:16]: Info: :SetProgressScreen: FinishMinorStep.

I checked on Internet and found these 2 posts related to that error :
http://www.scom2k7.com/error-installing-scom-2012-omserver-msi-returned-error-1603/
http://thoughtsonopsmgr.blogspot.be/2013/01/om12-sp1-upgrade-beware-for-corrupt-iso.html

Everything was fine with the registry, I re-downloaded the source files from TechNet and also MSDN, started the installation again and it always failed with the same error message.

I decided to go back to TechNet and I checked the requirement for SCOM 2012 (Without SP1) : http://technet.microsoft.com/en-us/library/jj656649.aspx#BKMK_RBF_ManagementServer

SCOM 2012 Management Server :

  • Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
  • Server Operating System: must be Windows Server 2008 R2 SP1.
  • Processor Architecture: must be x64.
  • Windows PowerShell version: Windows PowerShell version 2.0.
  • Windows Remote Management: Windows Remote Management must be enabled for the management server.
  • Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required for the management server.
  • Both .NET Framework 3.5 Service Pack 1 (SP1) and .NET Framework 4 are required. For more information, see the following documents:
    .NET Framework 3.5 SP1 redistributable package
    .NET Framework 4 redistributable package

OH OH OH .NET Framework 3.5 SP1 is required for SCOM 2012 and not for SCOM 2012 SP1 ????? Are you really sure of that ??? Let’s try to install it on the server. After a few clicks, it’s installed.
Capture

Let’s give a another try….. and….
image

BINGO, it was simply that !!! I had to install the .NET Framework 3.5 SP1. I already sent a mail to Microsoft and they will update the document on TechNet as soon as possible.

Cheers
Christopher

Upgrade to SCOM 2012 failed – SQL MPs involved

3:19 pm in Operations Manager by Christopher Keyaert

Hey,

I recently tried to upgrade a customer pre-production environment from SCOM 2007 R2 to SCOM 2012. As usual, I followed my upgrade guide: http://scug.be/christopher/2012/10/23/upgrade-guide-from-scom-2007-to-scom-2012/

But this time, when I started the RMS upgrade part, it failed with the following errors:

The errors

Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Column names in each table must be unique. Column name ‘Post_InstallPath_1ACC50C3_CE60_075D_18CF_BC3CAC665124′ in table ‘MT_AnalysisServices_Log’ is specified more than once.

Cannot find the object “dbo.MT_AnalysisServices_Log” because it does not exist or you do not have permissions.

Column names in each table must be unique. Column name ‘Post_InstallPath_1ACC50C3_CE60_075D_18CF_BC3CAC665124′ in table ‘MT_AnalysisServices_0_Log’ is specified more than once.

Cannot find the object “dbo.MT_AnalysisServices_0_Log” because it does not exist or you do not have permissions.

Column names in each table must be unique. Column name ‘Post_ServiceName_3F85503C_3D5E_19D8_0466_95AA9BB8AC05′ in table ‘MT_ReportingServices_0_Log’ is specified more than once.

Cannot find the object “dbo.MT_ReportingServices_0_Log” because it does not exist or you do not have permissions.

Column names in each table must be unique. Column name ‘Post_ServiceName_3F85503C_3D5E_19D8_0466_95AA9BB8AC05′ in table ‘MT_ReportingServices_Log’ is specified more than once.

Cannot find the object “dbo.MT_ReportingServices_Log” because it does not exist or you do not have permissions.

This upgrade failure completely crashed the environment as it let the SCOM2007 environment without any RMS. /!\ There is no automatic rollback process in case of RMS upgrade failure. /!\ The only choice that I had was to restore the complete environment from the snapshot that I took just before the upgrade proces.

It’s really mandatory for fixing this issue to have a SCOM environment up and running. When done, let’s try to understand what’s happened and find a way to fix it.

The debug

As we could see in the error logs above, there is a problem with the following 2 tables:

  • dbo.MT_AnalysisServices_log
  • dbo.MT_ReportingServices_log

These two tables has been created in the OperationsManager DB by the import of the SQL Management packs. I will not focus on the _log tables, but directly on the “main tables”, dbo.MT_AnalysisServices and dbo.MT_ReportingServices.

dbo.MT_AnalysisServices

Connect to the SQL server and run the following query:

select * FROM dbo.ManagedTypeProperty where managedtypeid = ‘1ACC50C3-CE60-075D-18CF-BC3CAC665124′

The query above will retrieve the properties available for the type AnalysisServices from the ManagedTypeProperty table. Below, the output of the column “ColumnName”:

Edition_1ACC50C3_CE60_075D_18CF_BC3CAC665124

InstallPath_1ACC50C3_CE60_075D_18CF_BC3CAC665124

PerformanceCounterObject_1ACC50C3_CE60_075D_18CF_BC3CAC665124

ServiceName_1ACC50C3_CE60_075D_18CF_BC3CAC665124

ServicePackVersion_1ACC50C3_CE60_075D_18CF_BC3CAC665124

Version_1ACC50C3_CE60_075D_18CF_BC3CAC665124

 

The second SQL query will retrieve the properties (Column name) that are available in the table MT_AnalysisServices:

SELECT COLUMN_NAME, COLLATION_NAME FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_NAME = ‘MT_AnalysisServices’ AND ORDINAL_POSITION > 1 ORDER BY ORDINAL_POSITION ASC

Query result:

Edition_1ACC50C3_CE60_075D_18CF_BC3CAC665124

ServiceName_1ACC50C3_CE60_075D_18CF_BC3CAC665124

ServicePackVersion_1ACC50C3_CE60_075D_18CF_BC3CAC665124

InstanceName_97408C11_D1C8_5BCE_EF78_74F0473964F3

Version_1ACC50C3_CE60_075D_18CF_BC3CAC665124

DisplayName_55270A70_AC47_C853_C617_236B0CFF9B4C

InstallPath_1ACC50C3_CE60_075D_18CF_BC3CAC665124

PerformanceCounterObject_1ACC50C3_CE60_075D_18CF_BC3CAC665124

ServiceClusterName_1ACC50C3_CE60_075D_18CF_BC3CAC665124


As you could see, there is some inconsistences between the properties available in the two tables. The properties DisplayName, InstanceName and ServiceClusterName are not available in the ManagedTypeProperty table for the type AnalysisServices.

For the two firsts values, DisplayName and InstanceName, the Microsoft Premier Support told me that was normal. I double checked in another environment and that seems to be true.

Now for the ServiceClusterName properties, there is a real problem, this properties must be available in both tables, so we already find a first problem here.

dbo.MT_ReportingServices

As, we already have one properties missing for the type AnalysisServices, we will now check if we have the same problem for the type ReportingServices.

Connect to the OperationsManager DB and run the following query:

select * FROM dbo.ManagedTypeProperty where managedtypeid = ‘3F85503C-3D5E-19D8-0466-95AA9BB8AC05′

The result of the query:

Edition_3F85503C_3D5E_19D8_0466_95AA9BB8AC05

InstallPath_3F85503C_3D5E_19D8_0466_95AA9BB8AC05

ServiceName_3F85503C_3D5E_19D8_0466_95AA9BB8AC05

ServicePackVersion_3F85503C_3D5E_19D8_0466_95AA9BB8AC05

Version_3F85503C_3D5E_19D8_0466_95AA9BB8AC05

 

The second SQL query will retrieve the properties (Column name) that are available in the table MT_ReportingServices:

SELECT COLUMN_NAME, COLLATION_NAME FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_NAME = ‘MT_ReportingServices’ AND ORDINAL_POSITION > 1 ORDER BY ORDINAL_POSITION ASC

The result:

Edition_3F85503C_3D5E_19D8_0466_95AA9BB8AC05

ServicePackVersion_3F85503C_3D5E_19D8_0466_95AA9BB8AC05

InstanceName_97408C11_D1C8_5BCE_EF78_74F0473964F3

DisplayName_55270A70_AC47_C853_C617_236B0CFF9B4C

InstallPath_3F85503C_3D5E_19D8_0466_95AA9BB8AC05

Version_3F85503C_3D5E_19D8_0466_95AA9BB8AC05

ServiceName_3F85503C_3D5E_19D8_0466_95AA9BB8AC05

ServiceClusterName_3F85503C_3D5E_19D8_0466_95AA9BB8AC05

 

We have exactly the same problem here, the property ServiceClusterName is also missing from the table ManagedTypeProperty for the type ReportingServices.

The fix

The ServiceClusterName property is missing from the ManagedTypeProperty for the types ReportingServices and AnalysisServices. We also know that these properties are link to the SQL Management Packs.

I had several calls with the Microsoft Premier Support and finally, they proposed me to Remove and Re-add the SQL management packs by following the steps below:

  1. Ensure to have all the binaries for the SQL MPs that you are currently running.
  2. Export your custom management packs where you stored SQL overrides
  3. Delete the all the SQL management packs
  4. Wait 30 minutes
  5. Import all the SQL MPs
  6. Import the custom SQL MPs

Now, we have to check if this export/re-import process of the SQL MPs fixed the problem or not. For that we have to run the following two queries:

select * FROM dbo.ManagedTypeProperty where managedtypeid = ‘1ACC50C3-CE60-075D-18CF-BC3CAC665124′
select * FROM dbo.ManagedTypeProperty where managedtypeid = ‘3F85503C-3D5E-19D8-0466-95AA9BB8AC05′

The both queries are now returning the ServiceClusterName_3F85503C_3D5E_19D8_0466_95AA9BB8AC05 properties for the type AnalysisServices and ReportingServices. Which is what we’re expecting J

As the export/re-import of the SQL Management packs seems to fix the problem, I started the RMS upgrade to SCOM2012. Hopefully for me, this time, it ran successfully without any problem. So yes, the first time, the SQL Management Packs crashed my upgrade process. FYI, the environment was running the following versions of the SQL MPs:

The conclusion part

I must admit that I still don’t know why the ServiceClusterName_3F85503C_3D5E_19D8_0466_ properties was missing from the ManagedTypeProperty table for the MT_Analysis and MT_ReportingServices tables.

I don’t believe to a DB corruption, as I noticed the same problem, in 2 different environments which were running exactly the same MPs.

Now, what is sure, the export/re-import fixed the problem and allow me to upgrade the environment to SCOM 2012 without any problem. My advice is now to run the following 2 queries:

select * FROM dbo.ManagedTypeProperty where managedtypeid = ‘1ACC50C3-CE60-075D-18CF-BC3CAC665124′
select * FROM dbo.ManagedTypeProperty where managedtypeid = ‘3F85503C-3D5E-19D8-0466-95AA9BB8AC05′

To ensure that the ServiceClusterName property is available for AnalysisServices and ReportingServices before starting an upgrade from SCOM2007R2 to SCOM2012.

Finally, I would like to thanks the Microsoft Premier Support.

Christopher

 

Upgrade guide from SCOM 2007 to SCOM 2012

11:41 am in Operations Manager by Christopher Keyaert

Hi Guys,

I would like to share with you my notes concerning the upgrade from Operations Manager 2007 to Operations Manager 2012. The guide below groups information from TechNet (for which I’m not the author! all credits go to Microsoft), my personal notes and screenshots from the field.

The pre-requisites for this guide is to have a Operations Manager 2012 compliant environment (OS version /SQL version / hardware).

SCOM 2012 – Upgrade Plan

More Information: http://technet.microsoft.com/en-us/library/hh476934.aspx

Distributed Upgrade (Simple)

Use this path when you have an Operations Manager 2007 R2 management group where various features are installed on separate servers, all of which meet the minimum supported configurations for System Center 2012 – Operations Manager.

Upgrade Process Flow Diagram

Checklist

Use the following checklist to upgrade your distributed management group if it already meets the supported configuration requirements for System Center 2012 – Operations Manager.

 More Information: http://technet.microsoft.com/en-us/library/hh241301.aspx

 

Task

Import the Upgrade Helper management pack.

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

Back up the encryption key.

Review the Operations Manager 2007 R2 event logs.

Remove agents from pending management.

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

Upgrade the manually installed agents.

Upgrade the secondary management servers.

Upgrade gateways, if present.

Upgrade the push-installed agents.

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

Disable all notification subscriptions.

Stop services or disable any connectors that are installed.

Verify that your operational database has enough free space.

Back up the databases.

Restore the encryption key on secondary management server.

Run management group upgrade on the root management server.

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

Re-enable notification subscriptions.

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

Update overrides.

Verify the success of the upgrade.

Import the Upgrade Helper management pack.

The Upgrade Helper management pack guides you through the upgrade process from System Center Operations Manager 2007 R2 to System Center 2012. The Upgrade Helper management pack discovers the root management server, secondary management servers, gateway servers, and any agent-managed computers in your distributed Operations Manager 2007 R2 management group. The Upgrade Helper management pack monitors the progress of each phase of your upgrade.

Filename: OPERATIONSMANAGER.UPGRADE.MP

Back up the encryption key.

To start the Encryption Key Backup or Restore Wizard to back up the root management server encryption key

  1. Log on to the computer hosting the root management server with an account that is a member of the Administrators group.
  2. Open a command prompt window using the Run as Administrator option.
  3. At the command prompt, type

    cd <Operations Manager Installation Folder>

  4. Type SecureStorageBackup and then press ENTER.
  5. In the Encryption Key Backup or Restore Wizard, on the Backup or Restore? Page, select the Backup the Encryption Key option, and then complete the wizard.

More Information: http://technet.microsoft.com/en-us/library/cc540390.aspx

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

To determine the SQL Server collation of a database, you can check the database properties. In SQL Server Management Studio, right-click the database you want to check, and then click Properties. The collation is listed under Maintenance.

More Information: http://support.microsoft.com/kb/958979

ALWAYS INSTALL THE SCOM 2012 ENVIRONMENT ON SQL WITH THE SQL_Latin1_General_CP1_CI_AS collation!

Pre-requisites

  • Read Mihai Sarbulescu’s post : Know issues when upgrading from OM 2007 R2 to OM 2012 
  • RMS, MS, Gw must run Windows Server 2008 R2 Sp1 or another supported version
  • All the DBs (OperationsManager, Datawarehouse, Reporting) must be hosted on a SQL Server 2008 R2 or another supported version.
  • .Net 4 must be installed on the RMS, MS and GW.
  • Report Viewer 2010 must be installed on the RMS, MS, GW.

Upgrade the secondary management servers.

Upgrade of the Management Server

Start the SCOM 2012 upgrade process by upgrading all the management servers (/!\Not the RMS, only the MS). Let the agents connected to your MS during the upgrade process, otherwise, you will not be able to upgrade these agents via the SCOM Console after the MS upgrade and you will have to manually deploy the SCOM 2012 Agent to all the existing agents.

  1. 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.
  2. From the System Center 2012 – Operations Manager media, run Setup.exe, and then click Install. The Getting Started page displays information about which features will be upgraded.

Note

If a web console exists on the secondary management server, it will be removed instead of upgraded. You have to re-install the web console after you upgrade the management group. For more information, see How to Install the Operations Manager Web Console. To minimize downtime, you can install the Operations Manager 2007 R2 web console on a stand-alone server.

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, and have run upgrade on the management group itself. The next step is to upgrade any gateways.

More information: http://technet.microsoft.com/en-us/library/hh241296.aspx

  1. On the Getting Started, System Center 2012 – Operations Manager Upgrade page, click Next to proceed with the upgrade.

  1. On the Getting Started, Select installation location page, accept the default value of C:\Program Files\System Center 2012\Operations Manager, or type in a new location, or browse to one. Then click Next.

  1. On the Prerequisites page, review and address any warnings or errors that the Prerequisites checker returns, and then click Verify Prerequisites Again to recheck the system.

  1. If the Prerequisites checker does not return any warnings or errors, the Prerequisites, Proceed with Setup page appears. Click Next.

  1. On the Configuration, Configure Operations Manager accounts page, we recommend that you use the Domain Account option for the System Center Configuration service and System Center Data Access service accounts.

    Enter the credentials for a domain account, and then click Next.

  1. Review the options on the Configuration, Ready To Upgrade page, and then click Upgrade. The upgrade proceeds and displays the upgrade progress.

  1. When the upgrade is finished, the Upgrade complete page appears. Click Close. Be patient, the process is quite long.

Upgrade the push-installed agents.

Go to Administration > Pending Management and upgrade all the agents that need to be upgraded.

Upgrade the manual-installed agents

If you have manual-installed agents, (agents in DMZ, other domain …) you have to upgrade these agents manually.

Upgrade the other Management servers

You have to repeat these 3 following actions until you upgraded all you management servers and agents:

  • Upgrade the management server SCOM 2012
  • Upgrade the push-installed agent
  • Upgrade the manual-install agent

Upgrade the Gateway servers

Follow the same process than the management servers for the Gateway servers:

  • Upgrade the gateway server
  • Upgrade the push-installed agent
  • Upgrade the manual-install agent

Repeat these 3 steps for all the gateway servers.

Verify that your operational database has enough free space.

You must verify that the operational database has more than 50 percent of free space before you upgrade the management group because the upgrade might fail if there is not enough space. You should also ensure that the transactions logs are 50 percent of the total size of the operational database.

To check how much free space the Operational Database has

  1. On the computer that hosts the operational database, open SQL Server Management Studio.
  2. In the Object Explorer, expand Databases.
  3. Right-click the operational database, point to Reports, Standard Reports, and then click Disk Usage.
  4. View the Disk Usage report to determine the percentage of free space.


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

  1. On the computer that hosts the operational 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 operational 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 the operational database, and then click Properties.
  6. In the Database Properties 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 percent.

Note   

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

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

Verify the SQL Server Collation

SQL Server collation for all databases and database instances must be one of the following:

Language

Collation

English

SQL_Latin1_General_CP1_CI_AS

Run management group upgrade on the root management server.

To set the product key, use the Set-SCOMLicense cmdlet in PowerShell. To use the Set-SCOMLicense cmdlet you need to use elevated permissions. (Run as Administrator).

1. Open PowerShell as an Administrator
2. Load the OperationsManager Module (import-module operationsmanager)
3. Connect to your ManagementGroup (New-SCOMManagementGroupConnection)
4. Use Set-SCOMLicense -ProductId "yourlicensekey"
5. To check if changes were executed run Get-SCOMManagementGroup | ft skuforlicense, version, timeofexpiration –a

Note: This may require a reboot after running in order to register correctly.
More information: http://support.microsoft.com/kb/2699998

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

ACS upgrade

/!\ You must be logged on and run the install process with the service account that you are using to connect to the ACS DB /!\

/!\ You must be run the install process with the service account /!\

How to Upgrade Reporting from Operations Manager 2007 R2

  1. Log on to the computer that hosts the Reporting server with an account that is a member of the Operations Manager 2007 R2 Administrators role for your Operations Manager 2007 R2 management group.
  2. On the System Center 2012 – Operations Manager source media, run Setup.exe, and then click Install.

  1. On the Getting Started, System Center 2012 – Operations Manager Upgrade page, review the features that will be upgraded. In this case, it is Operations Manager 2007 R2 Reporting. Click Next.

  1. On the Select installation location page, accept the default value of C:\Program Files\System Center 2012\Operations Manager, or type in a new location or browse to one. Then click Next.

  1. On the Prerequisites page, review and address any warnings or errors that the Prerequisites checker returns, and then click Verify Prerequisites Again to recheck the system.
  2. If the Prerequisites checker does not return any warnings or errors, the Prerequisites, Proceed with Setup page appears. Click Next.

  1. On the Ready to Upgrade page, review the options, and then click Upgrade.

  1. When upgrade is finished, the Upgrade complete page appears. Click Close.

Run SQL Query on each Management Group

Run the following SQL query on the Operational database in each management group to clean up the Localizedtext table and the Publishmessage table.

Assign UNIX/Linux Agents to a Resource Pool

After completing the upgrade, UNIX/Linux agents must be assigned to a resource pool to enable highly-available monitoring and agent administration. For more information on creating resource pools, see How to Create a Resource Pool.

  1. Open the Operations console by using an account that is a member of the Operations Manager Administrators role for the om12short management group.

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

  3. In the Administration pane, under Device Management, click UNIX/Linux Computers.

  4. Select the UNIX/Linux computers to assign to a resource pool, and in the Actions pane, click Change Resource Pool.

  5. Complete the Change Resource Pool wizard to assign the computers to the selected resource pool.

UR3 installation

The update rollup 3 is available for Operations Manager 2012: http://support.microsoft.com/kb/2756127

We recommend that you install the update rollup package in the following order.

  • Install the update rollup package on the following server infrastructure:

  • Management server or servers

  • Gateway servers

  • Reporting servers

  • Web console server role computers

  • Operations console role computers

  • Manually import the management packs. (C:\Program Files\System Center 2012\Operations Manager\Server\Management Packs for Update Rollups)

  • Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.

For an SCOM 2012 Installation in English, please refer to the filename and GUID available in the table below:

TComponent

Architecture

Language

Appended GUID

Console 

amd 64

English 

755b85ba494fa5c83ca31cf40d38be5d6d0551ef

Consol

x86        

English 

74b1593272d3c45ca7a98b2a3e0d8dc2c3f795d6

Reporting

amd 64

English 

8043cc39d79514d1e633b645063100c136cf1f92

Web Console

amd 64

English 

2ef77d6ea1080b83c10351001dc13bf7e6977b7a



To manually install the update rollup packages, run the following command from an elevated command prompt:

msiexec.exe /update <PackageName>

For example, to install Update Rollup 3 for System Center Operations Manager 2012 (KB2750631), run the following command:

msiexec.exe /update KB2750631-AMD64-Server.msp

Conclusion

And voilà J your environment is upgrade to SCOM 2012.

System Center 2012 Update Rollup 3 : Which files must I install ?

9:38 am in Operations Manager by Christopher Keyaert

Hi Guys,

As you probably noticed, Microsoft released some days ago, the System Center 2012 Update Rollup 3. This UR3 contains fixes for :

  • Data Protection Manager 2012
  • Operations Manager 2012
  • Service Manager 2012.

All the information are available : http://support.microsoft.com/kb/2756127

To install this UR3 to your existing System Center 2012 environment, you basically have 2 choices :

  • Windows update
  • Manual Download and Manual installation.

If you choose the second approach, for example Operations Manager, you will have the following files :

OM Reporting
clip_image002

OM WebConsole
clip_image004

OM Console
clip_image006

Which files do I have to install in my environment ? What are the differences between these files ?
In fact, each of these files are for each different languages/locales installation. if your Operations Manager 2012 environment is in English, you have to choose the following files :

Component Architecture Language Appended GUID
Console amd 64 English 755b85ba494fa5c83ca31cf40d38be5d6d0551ef
Console x86 English 74b1593272d3c45ca7a98b2a3e0d8dc2c3f795d6
Reporting amd 64 English 8043cc39d79514d1e633b645063100c136cf1f92
Web Console amd 64 English 2ef77d6ea1080b83c10351001dc13bf7e6977b7a

For the other products and languages, you could wait for Microsoft to update the KB, which must happen really soon (http://support.microsoft.com/kb/2756127) or you could use Microsoft Update which will download automatically the right files.

I would like to thank you Laura Cruz from Microsoft to clarify the situation.

Cheers
Christopher

SCOM 2007 R2 : Configuration not loaded…again

12:56 pm in Operations Manager by Christopher Keyaert

Hi Guys,

If you follow my blog, we probably already read my previous post about : SCOM 2007 R2 : Configuration not loaded
Two days after this issue was resolved, my customer had again the exact same symptoms… First thing that I did, is to check the BaseManagedEntity table and  this time no inconsistency was found, everything seems to be ok.

After some search, I found that KB : Configuration may not update in System Center Operations Manager http://support.microsoft.com/kb/2635742/EN-US

The System Center Management Configuration service uses a timestamp to determine when new configuration data needs to be calculated for agents and management servers.  If the system clock on an agent is faster than the system clock on the Management Server, discovery data from this agent will set the timestamp for one or more managed instances hosted by that agent to the current agent system clock time.  The System Center Configuration Management service will delay calculating configuration updates for the instances on that agent until the system clock on the Management Server is current with the timestamp for that discovery data.  If the agent system clock was significantly faster than Management Server system time when discovery data was sent, or the agent continues to send data with a future timestamp, then it is possible that the management group would experience the symptoms listed above.

Setting the agent system clock time to match the Management Server system clock time will not reset the timestamp for the existing discovery data and the issue will remain until the Management Server system clock time exceeds the discovery data by the grooming interval, when the obsolete discovery data will be groomed normally.

Let check if we are in that case or not. The first thing to do is to run the following 3 queries :

Capture3

As we could see, there is a difference of 3 hours 30 min between the current time and some data inserted in the DB. “We’ve got data from the future” Open-mouthed smile. We have now to identify which computer is causing that problem in our environment.

For that, we have to run 3 new queries : (I modified the queries to return the computer that has inserted data with more than 1 hour in advance.)

Capture4

This second query didn’t return any on environment. we will now run the last query :

Capture5

It returned the exact same server that we had with the first query. Let’s have a quick look on that server. On the left the impacted server, on the right the Domain Controller located on the same site.

Capture

As you could see the time on the server is not correct. We have now to correct the time on the server, and also the existing data in the DB. For the time on the server, just modify it from the user interface, for the data in the data, we will have to run the following commands against the affected tables.

All data are now at the right time, a restart of the 3 SCOM services on the RMS should fix the problem.

Cheers

Christopher

SCOM 2007 R2 : Configuration not loaded

7:45 am in Operations Manager by Christopher Keyaert

Hi Guys,

On Tuesday, the SCOM 2007 R2 infrastructure of one of my customer reflected the following symptoms :

  • Newly installed agents display as "Not Monitored" in the Operations Console.
  • Agents show as being in maintenance mode in the Operations Console, yet the workflows are not actually unloaded by the System Center Management service on the monitored computer.
  • Configuration changes, new rules or monitors, or overrides will not applied to some agents.
  • The Operations Manager event log on one or more agents will display event 21026, indicating that the current configuration is still valid, even though the configuration for these agents should have been updated.
  • The file "OpsMgrConnector.Config.xml" in the management group folder under "Health Service State"\"Connector Configuration Cache" does not update for long periods of time relative to the rest of the management group on one or more agents.
  • SCOM Email alerts will not triggered.
  • RMS event log is flooded by event 21042: Operations Manager has discarded 1 items in management group MGTGROUP, which came from $$ROOT$$. These items have been discarded because no valid route exists at this time. This can happen when new devices are added to the topology but the complete topology has not been distributed yet. The discarded items will be regenerated.
  • RMS contains the event 29106: The request to synchronize state for OpsMgr Health Service identified by "a340d2a9-ab1b-2e53-ca78-d303510c831d" failed due to the following exception "Microsoft.EnterpriseManagement.Common.DataItemDoesNotExistException: An instance was deleted before its properties could be read.On the RMS, if you deleted the Health Service State folder and restarted the 3 SCOM Services, the file "OpsMgrConnector.Config.xml" is not generated and on the MS you have the event 20070: The OpsMgr Connector connected to RMSFQDN, but the connection was closed immediately after authentication occurred. The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration. Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.

Concerning the resolution, the first step is to make sure to have a good backup of all your Operations Manager databases /!\ The actions below are not supported, do it at your own risk /!\

Connect on the OperationsManager Database and run the following query :

This query will look for the objects that have not been completely and correctly deleted from the database. Normally this query must return nothing, but in our case, it returned a BaseManagedEntityId. This GUID correspond to an object that has been deleted but some references are still existing in the DB.

clip_image002

We have now to identify which computer is behind this id. For that run that following query

clip_image004

In our case, it returned an exchange server, I did a quick check of the server itself, SCOM agent is installed, nothing strange in the log. I went back in my SCOM console, and there, impossible to find the computer in the agent managed view. The object is well deleted but not all his references.

As this server seems to be cause of our trouble, we will delete all his references from the database by running the following query.

Now, go back to the RMS, stop the 3 SCOM services, delete the ‘Health Service State’ folder and restart the 3 SCOM services.

Normally, after a few second the OpsMgrConnector.Config.xml file will be created in the “%ProgramFiles%\System Center Operations Manager 2007\Health Service State\Connector Configuration Cache\MGTGROUP” and everything will start to work correctly.

Now concerning the root cause itself, I don’t have any explication, why this server and all his references have not been successfully deleted the first time ? How one server references could cause so much trouble to the infrastructure?

I would like to thank you my MVP friends Silvio Di Benedetto, Marnix Wolf, Bob Cornelissen and also Mihai Buia from the Microsoft Premier Support for their help to resolve this problem.

Cheers

Christopher

SCOM / OpsMgr : Moving the Operations Manager DB – Notes from the field

12:21 pm in Operations Manager by Christopher Keyaert

Last week, I had to move the Operations Manager DB (OpsDB) from one of my customer from SQL Server 2005 to SQL Server 2008. On Internet, you have a lot of person who already shared their experience, findings, problems about that migration.

I would like now to share my notes, compilation of posts coming from different sites (URL are provided at the end), that I used to successful migrate that DB.

/!\ The scope of this note is only the OperationsManger DB, not the Reporting DB, not the Datawarehouse DB. /!\


Stopping the services

  • Stop the System Center Management, System Center Data Access, and System Center Management Configuration services on the root management server and the System Center Management service on all the management servers.

Backup/Restore the DB

  • Start a backup /restore of the Operations Manager DB, from the SQL Server 2005 to the SQL Server 2008. Nothing Special at this point, just a classical backup/restore. Ensure to copy also all the existing the permissions.

Updating the registry

The following actions have to be taken on the RMS and all the MS.

  • Log on to the management server with Administrator permissions.
  • Click Start, select Run, type regedit in the Open box, and then click OK to start Registry Editor.
  • Under HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Setup, double-click the value DatabaseServerName, and then change the value to the hostname of the SQL Server-based computer now hosting the OperationsManager database. If you are using a named instance of SQL Server, be sure to use the ServerName\Instance name format.
  • Click OK.
  • Close the Registry Editor.

Updating DB

On the SQL Server 2008, update the OperationsManager database with the New Database Server Name, and ensure that the account that you are logged on with has sufficient privileges on the SQL Server instance.
    1. Open SQL Server Management Studio.
    2. Expand Databases, OperationsManager, and Tables.
    3. Right-click dbo.MT_ManagementGroup, and then click Open Table if you are using SQL Server 2005 or click Edit Top 200 Rows if you are using SQL Server 2008.
    4. Change the value in the SQLServerName_6B1D1BE8_EBB4_B425_08DC_2385C5930B04 column to reflect the name of the new SQL Server-based computer.

Enable  CLR functions

In order to support regular expressions in Operations Manager SQL queries, the development team needed to create CLR functions that use .NET’s RegEx library. 
Operations Manager Setup configures SQL to allow execution of the CLR code. When the customer in this case moved the database from one SQL server to another they 
lost this setting in the OperationsManager Database.

To resolve this issue, on the SQL Server 2008, run the following query on the OperationsManager database:

sp_configure @configname=clr_enabled, @configvalue=1
GO

Let that command execute successfully then run

RECONFIGURE
GO

Add back the missing information into the MASTER database

After moving your OperationsManager Database–you might find event 18054 errors in the SQL server application log. Because in this process – we simply restore the Operations Database ONLY, we do not carry over some of the modifications to the MASTER database that are performed when you run the Database Installation during setup to create the original operations database.

To resolve this – you should run the attached SQL script against the Master database of the SQL instance that hosts your OperationsManager Database

http://scug.be/christopher/files/2012/06/Fix_OpsMgrDB_ErrorMsgs.zip

Check the permissions on the DB

Just check if the permissions of the new server are ok.

  1. On the new server hosting the OperationsManager database, add the correct permission for the login of the root management server on which the SDK Account is running, as follows:
    • Open Microsoft SQL Server Management Studio, and in the Object Explorer pane, navigate to Security and then expand Logins.
    • Locate the SDK Account, and add the account if it is not listed.
    • If the SDK Account is running as LocalSystem, use the format <domain\computername$> in SQL Logins, where <computername> is the name of the root management server.
    • Right-click the SDK Account, and select Properties.
    • In the Login Properties dialog box, in the Select a page pane, select User Mapping.
    • In the Users mapped to this login list, in the Map column, select the box that corresponds to OperationsManager (default name).
    • In the Database role membership for: OperationsManager list, ensure that the following items are selected: configsvc_users, db_datareader, db_datawriter,db_ddladmin, and sdk_users.
    • Click OK to save your changes and to close the Login Properties dialog box.
  1. On the new server hosting the Operations Manager database, add the correct permission for the login of the root management server on which the Action Account is running, as follows:
    • Open Microsoft SQL Server Management Studio, and in the Object Explorer pane, navigate to Security and then expand Logins.
    • Locate the Action Account, and add the account if it is not listed. If the Action Account is running as LocalSystem, use the format <domain\computername$> in SQL Logins, where <computername> is the name of the root management server.
    • Right-click the Action Account, and select Properties.
    • In the Login Properties dialog box, in the Select a page pane, select User Mapping.
    • In the Users mapped to this login list, in the Map column, select the box that corresponds to OperationsManager (default name).
    • In the Database role membership for: OperationsManager list, ensure that the following items are selected: db_datareader, db_datawriter, db_ddladmin, anddbmodule_users.
    • Click OK to save your changes and to close the Login Properties dialog box.
  1. On the new server hosting the Operations Manager database, add the correct permission for the login of the Data Warehouse server on which the Data Warehouse Action Account is running, as follows:
    • Open Microsoft SQL Server Management Studio, and in the Object Explorer pane, navigate to Security and then expand Logins.
    • Locate the Data Warehouse Action Account, and add the account if it is not listed.
    • Right-click the Data Warehouse Action Account, and select Properties.
    • In the Login Properties dialog box, in the Select a page pane, select User Mapping.
    • In the Users mapped to this login list, in the Map column, select the box that corresponds to OperationsManager (default name).
    • In the Database role membership for: OperationsManager list, ensure that the following items are selected: db_datareader and dwsynch_users.
    • Click OK to save your changes and to close the Login Properties dialog box.

Set Enable BROKER

Before you can run tasks and use the Discovery Wizard to install agents, you need to set the ENABLE_BROKER value.After moving the Operations Manager database, the status of the Sql Broker Availability Monitor might be set to Critical or Sql Broker is disabled. You can check the state of the Sql Broker Availability Monitor by running the following SQL query:

SELECT is_broker_enabled FROM sys.databases WHERE name=’OperationsManager’

Where ‘OperationsManager’ is the default database name, replace this name as appropriate. If the query result is ‘0’, the Sql Broker is disabled and you must re-enable it using the following procedure.

To set ENABLE_BROKER

  1. Open SQL Server Management Studio.
  2. In the Connect to Server dialog box, select the appropriate values in the Server type list, Server name list, and Authentication list, and then click Connect.
  3. Click New Query.
  4. In the query window, enter the following query:
    ALTER DATABASE OperationsManager SET SINGLE_USER WITH ROLLBACK IMMEDIATE
  5. Click Execute.
  6. Enter the following query:
    ALTER DATABASE OperationsManager SET ENABLE_BROKER
  7. Click Execute.
  8. Close SQL Server Management Studio.

Note : Closing SQL Server Management Studio closes the connection to the database in single-user mode. Depending on your configuration, you might have to manually stop any process that is connected to the database before completing the ALTER query below.

  1. Open SQL Server Management Studio.
  2. In the Connect to Server dialog box, select the appropriate values in the Server type list, Server name list, and Authentication list, and then click Connect.
  3. Click New Query.
  4. In the query window, enter the following query:
    ALTER DATABASE OperationsManager SET MULTI_USER
  5. Click Execute.

You can verify the setting for ENABLE_BROKER is set to 1 by using this SQL query: SELECT is_broker_enabled FROM sys.databases WHERE name=’OperationsManager’

Starting the services

  • On all management servers in the management group, restart the System Center Management, System Center Data Access, and System Center Management Configuration services on the root management server, and then restart only the System Center Management service on the remaining management servers.

Conclusion

Normally, if you followed the notes above, the move of your Operations Manager DB must be successful as the one I did.
As I said, I’m not the author of the notes, I just compiled them into one post. All the information are coming for the links below :

Resources :

http://technet.microsoft.com/en-us/library/cc540384.aspx
http://blogs.technet.com/b/kevinholman/archive/2010/08/26/moving-the-operations-database-my-experience.aspx
http://blogs.technet.com/b/smsandmom/archive/2007/10/11/scom2007-moving-the-operations-manager-database.aspx
http://blogs.technet.com/b/kevinholman/archive/2010/10/26/after-moving-your-operationsmanager-database-you-might-find-event-18054-errors-in-the-sql-server-application-log.aspx

Regards
Christopher