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 :

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

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

First part of the Script, we define the variables :

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.

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.

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

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 :

The xml file is built :

The task successfully ran:

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

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.

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

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

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

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

Specify the Action Account for this management server.

Specify now the SDK and Config Service Account.

We are new ready for the installation.

Installation done.

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

CU5 Installed on our new management server.

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

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

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

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.

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

Click on YES.

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

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

We’re starting a new SQL installation

Select SQL Server Feature Installation

Check at least the check boxes below

Just click on next.

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

Review the information and click on next.

Configure your Run As Account for the SQL Server.

In the Collation Tab, select SQL_Latin1_General_CP1_CI_AS and click next.

Specify the SQL Admins for your new SQL Server.

Select Install the Native Mode Default Configuration and click Next.

Just review the information and click on Next.

Just review the information and click on Next.

Just review the information and click on Install.

Installation is in progress.

Installation Completed Successfully.

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

Accept the license terms and click next.

Review the information and click on next.

Review the information and click on next.

Review the information and click on update.

Update is in progress.

SP1 has been successfully installed.

Report Server Uninstallation

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

Uninstallation in progress.

SQL Server 2005 : Backup the DBs

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

Select the backup location for your Operations DB.

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

The backup of the Operations Manager DB completed successfully.

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

We’ve got now, two DB Backup files.

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.

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

Check the Restore box next your DB name.

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

Review all the information, and click on OK.

Do exactly the same for the Data Warehouse DB.

Both DBs are now available.

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.

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 :

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

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.

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

Click on Execute and check the result.

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

Select Edit Top 200 Rows.

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

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

Select Edit Top 200 Rows.

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

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 : Changing the link to the DB server

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

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

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

Start the 3 Operations Manager Services on the RMS.

In the Event Logs, you must see these events.

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>

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

Install System Center Operations Manager 2007 R2 Reporting.






Select only the Reporting Server Part.


Specify the name of you RMS server.


Specify the name of your new SQL Server.


Review the information and click on Next.


Click on Next.


Click on Next.


Click on Install.


Installation in progress.


Installation done.

The Reporting is Back in SCOM Console.

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


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

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

The TechDays 2012 Belgium will happen between the FEB 14 and FEB 16 in Belgium at KinePolis Imagibraine. During these 3 days, a lot of IT Pro sessions will be delivered, the complete list is available http://www.microsoft.com/belux/techdays/2012/Home.aspx

My Agenda for the TechDays :

Monitoring and Operating a Private Cloud with System Center 2012
Speaker : Adam Hall | Level : 300
Date : 14 February 2012 | Timeslot : 10:45 - 12:00
Themes : Cloud, Virtualization, ITPRO, Level 300, Hyper-V, System Center, Windows Server 2008 R2
Type : IT Pro
http://www.microsoft.com/belux/techdays/2012/SessionDetail.aspx?sessionId=232

Configuring and Deploying a Private Cloud with System Center 2012
Speaker : Adam Hall | Level : 300
Date : 14 February 2012 | Timeslot : 13:00 - 14:15
Themes : Cloud, Virtualization, Windows Server 2008 R2, System Center, ITPRO, Level 300, Hyper-V
Type : IT Pro
http://www.microsoft.com/belux/techdays/2012/SessionDetail.aspx?sessionId=231

The Private Cloud, Principles, Patterns and Concepts
Speaker : Tom Shinder | Level : 300
Date : 15 February 2012 | Timeslot : 13:00 - 14:15
Themes : Cloud, Level 300, ITPRO, Virtualization
Type : IT Pro
http://www.microsoft.com/belux/techdays/2012/SessionDetail.aspx?sessionId=252

Private Cloud Day Session 1: Building your Private Cloud Infrastructure
Speaker : Kurt Roggen | Level : 300
Date : 16 February 2012 | Timeslot : 09:00 - 10:15
Themes : Deep Dive Post-conference, Cloud Computing, Virtualization
Type : IT Pro
http://www.microsoft.com/belux/techdays/2012/SessionDetail.aspx?sessionId=284

Private Cloud Day Session 2: Creating & Configure your Private Cloud
Speaker : Kurt Roggen | Level : 300
Date : 16 February 2012 | Timeslot : 10:45 - 12:00
Themes : Cloud, Deep Dive Post-conference
Type : IT Pro
http://www.microsoft.com/belux/techdays/2012/SessionDetail.aspx?sessionId=285

