You are browsing the archive for SCOM.

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

OpsMgr / SCOM : NetApp Management pack 3.0 – Installation

12:04 pm in Uncategorized by Christopher Keyaert

A few months ago, Netapp upgraded, renamed and grouped their Microsoft System Center management pack and Microsoft PowerShell command-lets into one new product, the OnCommand Plug-in for Microsoft.

This new version of this tool includes also new functionalities like:

· Opalis Integration Packs
· Discovery Agent for Hyper-V host
· Complete documentation for all these functionalities.

Here we will focus only on the Microsoft Operations Manager management pack. This application has to be installed on a management server, if possible, avoid installing it on the root management server.

Copy the file, OnCommand-PlugIn-Microsoft_3.0_x64_NetApp.exe, on the root management server and let’s start the installation by double clicking on it. Unfortunately, we don’t have the choice here, it must run from the RMS.

If a previous version of the management pack is installed, like the Data Ontap Appliance Watch PRO 2.1, it will be automatically uninstalled it.

Click on Yes to continue.
clip_image001

Click on Next to continue.
clip_image002

Click on Next to continue.
clip_image003

Specify the destination folder and Click on Next to continue. clip_image004

As we are only interested by the SCOM Management Pack, we will not install other component.
clip_image005

NetApp OnCommand needs to run a Web Service. Create a Service Account that will be local admin of the server on which you install the software. Set the credentials and click on Next.clip_image006

Click on Install to continue.
clip_image007

The installation is now in progress, it will install the application, but it will also automatically import/upgrade the NetApp management packs to the Operations Manager Infrastructure.clip_image008

And finally, click on Finish.
clip_image009

Start the SCOM Console, the installation process automatically installed the new the NetApp Management packs. /!\ If you were previously using the Netapp management pack, extract your custom management pack because the upgrade will simply remove it, which could be really frustrating. After the upgrade, you are able to reinstall it. It seems that NetApp changed some class, be sure to check that your overrides are well targeting the right classes./!\
clip_image011

The next step is to add the Netapp Controllers as Network device. Go to Administration > Network Devices > Discovery Wizard. Specified the IP range and start the discovery.
clip_image013

Discovery is in progress.
clip_image015

The controllers have been discovered as SNMP devices. Select all the controllers and click Finish.
clip_image016

Go to Monitoring > Data ONTAP > Storage Systems > Management Server, choose the root management server that will monitor your Netapp infrastructure and run the Data ONTAP : Run Discovery Task.

After a few moments, the Netapp Controllers will automatically appear in the Data Ontap > Storage Systems > Controllers view.
clip_image018

Extend the actions pane and click on Data ONTAP : Manage Controller Credentials task.
clip_image019

This will start the Netapp Credentials Manager, where we have to specify the credentials for all the NetApp Controllers.
clip_image021

When done, go back to the SCOM console, Go to the Authoring section > Management Pack Objects > Rules and search for the Data ONTAP: Discovery Rule.
clip_image022

This is the principal discovery rule for all Data ONTAP storage systems. Once you use the SNMP network device Discovery wizard in System Center Operations Manager to discover your Data ONTAP storage controllers, this rule contacts each storage controller and discovers all of its physical and logical storage elements.

This rule is disabled by default. You should enable the rule, via an override, for the management server that will monitor your Data ONTAP storage controllers.clip_image024

After a few moments, the entire infrastructure will be discovered and all the views will be populated.
clip_image026

clip_image027

Regards
Christopher KEYAERT
clip_image001 clip_image002 clip_image004 clip_image005 clip_image007 clip_image008

System Center 2012 RTM is available

12:33 am in Uncategorized by Christopher Keyaert

Yesterday, during the  Microsoft Management Summit keynote, Microsoft announced the availability of System Center 2012 RTM. You could download for free, the evaluation version via the following link : http://aka.ms/PvtCld

The Microsoft private cloud evaluation includes:

