System Center Operations Manager 2012 Beta is now available for public download.

Here’s what’s new

• Rich application performance monitoring and diagnostics for .NET applications plus JEE application health monitoring
• Support for monitoring heterogeneous environments
• Integrated network device monitoring and alerts
• Simplified management infrastructure (no more RMS)
• Common console across datacenter and clouds with customizable dashboards

Microsoft Download link : DOWNLOAD
Microsoft Official announcement : Read it

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

beta · operations manager · opsmgr · rms · Scom

Promoting a new server as the new RMS of your SCOM infrastructure could be very useful when you want to upgrade your OS from Windows Server 2003 to Windows Server 2008.
The information below are coming directly from Microsoft TechNet, I just add some print screen for simplifying the procedure.

In the example, CENMOMRMS701 is my current RMS and CENMOMMS701 is the MS that I want to promote as RMS.

Pre-requisites

1. Make sure that you have a backup of the databases and all servers.
2. Backup the Key from the RMS by using SecureStorageBackup.exe
   and copy it to the MS that you want to promote.
3. Be sure to have all the services accounts passwords available.
4. Be sure that no agent, no Linux servers, no website, no network devices that are currently monitored by the RMS.

To promote a management server to a root management server role

1. 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.
   
2. Open a command prompt window using the Run as Administrator option, and then change the folder to the installdir folder.
   
3. Type the following command:
   

   SecureStorageBackup.exe Restore < filename >
   

   
   

   Here, filename is the root management server encryption key backup file.
   

4. Provide a password as required.
   
5. On the management server, open a command prompt window using the Run as Administrator option, and then type the following command:
   

   ManagementServerConfigTool.exe PromoteRMS
   

6. You will see two warnings come up. The first warns you to backup your OperationsManager database, the second warns you to take the System Center Management, System Center Management Configuration and System Center Data Access services offline if your RMS is on a cluster. Type in Y for both.
   

   
   

7. Demote the original root management server to a management server by doing the following on the original root management server:
   
   • Type the following command: ManagementServerConfigTool.exe UpdateDemotedRMS. Type in Y to the backup database warning.

   
   

   • Stop System Center Management service
   • Delete the existing subfolders of the Health Service State folder in the installdir.
   • Start System Center Management service

To configure the reporting server with the name of the new root management server

1. Log on to the reporting server.
   
2. Navigate to the installation folder of Reporting Services for example, %ProgramFiles%\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer if you are using SQL Server 2005 or %ProgramFiles%\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer if you are using SQL Server 2008.
   
3. 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.
   
4. Save the file, and then close Notepad.
   
5. Open the registry and locate the key HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Reporting.
   
6. Change the DefaultSDKServiceMachine value to be the name of the new root management server.
   

To configure the data warehouse server with permissions for the new root management server

1. On the server hosting the data warehouse, open Microsoft SQL Server Management Studio, and in the Object Explorer pane, navigate to Security and then expand Logins.
   
2. Locate the account that corresponds to the new root management server and on which the System Center Data Access Service is running (if it’s running under LocalSystem, the format is <domain\computername$>).
   
3. Right-click the account and select Properties.
   
4. In the Login Properties dialog box, in the Select a page pane, select User Mapping.
   
5. In the Users mapped to this login list, in the Map column, select the box that corresponds to the OperationsManagerDW database.
   
6. In the Database role membership for: OperationsManagerDW list, ensure that the following items are selected: configsvc_users, db_datareader, db_datawriter, db_ddladmin, and sdk_users.
   
7. Click OK to save your changes and to close the Login Properties dialog box.
   

cluster type · ms · opsmgr · rms · Scom

The OpsMgr event log of the RMS showed EventID 31567, Failed to deploy reporting component to the SQL Server Reporting Services server.

Solution : http://thoughtsonopsmgr.blogspot.com/2010/09/eventid-31567-failed-to-deploy.html

EventID · rms · Scom · Solution · sql server reporting services