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

Migration · operations manager · opsmgr · Scom · SQL

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.

Click on Next to continue.

Click on Next to continue.

Specify the destination folder and Click on Next to continue.

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

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.

Click on Install to continue.

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.

And finally, click on Finish.

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./!

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.

Discovery is in progress.

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

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.

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

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

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.

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.

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

Regards
Christopher KEYAERT

operations manager · opsmgr · Scom

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

nworks · operations manager · opsmgr · SCCM · Scom · SCOrchestrator · veeam · VMWare

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.

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

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.

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

operations manager · opsmgr · Scom

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:

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

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_MACHINESYSTEMCurrentControlSetServicesTcpip6Parameters
• 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.

Regards
Christopher Keyaert

operations manager · opsmgr · Scom