Home » 2006 (Page 5)
Yearly Archives: 2006
Idea around Group Management with Service Manager and Orchestrator
Validate your runbook design - part IIMaintenance Mode Tools and Strategies
I have written a article about for momresources.org about maintenance mode. The article takes up how maintenance mode work, why it sometimes don’t work, tools, script and GUI.
KB Article 922332
Article 922332: How to move Microsoft Operations Manager 2005 Reporting together with the MOM Reporting database to a different computer.
Article 9223322 is about moving the SystemCenterReporting database to a new machine. In general that KB is enough, but I would like to add some information.
During step 1 you should write down all permissions that you have in your reporting console. Also document all extra SQL permissions that you have setup, for example permissions to dev department. Step 1 describe how you should use RptUtil.exe to export reports. SQL 2005 is require higher XML security so most of your SQL 2000 reports will not work in SQL 2005. There is a KB about this KB919598 too. If you don’t get reports to work with the latest MP version you can call Microsoft Product Support Services and ask them to send you latest report version.
During step 4 you are told to install MOM 2005 reporting on the target machine. To make sure MOM 2005 don’t think the old machine still is the reporting server you can run the following query in the OnePoint database “SELECT * FROM reportingsettings”. If MOM 2005 thinks there is two reporting servers you will get problems when importing reports. They will be imported but never show up in reporting console.
Be sure that you export your custom made reports during step 1, you can import them in reporting console after step 8.
Don’t forget to write down all subscriptions too. If you use subscriptions you will have to setup SMTP again.
Configuring a Report Server for E-Mail Delivery
When you try to import a Microsoft Operations Manager 2005 report file, the import process fails
Prerequisite Check Failed
Prerequisite Check Failed
When you are installating MOM 2005 Reporting Services on SQL 2005 SP1 the default settings will presumably not work. When you get to “SQL Server Reporting Services Server” there is a checkbox named “Automatically detect virtual directories”. If that box is enabled you will get the above error. Uncheck that box and fill in the input boxes with the default values, and it will work.
- Report Server Virtual Directory: ReportServer
- Report Manager Virtual Directory: Reports
Event, Alert and Performance parameters
Article ID 885725 contains all event, alert and performance parameters. Its a very good source when setting up advanced criteria.
An alert that is generated by using managed code displays the property text name instead of the event information in Microsoft Operations Manager 2005
http://support.microsoft.com/?id=885725
Side-by-Side Migrering part 2
To import a management pack from MOM 2005 to SCOM 2007 you can do like this
- Export the management pack from MOM 2005 with Administrator Console
- Convert the AKM file to XML with MP2XML, from MOM 2005 resource kit
- Convert the XML file to SCOM 2007Â XML format with the MPConvert tool that is included in the SCOM 2007 software package
- Import the XML file into SCOM 2007 with Operator Console
Side-by-Side Migrering part 1
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.
The setup was interrupted before System Center Operations Manager 2007 could be installed
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.Â
The .NET Framework is required to install this application.
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.
Setup cannot locate the MOM database
“Setup cannot locate the MOM database” can come up when you install MOM management server and the database is on another server that is just installed. The cause is that the management server cant connect to the database server.
Workaround:
- Open “SQL Server Configuration Manager” on your SQL server
- Expand “SQL Server 2005 network configuration”
- Click “Protocols for MSSQLSERVER”
- Duble click TCP/IP
- Change Enabled No to Enabled Yes, then click Ok
- Restart the MSSQLSERVER service under “SQL Server 2005 Services”
What happens to mailflow during maintenance mode?
What happens to mailflow during maintenance mode?
There is a function in Exchange MP that test mailflow between mailservers. A friend asked me what happens to those test if one mail server is in maintenance mode?
I have two mail servers, MX01 and MX02. I run the wizard and setup mailflow test between them. After a while I start receive notifications every 10 minute that MX02 has sent a e-mail and MX01 received it.
I put MX01 into maintenance mode and waits 5 minutes to make sure that the maintenance mode flag has been changed in the OnePoint database, then I shut down MX01.
During the time when MX01 is in maintenance mode there still is events that MX02 has sent e-mails and all local test is ok. There is no alerts.
30 minutes later when MX01 returns from maintenance mode I received two alerts about missing heartbeat, that is normal because the server is still down.
10 minutes later I start MX01 again, all normal events under events in operator console. Mailflow events start coming back again, both that MX02 sends and MX01 receives. 10 minutes later this error is generated from MX01
Computer: MX01
Description:
Specified delivery latency of mail flow messages exceeded. Detailed information:
Delivery latency from MX02 (at Fri Jul 28 12:19:01 UTC+0200 2006) = 2926 (seconds)
Delivery latency from MX02 (at Fri Jul 28 12:49:00 UTC+0200 2006) = 1127 (seconds)
Delivery latency from MX02 (at Fri Jul 28 12:34:00 UTC+0200 2006) = 2027 (seconds)
Delivery latency from MX02 (at Fri Jul 28 13:04:00 UTC+0200 2006) = 227 (seconds)
This event was generated by the script: "Exchange 2003 - Mail flow receiver"
2000 seconds is around 30 minutes, the same as the maintenance mode. Â
Summary: There is no alert generated when one of the mail servers is in maintenance mode. Â At least not the first 30 minutes.
Recent Comments