This weekend I did some migration from MOM 2005 to SCOM 2007 beta 2.

First I tried to install SCOM 2007 on the MOM2005 management server. There was a conflict during setup because of a performance counter issue. That will work in the RTM version. I then installed SCOM 2007 on its own server. MOM 2005 and SCOM 2007 did share SQL server, SQL 2005 SP1.

I exported some common made management packs from MOM 2005, converted them to XML with MP2XML from MOM 2005 resource kit. SCOM 2007 didn’t liked them, there was a issue with the XML file it said.

The next step was to add machines. Auto discovery didn’t find any machines at all, this is a known bug in beta 2. I then installed a agent manually on FASRV02, a machine that already have a MOM 2005 agent. There wasn’t a problem running them on the same machine.

I shut down FASRV02 and received an alert in MOM 2005 and some kind of alert in SCOM 2007, unfortunately there was a problem writing to the database.

I then uninstalled the SCOM 2007 agent from FASRV02 and from FAOP01 that has been running SCOM 2007 before. I also removed the database and cloned a new machines named FAOPSMGR where I installed all parts of SCOM 2007, even the database.

I installed a agent manually on FASRV02 again. FASRV02 now has both the MOM service and the MOM Health service running. I disconnected the network card from FASRV02 and did receive an alert in both MOM 2005 and SCOM 2007, nice! 🙂

I looks like a computer can be monitored with both MOM 2005 and SCOM 2007 at the same time. Almost all problems I run into this weekend is known issues according to Microsoft beta newsgroup.

In place migration from MOM 2005 to SCOM 2007 is not supported in beta 2. It will work in the RTM version. There will be a conflict during installation because a performance counter already exist on the machine if MOM is running there. There for you will need to install beta 2 on its own machine. 

To run Microsoft System Center Ops Mgr 2007 beta 2 you will need .NET Framework. The link in “Microsoft Operations Manager 2007 Help” is unfortunately not working. You will find a working version on Microsoft Update or at this URL http://msdn.microsoft.com/netframework/downloads/updates/default.aspx.

Remember to reboot your server before continue the installation.

Every time I am working with System Center Operations Manager 2007 beta 2 I find more and more new functions. Here are some of them that I found today

When a administrator is about to add new agents he/she will run the discovery wizard. A nice news is that you now is enable to do that with a LDAP question. In these screenshots I have choose to install agent on all machines that is named anything with SRV.

Discovery Wizard 1
Discovery Wizard 2 

When a agent is installed manually there is a new function to get all settings about the management group from Active Directory. This improved failover and also its make is much more easy if you are using a image when installing new machines.

Screenshot from agent installation

I would like to tip you about these Operations Manager 2007 movies from Microsoft.

Installing OpsMgr 2007

Using OpsMgr 2007 Management Packs

Introduction to Agentless Exception Monitoring (AEM)

Introduction to Audit Collection Services (ACS)

I got a question a couple of days ago from my friend Christoffer Andersson:
“Is it possible to remove a management pack from SCOM 2007”?

Operations Manager 2007 also includes the ability to delete a management pack.
Deleting a management pack will remove all management pack objects and discovered data from the database.

source: Operations Manager 2007 Help

There is a large number of operations in SCOM 2007 for example close alerts, run scripts and change rules. All these operations have been group in different profiles.  Every profile correspond to function or service. Below there is a explanation to every default role. A great news is that we finally got that true read-only operator role without multiple management groups.

• Report Operator
  This profile is used to give permissions to reports. SCOM 2007 have integrated SQL Reporting service security into SCOM 2007 security. Only members or the Report Operators role can read reports.
  
• Report Security Administrator
  This profiles is used between SQL Reporting services and SCOM 2007. The IIS application pool that run SQL Reporting Server is using this profile.
  
• Read-Only Operator
  This profile is for persons who should only be enable to read alerts and views. What the persion can see is controlled by scope.
  
• Operator
  This profile is for persons that need access to alerts, views and to be enable to run tasks. This profile is the same as MOM User group in MOM 2005.
  
• Advanced Operator
  This profile is based on the operator profile, but this profile can also change a part of the configuration. Which part of the configuration is controlled by the running scope.
• Author
  This profile is the same as the MOM Author group in MOM 2005. This profiles if for persons who will work with management packs and settings.
• Administrator
  The Administrator profile is the most powerful profile. Administrators can do anything within the system. During the installation you will choose a group who will become SCOM 2007 Administrators. This profile is the same as MOM Administrators in MOM 2005.

Today System Center Operations Manager 2007 beta 2 was released. You can download it at Microsoft Connect. You can find FAQ about SCOM 2007 here I have installed SCOM 2007 in Hyper-V and some commentary is

• Require SQL 2005 with SP1
• During the installation you can choose a security group that will be SCOM administrators. Local administrators is no longer SCOM Administrators
• You can change the name of the database, default name is OperationsManager
• Administrator Console is gone. In SCOM 2007 all operations is done from the same console, Operator Console. What you see and can do is controlled by roles. There is seven roles in SCOM out-of-the box. Administrator is the highest role and read-only operator is the lowest. A read-only operator can only read alerts and look at views in operator console.
• MOM v3 Command Shell, a great way to operate SCOM