System Center 2012

  • System Center 2012 Unified Installer is a utility designed to perform new, clean installations of System Center 2012 for testing and evaluation purposes only. If you want to upgrade from an existing System Center installation or choose set up options such as high availability or multi-server component installs, please refer instead to the System Center 2012 component installation guides located on the Microsoft Private Cloud Evaluation Resource Page.
    User’s Guide >>
  • System Center 2012 App Controller provides a common self-service experience across private and public clouds that can help you empower application owners to easily build, configure, deploy, and manage new services.
    System Requirements >>
  • System Center 2012 Configuration Manager provides comprehensive configuration management for the Microsoft platform that can help you empower users with the devices and applications they need to be productive while maintaining corporate compliance and control.
    System Requirements >>
  • System Center 2012 Data Protection Manager provides unified data protection for Windows servers and clients that can help you deliver scalable, manageable, and cost-effective protection and restore scenarios from disk, tape, and off premise.
    System Requirements >>
  • System Center 2012 Endpoint Protection, built on System Center Configuration Manager, provides industry-leading threat detection of malware and exploits as part of a unified infrastructure for managing client security and compliance that can help you simplify and improve endpoint protection.
    System Requirements >>
  • System Center 2012 Operations Manager provides deep application diagnostics and infrastructure monitoring that can help you ensure the predictable performance and availability of vital applications and offers a comprehensive view of your datacenter, private cloud, and public clouds.
    System Requirements >>
  • System Center 2012 Orchestrator provides orchestration, integration, and automation of IT processes through the creation of runbooks that can help you to define and standardize best practices and improve operational efficiency.
    System Requirements >>
  • System Center 2012 Service Manager provides flexible self-service experiences and standardized datacenter processes that can help you integrate people, workflows, and knowledge across enterprise infrastructure and applications.
    System Requirements >>
  • System Center 2012 Virtual Machine Manager provides virtual machine management and services deployment with support for multi-hypervisor environments that can help you deliver a flexible and cost effective private cloud environment.
    System Requirements >>

Christopher KEYAERT

clip_image001 clip_image002 clip_image004 clip_image005 clip_image007 clip_image008

SCOM 2007 R2 – Reporting : Value of ‘1/01/0001 12:00:00 AM’ is not valid for ‘Value’. ‘Value’ should be between ‘MinDate’ and ‘MaxDate’

8:40 am in Uncategorized by Christopher Keyaert

Hi Guys,

Yesterday, I migrated a SCOM 2007 R2 reporting module from a SQL Server Reporting Services 2005 to a SQL Server Reporting Services 2008 R2. The migration worked perfectly, the reports were available, I was able to start it, everything seems ok, but…

when I checked the scheduled reports, the schedule date/time display was set At 12:00 AM on 1/1/001. Confused smile

image

And when I tried tried to edit a scheduled reports I’ve got the following error :

clip_image002

Hopefully the scheduled reports itself were still running fine, only the display was incorrect and an error message when I tried to edit it. I did some search and I found the following links :

http://wmug.co.uk/blogs/aquilaweb/archive/2008/10/14/reporting-error-value-of-1-1-0001-00-00-00-is-not-valid-for-value.aspx

http://qa.social.technet.microsoft.com/Forums/eu/operationsmanagerreporting/thread/06d79194-2919-4236-bddf-371c7f1cc022

http://nocentdocent.wordpress.com/2010/02/23/reporting-error-when-a-different-locale-is-used-for-srs-and-console/

http://nocentdocent.wordpress.com/2011/03/04/issue-with-reports-and-non-en-us-locale/

All my servers were in English US format, none of the link above solved my problem. Finally, I found this thread :

http://social.technet.microsoft.com/Forums/en-US/operationsmanagerreporting/thread/c070e435-862b-4ccd-ab4a-d2202c61aab3

Update:

I opened up a case with Microsoft Support and resolved the issue. Apperantly this is a known issue and the bug will be addressed in CU6. Microsoft was able to give me a hotfix (QFE_MOMEsc_4724.msi) which I applied on all systems that have SCOM Console. I am told that this issue occurs when SCOM 2007 R2 CU5 runs on SQL 2008 R2.

I hope it helps to others that run into same problem.

ZMR 

I contacted my Microsoft Premier Support Contact and they sent me the hotfix. (Reference : Hotfix for MOMEscalation 4724).

This hotfix is simply a new DLL, Microsoft.MOM.UI.Common.dll, that you will have to place in the Operations Manager installation folder on all the machines where you run the Operations Manager Console. When done, just restart the Operations Console, and you will be able to see the Schedule information and edit the jobs without any error message.

image

As this hotfix is not public, you will have now other choice than contacting the Microsoft Support to get it. I received the confirmation that this hotfix will be included in the SCOM Cumulative Update 6, but we don’t know the release date yet.

Christopher KEYAERT