Private Cloud Day Session 3: Monitor & Operate your Private Cloud
Speaker : Mike Resseler | Level : 300
Date : 16 February 2012 | Timeslot : 13:00 - 14:15
Themes : Cloud, Deep Dive Post-conference, ITPRO
Type : IT Pro
http://www.microsoft.com/belux/techdays/2012/SessionDetail.aspx?sessionId=256

Private Cloud Day Session 4: Automating & Delivering Services in your Private Cloud
Speaker : Mike Resseler Kurt Roggen | Level : 300
Date : 16 February 2012 | Timeslot : 14:30 - 15:45
Themes : Cloud, Virtualization, Level 300, ITPRO, Deep Dive Post-conference
Type : IT Pro
http://www.microsoft.com/belux/techdays/2012/SessionDetail.aspx?sessionId=255

Private Cloud Day Session 5: A Solution for Private Cloud Security
Speaker : Tom Shinder | Level : 300
Date : 16 February 2012 | Timeslot : 16:15 - 17:30
Themes : Cloud, Virtualization, Deep Dive Post-conference, ITPRO, Level 300
Type : IT Pro
http://www.microsoft.com/belux/techdays/2012/SessionDetail.aspx?sessionId=253

Christopher Keyaert – Ops Mgr MVP

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 :

DB Server supported configuration :

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.

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.

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.

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.

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.

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.

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

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

His summary :

The RMS Emulator only provides backward compatibility to management pack using things which target the ‘Root Management Server’ class instance (Target=”SC!Microsoft.SystemCenter.RootManagementServer). The RMS emulator is hosted on a management server and as such it does a lot of activities that aren’t specific to the RMSE role. Everything else the RMS used to be responsible for is managed by the “All Management Servers Resource Pool”, the “Notifications Resource Pool” and the “AD Assignment Resource Pool”.

I really invite you to read the complete story available : HERE

Christopher

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.

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.

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

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

Or by looking on in the SCOM Console :

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

Two days ago, I received the Microsoft MVP award for the first time. I’m really happy and proud of this status. I will continue to do my best for sharing my knowledge with the System Center Community.

I would like to thank you all my readers, the persons who follow me on tweeter, SCUG.be Team, Microsoft and of course the System Center Community.

Thank you
Christopher

First day back to work after the Xmas holidays and first error of the year
Below 3 events that I found on a customer server, that was not reporting to Operations Manager anymore.

Event Type:    Error
Event Source:    HealthService
Event Category:    Health Service
Event ID:    1220
Date:        1/3/2012
Time:        4:22:36 PM
User:        N/A
Computer:    xxxx
Description:
Received configuration cannot be processed. Management group "xxxx". The error is 0x80FF0066(0x80FF0066).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:    Error
Event Source:    HealthService
Event Category:    Health Service
Event ID:    7022
Date:        1/3/2012
Time:        4:22:35 PM
User:        N/A
Computer:    xxxx
Description:
The Health Service has downloaded secure configuration for management group xxxx, and processing the configuration failed with error code 0x80FF0066(0x80FF0066).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:    Warning
Event Source:    HealthService
Event Category:    Health Service
Event ID:    7004
Date:        1/3/2012
Time:        4:22:35 PM
User:        N/A
Computer:    xxxx
Description:
The Health Service received a secure message from management group xxxx which was encrypted using the wrong public key.  This message has been discarded and the public key will be re-published.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The root cause is a missing registry key on the server. Take a look to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\Management Groups\UCBOM2007\SSDB\References

On the non working server :

On a working server :

When you compare the both servers, you notice that the following registry key is missing :

Just import the missing registry key from the working server to the non working server, and after a few seconds, the event below will appear, problem fixed

Event Type:    Information
Event Source:    OpsMgr Connector
Event Category:    None
Event ID:    21025
Date:        1/3/2012
Time:        4:28:37 PM
User:        N/A
Computer:    xxxx
Description:
OpsMgr has received new configuration for management group xxxx from the Configuration Service.  The new state cookie is "24 58 21 8C 7C D4 70 68 B2 87 1A 52 EA BE 7F 66 43 10 FC A7 "

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

If you want more information about this issue, I invite you to read the two followings posts :

http://thoughtsonopsmgr.blogspot.com/2009/02/eventid-7024.html
http://www.systemcentercentral.com/tabid/60/indexId/34058/tag/Forums+Operations_Manager/Default.aspx#vindex56241

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

Just a quick post to show you how to retrieve SCCM Client Service Window directly from a PowerShell script. The script is really simple, it queries the class CCM_ServiceWindow in the namespace "root\CCM\policy\machine\actualconfig". This script must be executed directly on a SCCM Client computer.

Script :

Output :

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