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 :

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

operations manager · opsmgr · Scom

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.

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 FilesSystem 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 FilesMicrosoft SQL ServerMSRS10_50.MSSQLSERVERReporting ServicesReportServer 
• 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_MACHINESoftwareMicrosoftMicrosoft Operations Manager3.0Reporting.
• 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

operations manager · opsmgr · Scom