clip_image001 clip_image002 clip_image004 clip_image005 clip_image007 clip_image008

OpsMgr / SCOM : ADFS 2.0 MP Discovery Issue

10:14 am in Uncategorized by Christopher Keyaert

Hi Everyone,

One of my customer requested me to implement the Active Directory  Federation Services 2.0 Management Pack on Operations Manager 2007 R2.

Management Pack is available here with the Guide :
http://systemcenter.pinpoint.microsoft.com/en-US/applications/active-directory-federation-services-2-0-adfs-monitoring-management-pack-12884905753

The only pre-requisite of this management pack that I found in the documentation is to enable the IIS 6 Management Compatibility:image

After several hours, still no server in the Federation Servers State view, nothing strange in the event viewer:
image

Hopefully, one colleague of mine, that I would like to thank you, found the solution in the Know Issues on Microsoft TechNet :

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

In fact, there is a second pre-requisites that is not in the ADFS MP guide, we have to disable IP version 6 (IPV6) on the agent computer that is running AD FS 2.0.

We have first to disable IPv6 in the Local Area Connection Properties :

But we have also to do it in the server registry. To do that, follow the step below :

  • Click Start, type regedit in the Start Search box, and then click regedit.exe in the Programs list.
  • In the User Account Control dialog box, click Continue.
  • In Registry Editor, locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters \
  • Double-click DisabledComponents to modify the DisabledComponents entry.

Note If the DisabledComponents entry is unavailable, you must create it. To do this, follow these steps:

  • In the Edit menu, point to New, and then click DWORD (32-bit) Value.
  • Type DisabledComponents, and then press ENTER.
  • Double-click DisabledComponents.

And finally, the value of the key:

  • Type 0xffffffff to disable all IPv6 components, except the IPv6 loopback interface

More details on disabling IPv6 : http://support.microsoft.com/kb/929852

You have to do the steps above on all the servers running ADFS 2.0.

Normally, your ADFS 2.0 servers will now shortly be appear in the Operations Manager Console. Smile

Regards
Christopher Keyaert

clip_image001 clip_image002 clip_image004 clip_image005 clip_image007 clip_image008

SharePoint 2010 MP : how to automate the SharePointMP.Config configuration

4:01 pm in Uncategorized by Christopher Keyaert

Dear all,

If you already installed the SharePoint 2010 management pack for Operations Manager 2007, you know that this management pack requires the some extra configuration with a file named SharePointMP.Config

First, I invite you to take a look to the following post to help you to understand how the SharePoint 2010 management pack works :

http://blogs.technet.com/b/berryst/archive/2011/03/25/configuring-scom-r2-management-pack-for-sharepoint-2010-foundation-monitoring.aspx

In fact, It’s quite simple, each time that a server is added to a SharePoint farm, it has to be added to the SharePointMP.Config XML file, like the example below :image

and to complete the configuration, the Operations Manager task “Configure SharePoint Management Pack” must be also started from the Operations Manager Console.
image

Unfortunately, these both actions have to be done manually and each time that a SharePoint server is added to a SharePoint farm…. not really nice…. So let’s try to automate that with PowerShell Smile

First part of the Script, we define the variables :
image

The script connects to each Central Admin SharePoint server that you defined in the variables, to retrieve the complete servers list of each SharePoint farms.
image

The script is now building the SharePointMP.Config XML file and will copy it to the %ProgramFiles%\System Center Management Packs\ folder on the RMS.image

Last step is to start the “Configure SharePoint Management Pack” task in Operations Manager, like you could do it in the Operations Console.
image

The following script has some requirements about the service account that it will use to run :

  • local admin on all SP2010 Front End and Application servers
  • local admin on all SQL boxes that host SharePoint 2010 Databases
  • local admin on Operations Manager Root Management server
  • Operations Manager Administrator
  • dbo for the actual SharePoint databases
  • full farm admin rights within SharePoint 2010

Normally, most of this requirements are already meet with the installation of the SharePoint management pack itself.

The script is limited to the use of the default “SharePoint Discovery/Monitoring Account” Operations Manager Run As Account.

To summary, you have to run this script, on the RMS, every time that you added a server into a SharePoint Farm. Tips : Create a schedule task and run it once per day…. no more manual action to do.

Let’s try to run the script manually :
image

The xml file is built :
image

The task successfully ran:
image

The SharePoint 2010 management pack configuration is now completed and fully automated.

