MS System Center Operations Manager 2012 database move notes

So, it’s been a while since I previously updated my blog.

I currently work with VMware and SCOM products and I wasn’t able to find some information on SCOM 2012, there are a lot of articles regarding SCOM 2007 and most of them works for 2012 version, BUT in case you are moving SQL databases from host to host (for scalability improvements that was first thing I did when after installing SCOM on a single server I realized that performance is ugly) there are some differences and additional steps. So, I wanted to share some notes, there are a lot of guides on how to move Operation Manager databases, you Google them. However, there are the following important things to consider:

- You do not need to backup secure storage encryption key

- There is a stand-alone configuration file for Management Configuration Service (C:\Program Files\System Center Operations Manager 2012\Server\ConfigService.xml) which should be altered after database has been migrated. Just change database server name and database name if necessary. You might need to stop the Management Configuration Service first. Then restart the service and it should connect successfully to a new database.

That’s it. There are some issues with .Net app monitoring service, so I might need to check where it store its configuration, but maybe its configuration will be updated after a while automatically.

While using SCOM I also discovered some other interesting task – monitoring of a remote machine which is outside of the domain you are monitoring (happens a lot in case of a lab). In this case a certification-enabled communication should be used, which requires some configuration steps. maybe I’ll write my next post about this.

UPDATE:

To fix issues with .Net app monitoring, you should also alter settings in the MT_Microsoft$SystemCenter$OpsMgrDB$AppMonitoring table of the Operations Manager DB