The complete script is available here : DOWNLOAD
Use it at your own risk, feel free to modify it and distribute it.

Regards
Christopher Keyaert

clip_image001 clip_image002 clip_image004 clip_image005 clip_image007 clip_image008

Prepare your environment to Operations Manager 2012 – Part III Moving the RMS role

3:48 pm in Uncategorized by Christopher Keyaert

Hi All,

To continue the serie about “Prepare your environment to Operations Manager 2012”, we have now to move the RMS role to a Windows Server 2008 R2 server and remove the Windows Server 2003 server.

Pre-requisites
Resources

I invite you first to read my previous post :
Prepare your environment to Operations Manager 2012 – Part I Actions Plan
Prepare your environment to Operations Manager 2012 – Part II Updating the SQL Server

Adding a new management server

The really first step is to add our brand new Windows Server 2008 R2 server as a management server in our existing Operations Manager Management Group. As this is a quite regular process, I will skip some screens.

First step, we have to install the .Net Framework 3.5.1.
image

Don’t forget to add your service accounts as Local Administrator of this new server.
image

Let’s starting the installation of this new management server.
image

We only have to install the Manager Server and the User Interfaces.
image

We have to specify our DB server (the new one, running SQL Server 2008 R2 SP1).
image

Specify the Action Account for this management server.
image

Specify now the SDK and Config Service Account.
image

We are new ready for the installation.
image

Installation done.
image

Don’t forget to apply the Cumulative Update 5 to this new management server.
image

CU5 Installed on our new management server.
image

if we take a look in the console, we could see that our new management server is working well.
image

 

Moving the RMS role

As our final goal is to remove the Windows Server 2003 server, we have to promote as RMS our new installed management server.

Pre-requisites
  • Make sure that you have a backup of the databases and all servers.
  • Backup the Key from the RMS by using SecureStorageBackup.exe and copy it to the MS that you want to promote.
    image
  • Be sure to have all the services accounts passwords available.
  • Be sure that no agent, no Linux servers, no website, no network devices that are currently monitored by the RMS.
  • Run the command prompt as Administrator
To promote a management server to a root management server role
  • On the management server that you want to promote, copy the ManagementServerConfigTool.exe tool from the SupportTools folder of the installation media to the installation folder (by default, C:\Program Files\System Center Operations Manager 2007), called installdir in this example.
  • Open a command prompt window using the Run as Administrator option, and then change the folder to the installdir folder.
  • Type the following command:
    SecureStorageBackup.exe Restore < filename >
    image
  • Provide the password as required.
  • On the management server, open a command prompt window using the Run as Administrator option, and then type the following command:
    ManagementServerConfigTool.exe PromoteRMS
    image
To configure the reporting server with the name of the new root management server
  • Log on to the reporting server.
  • Navigate to the installation folder of Reporting Services for example, C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer 
  • Open the rsreportserver.config file in Notepad, and locate the two instances of <ServerName>ServerName</ServerName>, where ServerName is the name of the original root management server. Change ServerName to be the name of the new root management server.
    image
    image
  • Save the file, and then close Notepad.
  • Open the registry and locate the key HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Reporting.
  • Change the DefaultSDKServiceMachine value to be the name of the new root management server.

If we start the console, connect it to the new RMS, we could see that the RMS role has been well moved.
image

Removing the Windows 2003 Server

As we now have our brand new RMS running on Windows Server 2008 R2, the last thing that we have to do is to uninstall Operations Manager 2007 R2 from the Windows Server 2003 server.

Go to the Windows Server 2003, Control Panel, Add/Remove Programs and remove Operations Manager 2007.
image

The last step is to remove the server from the Operations Manager Console, right click on it and chose delete.
image

Click on YES.
image

Our Operations Manager Group is finally compliant for the upgrade to Operations Manager 2012. I will cover this process step by step into a next post.

Don’t hesitate to contact me if you have any question.

Regards
Christopher Keyaert

clip_image001 clip_image002 clip_image004 clip_image005 clip_image007 clip_image008

Prepare your environment to Operations Manager 2012 – Part II Updating the SQL Server

2:29 pm in Uncategorized by Christopher Keyaert

Hi All,

As promise, the second part of this series will show you to how to update your Operations Manager 2007 R2 infrastructure from SQL Server 2005 to SQL Server 2008 R2 SP1.

Pre-requisites

Resources

I invite you first to read my previous post : Prepare your environment to Operations Manager 2012 – Part I Actions Plan

Marnix Wolf, an Operations Manager MVP, already posted a series about the same subject, and I really advise you to read it :

Preparing for migrating to OM12: Moving from SQL 2005 to SQL 2008 – Part I: Along came a theory
Preparing for migrating to OM12: Moving from SQL 2005 to SQL 2008 – Part II: Phase I – The Preparations
Preparing for migrating to OM12: Moving from SQL 2005 to SQL 2008 – Part III: Phase II – The Migration

 

Infrastructure

Below, the pre-requisites from a infrastructure point of view :

  • Your current SCOM 2007 R2 Infrastructure must be at least Cumulative Update 4 (CU4) Level, but my personal advice it’s to update it first to the last Cumulative Update, the CU5.
  • A brand new server running Windows Server 2008 R2 SP1.
  • .Net Framework 3.5.1 role installed.
  • Microsoft SQL Server R2 2008 source +  SP1 Package.
  • Add you SQL Service Account to the local administrator group of the new server.
  • Backup all your SCOM 2007 R2 Infrastructure.

SQL Server 2008 R2 installation

let’s starting
image

We’re starting a new SQL installation
image

Select SQL Server Feature Installation
image

Check at least the check boxes below
image

Just click on next.
image

Use the default instance, or create a new one, depending of your environment.
image

Review the information and click on next.
image

Configure your Run As Account for the SQL Server.
image

In the Collation Tab, select SQL_Latin1_General_CP1_CI_AS and click next.
image

Specify the SQL Admins for your new SQL Server.
image

Select Install the Native Mode Default Configuration and click Next.
image

Just review the information and click on Next.
image

Just review the information and click on Next.
image

Just review the information and click on Install.image

Installation is in progress.
image

Installation Completed Successfully.
image

It’s now time to install the SP1, run the SQLServer2008R2SP1-KB2528583-x64-ENU.exe that you have previously downloaded on Microsoft Website.
image

image

Accept the license terms and click next.
image

Review the information and click on next.
image

Review the information and click on next.
image

Review the information and click on update.
image

Update is in progress.
image

SP1 has been successfully installed.
image

 

Report Server Uninstallation

You must back up any custom reports that were authored outside of Operations Manager 2007. For more information about this, see Moving the Report Server Databases to Another Computer in the SQL Server 2008 Books Online (http://go.microsoft.com/fwlink/?LinkId=151513).

Go to your current SCOM reporting Server, Add and Remove Programs menu and uninstall the System Center Operations Manager 2007 R2 Reporting Server.
image

Uninstallation in progress.
image

 

SQL Server 2005 : Backup the DBs

Go on your SQL Server 2005, start the SQL Management Studio, select OperationsManagerDB, Tasks, Backup.

image

Select the backup location for your Operations DB.
image

In the options, check Verify backup when finished and click on OK.
image

The backup of the Operations Manager DB completed successfully.
image

Do exactly the same operations than above for the Data Warehouse DB.
image

We’ve got now, two DB Backup files.
image

 

SQL Server 2008 R2 SP1 : Restoring the DBs

It’s now time to go on your brand new SQL Server 2008 R2 SP1 server to restore the two databases.

Start the Sql Management Studio and choose Restore Database.
image

Select restore from Device and add the backup file of your OperationsManager DB and click OK
image

Check the Restore box next your DB name.
image

In the Destination for restore, you are now able to specify the OperationsManager DB.
image

Review all the information, and click on OK.
image

Do exactly the same for the Data Warehouse DB.
image

Both DBs are now available.
image

Now, we have to authorize the SCOM service accounts to connect to these newly restored DBs. For that simply go Sql Management Studio, Security Logins and do a right click, chose new login.
image

In the User Mapping part, we have to copy exactly the same rights that we have on the SQL Server 2005.

On the SQL Server 2005 :
image

Replicate the exact same configuration, for each Maps to the SQL Server 2008 R2 SP1.
image

If you are using several account to connect to the different Database, apply the same than what we did above for all your accounts. For my lab environment, I just have a second account.
image

We have to Enable the CLR on the Operations Manager DB on the SQL Server 2008 R2 SP1 server. Just copy past the query below.

sp_configure ‘show advanced options’, 1;

GO

RECONFIGURE;

GO

sp_configure ‘clr enabled’, 1;

GO

RECONFIGURE;

GO

image

Click on Execute and check the result.
image

Now, in the OperationsDB, search for the table dba.MT_ManagementGroup.
image

Select Edit Top 200 Rows.
image

Change the SQLServerName_6B1D1BE8_EBB4_B425_08DC_2385C5930B04 value from your SQL Server 2005 server name to the SQL Server 2008 server name.
image

Go on your OperationsManagerDW Db, select the table dbo.MemberDatabase.
image

Select Edit Top 200 Rows.
image

Change the ServerName value from your SQL Server 2005 name to the SQL Server 2008 name.
image

Enable the SQL Broker, for that, take a look to Alexander’s post : http://scug.be/blogs/scom/archive/2008/11/22/the-sql-server-service-broker-for-the-current-opsmgr-database-is-not-enabled.aspx

 

RMS & MS : Changing the link to the DB server

We now have to change the SQL server reference on the RMS server and every MS to point to the new SQL Server. For that, stop the three System Center Services.
image

Launch the RegEdit and look for the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup

image

We have to change the DatabaseServerName value to point to our new SQL Server.
image

Start the 3 Operations Manager Services on the RMS and the System Center Management service on the MS. 
image

In the Event Logs, you must see these events.
image

image

 

Last but not least, the reporting server.

Microsoft released a KB for running Operations Manager 2007 R2 on SQL Server 2008 R2 KB245714. http://support.microsoft.com/kb/2425714

Open Computer Management, in the Computer Management MMC snap-in, expand System Tools, expand Local Users and Groups, and then click Groups.

Locate the following group:
SQLServerReportServerUser$<hostname>$MSRS10_50.<SQLInstanceName>
image

Rename the group to the following by removing "_50" from the group name:
SQLServerReportServerUser$<hostname>$MSRS10.<SQLInstanceName>
image

Install System Center Operations Manager 2007 R2 Reporting.
image

image

image

Select only the Reporting Server Part.
image

Specify the name of you RMS server.
image

Specify the name of your new SQL Server.
image

Review the information and click on Next.
image

Click on Next.
image

Click on Next.
image

Click on Install.
image

Installation in progress.
image

Installation done.image

The Reporting is Back in SCOM Console.
image

After you install System Center Operations Manager 2007 R2 Reporting, rename SQLServerReportServerUser$<hostname>$MSSRS10.<SQLInstanceName>
image

back to original name SQLServerReportServerUser$<hostname>$MSSRS10_50.<SQLInstanceName>
image

We could now remove the SQL Server 2005 and enjoy our new SQL Server 2008 R2 SP1.

I hope this post will help you to prepare your environment to be ready for SCOM2012. The next post of this series will show you how to migrate your RMS role from Windows Server 2003 SP2 to Windows Server 2008 R2 SP1.

Christopher Keyaert – Ops Mgr MVP

mvp_avatar

Prepare your environment to Operations Manager 2012 – Part I Actions Plan

8:16 pm in Uncategorized by Christopher Keyaert

Hi all,

I will start this new series of posts about Operations Manager 2012 by explaining how to prepare your SCOM2007 environment to move to SCOM2012. The very first step to do before updating OM itself is to update the existing environment configuration, OS and DB, to be compliant with the OM2012 requirements.

Hopefully for us, you will see that there is several OS and DB configurations supported by bot Operations Manager releases, OM2007 and OM2012.

I invite you to take a look to the information available on Microsoft TechNet :

Operations Manager 2007 R2 Supported Configurations
http://technet.microsoft.com/en-us/library/bb309428.aspx

Operations Manager 2012 Supported Configurations
http://technet.microsoft.com/en-us/library/hh205990.aspx

I did a summary of he OS and DB configurations information in the tables below :

Supported Configuration for OM2007 and OM2012

Management Server supported configuration :

OS Configuration

SCOM 2007 R2

SCOM 2012

Windows Server 2003 SP2 X86

Supported

Not Supported

Windows Server 2003 SP2 X64

Supported

Not Supported

Windows Server 2003 R2 SP2 X32

Supported

Not Supported

Windows Server 2003 R2 SP2 X64

Supported

Not Supported

Windows Server 2008 SP2 X86

Supported

Not Supported

Windows Server 2008 SP2 X64

Supported

Not Supported

Windows Server 2008 R2 SP1

Supported

Supported

DB Server supported configuration :

OS Configuration

SCOM 2007 R2

SCOM 2012

Windows Server 2003 SP2 X86

Supported

 

Windows Server 2003 SP2 X64

Supported

Not Supported

Windows Server 2003 R2 SP2 X32

Supported

Not Supported

Windows Server 2003 R2 SP2 X64

Supported

Not Supported

Windows Server 2008 SP2 X86

Supported

Not Supported

Windows Server 2008 SP2 X64

Supported

Supported

Windows Server 2008 R2 SP1

Supported

Supported

          

DB Configuration

SCOM 2007 R2

SCOM 2012

SQL Server 2005 SP1/SP2/SP3/SP4

Supported

Not Supported

SQL Server 2008 SP1

Supported

Supported

SQL Server 2008 SP2

Supported

Not Supported

SQL Server 2008 R2 RTM/SP1

Supported

Supported

As you can see, several configurations are supported by OM2007 and OM2012.

The actions plan – Theory Part

In this posts series, we will work on a really small SCOM 2007 R2 infrastructure. We just have, one DB server and one Root Management Server. Concerning the configuration, both are running Windows Server 2003 R2 SP2 X64 and the Operations Manager DBs are hosted on SQL Server 2005 SP3.

image

As we could conclude from the tables above, our current Operations Manager 2007 infrastructure is not eligible for Operations Manager 2012. We have to update the Operating Systems on both servers and the SQL Server version must be also updated.

Updating the DB server

As we have to move from SQL Server 2005 to SQL Server 2008 R2 SP1, we will install a brand new server which will run Windows Server 2008 R2 SP1 and SQL Server 2008 R2 SP1.

image

We will move the Operations Manager 2007 DBs from the old SQL Server 2005 to the new SQL Server 2008 R2 SP1. Don’t worry  too much about this part, the second post of this series will explain in detail how to move the Operations Manager DBs from SQL 2005 to SQL 2008.

image

Once done, we will remove the old SQL Server from our infrastruture.

Updating the RMS server

Now that our Operations Manager is running on the new SQL Server 2008, we will update the RMS. Our Root Management Server is currently running Windows Server 2003 R2 SP2 X64. To be compliant to SCOM2012, we will have to update it to Windows Server 2008 R2 SP1.

image

For doing this update, we will first install a brand new server running Windows Server 2008 R2 SP1 and install it as a new Management Server in our current SCOM 2007 R2 infrastructure.

image

Once done, we have to promote our brand new Management Server as Root Management Server of our OM infrastructure. The old RMS will be retrograded to a Management Server role.

image

and finally, we will remove the Management Server which is running Windows Server 2003 R2 SP2 X64.

image

We have now an environment eligible to Operations Manager 2012.

Conclusion

As we noticed, there is several step to accomplish. This first post was the actions plan, the theory, in my next posts, we will do it in practice.

Stay tune for the next post, in which I will explain in detail how to move the Operations Manager DBs from SQL Server 2005 to SQL Server 2008 R2 SP1.

Resources

Microsoft System Center Operations Manager 2007 R2 download
http://technet.microsoft.com/en-us/evalcenter/bb738014.aspx

Microsoft System Center Operations Manager 2012 RC download
http://www.microsoft.com/download/en/details.aspx?id=27974

Operations Manager TechNet Forums
http://social.technet.microsoft.com/Forums/en-US/category/systemcenteroperationsmanager

Christopher Keyaert – Ops Mgr MVP
mvp_avatar   

SCOM 2012 : How to move RMS Emulator role

10:10 am in Uncategorized by Christopher Keyaert

Hi,

As you probably know, in SCOM 2012, there is no RMS role anymore. For keeping backward compatibility with some management packs that required the RMS role, Microsoft created the RMS Emulator role.

By default this role is hosted on the first management server that you installed.
image

As you can see, SCOM2012.vnext.be server is hosting the RMS Emulator role. This is confirmed by the following PowerShell command : GET-SCOMRMSEmulator command-let.
image

Now, if you want to move this role to another, simply execute the command : Get-SCOMManagementServer -Name "NewServerThatWillHostRMSEmulatorRole" | Set-SCOMRMSEmulatorimage

You could confirm the move of the RMS Emulator role by retyping the command : GET-SCOMRMSEmulatorimage

Or by looking on in the SCOM Console :image

Cheers
Christopher KEYAERT
http://twitter.com/keyaertc