| Blake's profileDiscuss IT now - Microso...PhotosBlogLists | Help |
|
|
April 21 MOM 2005: How can I monitor the number of files in a folder and collect the value as performance data?Are you still using MOM 2005? Has anyone approached you with this request? If you did, then I had this same question from our team who manages CA Message Manager. They wanted to be able to get a real count of files in message queue folders, set thresholds on the number of files, age of the files, and create performance data for trending. In the past I was using a old MOM 2000 script from a NetIQ consultant (Ugo Corti) to do this. However, as we progressed more and more towards using MOM 2005 as our one stop shop for monitoring, the CA Message Manager group needed something a bit better. This older script wasn’t going to work as they liked. I imported this script into my MOM 2005 labs and started testing. It worked as expected except for the performance collection portion. Performance objects were being created and collected, but the value was always “0”. I asked Pete about this and he was very helpful in troubleshooting the issues I was having (despite the ribbing I was giving him about this old script). He wanted me to have someone else test the script in there lab to see if the results were the same, so as to rule out my environment. So that brings us to Scott Moss. Scott, like me, still has MOM 2005. Scott, unlike me, happens to actually know Visual Basic along with many other things (like top 10 famous midget wrestling matches, how many licks it takes to get to the center of a tootsie pop, etc). So tonight he was kind enough to give me a hand with this issue and guess what? He fixed it! I could have said I fixed it, but I’d like to say I was his muse to get this script working. Area of the Original Script that needs to be modified:
Once you do this, then the number of old files in the folder that you are monitoring will be logged correctly in your performance view. April 03 MOM 2005: MSFT Windows Server Base OS MP IssueThis article applies to the MOM 2005 Server Base OS MP version: 05.0.3500.0010 (The latest version) Tonight I was ensuring that specific counters were collected for CA Message Manager. We monitor this application and the engineers for it wanted me to add any counters that MOM isn’t currently collecting. After I installed agents I made some views for CA MM. I looked at the performance data views and saw about nine counters. I thought that was odd. So I did some digging and found that in the MSFT Windows Servers Base OS>Windows 2003>Performance RG some of the counters I wanted to collect were there. I scratched my head, because this was a W2K3 server. So I checked the computer groups the RG was bound too. It was bound to W2K3 Virtual Clusters! Sweet! Oh wait, not so sweet. Why this computer group is even in there is beyond me. I thought maybe I got drunk one night and decided to do some tweaking and broke it. However, I checked all my environments and it was the same. I downloaded the MP from the catalog, imported it with the option to OVER WRITE any changes to my MP and sure enough it was still there. What does this mean? That these performance measuring rules are not running against stand alone W2K3 servers. It also means that someone didn’t QA the MP very well. Now I have to go check all the other RG’s to see if there are MORE mistakes. I know not a lot of people are still using MOM 2005, but just imagine if this happens in OM 2007? Sealed MP targeting the wrong server class? How fun would that be to fix. My fix will be to remove the cluster computer group and add the Windows 2003 Server group. Details: Computer Group bound to the performance RG in W2K3 Servers RG: MSFT needs to pull this MP, fix it, and repost it. Otherwise, you need to do the right thing and change it on your own. It’s up to you if you want to leave the cluster computer group in there. I doubt you have to since your nodes are W2K3 servers. August 12 MOM 2005 Agent Pending Uninstall - 21078Today I looked in the MOM 2005 Admin console and checked pending actions. I am used to seeing one computer listed in there from EMEA that isn't registered in DNS correctly. However, today I saw a SharePoint server listed in the pending uninstall.
I rejected the uninstall and ran a computer scan again. It showed up again but I didn't understand why.
So I uninstalled and reinstalled the agent. Then I looked in the management server's application log again and I saw this:
=====
Event Type: Error
Event Source: Microsoft Operations Manager Event Category: None Event ID: 21078 Date: 8/12/2008 Time: 3:51:07 PM User: N/A Computer: XXXXXXMOM03 Description: Computer Discovery Engine failed to contact machine "XXXXXXIISNB". This could be a misspelled computer name or the computer is not contactable. Error Message: "Machine name:XXXXXXIISNB [IP:XXX.XXX.XXX.76], Error: Workstation info failed with Status code : 1792, Error Message: An attempt was made to logon, but the network logon service was not started. " For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
=====
Well how about that. IF I had only looked here first, I could have saved myself a lot of time. I went out to the server in question and sure enough the netlogon service was not running (but set to automatic). I started it, ran a scan again, and the agent was no longer in pending uninstall. July 25 Support for running System Center Operations Manager 2007 Service Pack 1 and System Center Essentials 2007 Service Pack 1 on a Windows Server 2008-based computerReleased today:
For System Center Operations Manager 2007 and System Center Essentials 2007 to support Windows Server 2008-based computers, you must install the following:
Assume that you perform an in-place upgrade to Windows Server 2008 from a Windows Server 2003-based system that support Operations Manager 2007 and Essentials 2007. In this case, you must install the Windows Server 2008 hotfixes immediately after the in-place upgrade. Support for running System Center Operations Manager 2007 Service Pack 1 and System Center Essentials 2007 Service Pack 1 on a Windows Server 2008-based computerReleased today:
For System Center Operations Manager 2007 and System Center Essentials 2007 to support Windows Server 2008-based computers, you must install the following:
Assume that you perform an in-place upgrade to Windows Server 2008 from a Windows Server 2003-based system that support Operations Manager 2007 and Essentials 2007. In this case, you must install the Windows Server 2008 hotfixes immediately after the in-place upgrade. July 16 Loading reporting hierarchy failed - Can't see reportsThe other day I logged onto my management server to run some reports but when I loaded the console and clicked on reporting I got an error: Loading reporting hierarchy failed. I had never had problems before and I wondered what had changed. I thought it might have something to do with my admin id that doesn’t have a proxy id for IE. I talked to my co-worker who shares the environment with me and he said he didn’t have that issue. I had him shadow my session to see just what was happening. Then I decided to check the IE settings (connections>lan settings) for this admin account. I noticed that the box for ‘Automatically detect settings’ and ‘Use automatic configuration script’ were checked and the proxy address was filled out. I unchecked ‘Use automatic configuration script’ and went back to the console. I clicked on the reporting tab and the reports appeared. Not sure why this would affect how the console operates. I hope to get an explanation, but in the meanwhile I know how to get around it. June 25 MPViewer 1.7 ReleasedFinally got around to getting SCOM deployed in our dev lab and have learned a lot. Today I was making some rule changes and over rides and I was looking for my tool kit folder that had the various tools by Borris Yanushpolsky. I couldn't find it so I went to his site and noticed he had released the 1.7 version of his tool. If you don't have this you may want to get it.
MP Viewer 1.7:
He also has another great tool called over ride explorer. A must have for OM 07 Admins.
Override Explorer v3.3:
April 20 MVP Summit 2008Went to the MVP Summit this past week. It was the first one I have been too. It was an interesting experience and there was a lot of good information to absorb. The best thing about the summit was meeting the other MOM MVP's as well as the product team. I would have to say that the experience was very "tight" and worth all the "peer pressure" to attend.
I have added some of the photos taken during the summit. The pictures include both MVP's and product team members. Thanks everyone for making this a pleasant experience! I guess there is a "first time" for everything!
Regards,
Blake
P.S.
I updated many of my lists and soon I hope to post some decent content. February 02 Exchange Management Pack Issues: MOM 2005After recently importing the latest versions of the Exchange 2003 and 2007 Management packs I have found some of the older bugs still exist. I am in the process of documenting these and potential solutions. I understand that MSFT is not putting a lot of time into fixing minor issues with MOM 2005, but I think we deserve them. We will be using MOM 2005 for at least another year. The majority of our monitoring is for Exchange 2003 and 2007. So stay tuned for an update. September 26 Hotfix breaks erformance threshold rule: Rule description blank for MOMOh ya! I had a issue with MOM memory and CPU usage on some of our EVA clusters and other clusters. I did a trace and submitted the logs to MSFT. The trace showed signs of something a hotfix would resolve. I deployed this hotfix. As we rolled new agents out I deployed this hotfix and noticed that all of these agents didn't show a description for performance threshold rules. Working with MSFT we discovered it was the hotfix that broke this. They reproduced it and are working on a fix.
September 13 Exchange 2007 MP and MOM 2005: Topology discovery brokenSince we started monitoring Exchange 2007 in our dog food lab I started having issues on one of my management servers in regards to Exchange Server Discovery. I would get about 400 alerts (suppressed of course) for an issue with the Exchange Topology Discovery. This script runs once daily usually. This script is used to draw the Exchange Diagram. I don't think many people use it, but I do. According to the support engineer the "Bridgehead" class is deleated when you import the E2K7 MP.
He offered the following soutions:
Disable the rule.
Re-import the Exchange 2003 MP.
I am going to disable the rule. I am just happy that he was able to repro the issue. Now, maybe, MSFT will fix it.
***UPDATE***Fix from MSFT:
In SQL – in the classattribute table, there are two rows that had a classattributename of “Bridgehead” which the script is looking for.
In the E2K07 MP – these were renamed to “Hub Transport”
To fix – simply open Enterprise Manager, open the classattribute table, and rename these back on the two rows from “Hub Transport” back to “Bridgehead” (no quotes) This will be corrected in the official Exchange 2007 MP release to support E2K7 SP1. August 15 MOM 2005 Knowledge Base tab and IE 7I guess this is known to most consultants, but IE 7 breaks the MOM KB's and MP descriptions. I told Alliance about this and will log a bug about it. Apparently there is no known fix yet.
So if you have the MOM 2005 ops and admin console on a PC or Server with IE 7, then expect to not be able to view these items. SCOM 2007 - It will have to waitDue to budget issues, it looks like SCOM 07 will have to wait until 08 or 09 (in production). Lab wise, looks like this year and next. Woo Hoo! July 21 HP StorageWorks Management Pack Links (HP EVA)Our SAN group just notified me that there was a 2.1 version for MOM 2005 released.
I searched their site and found the following links:
Not sure, but I think you can use the WEBESListener from the SCOM MP (may be newer - unless they updated both packages).
When we had issues, the HP Support tech told me to install the WEBESListener service that was built for SCOM, so that is what I am running. Oddly enough, the email from our SAN group says the new version is 2.1, but the web site says 2.0. The march to SCOM 2007At work we are finally starting to prepare for SCOM 2007. There are several reasons why we haven't jumped right in with SCOM 2007, but I won't go into the details. Nonetheless in the various test labs we will have sufficient hardware and storage space to handle these small labs and test configurations. In production I have submitted the following hardware requests:
Two management servers
One clustered RMS
Two SQL Clusters for the Reporting and Production DB
One IIS server for the web console
One additional SQL server for log shipping from the Production SQL Cluster
SAN attached storage for the Reporting DB
All hardware will be 64 bit. Most of the servers will have 4 GB of ram, while the SQL boxes will have 8 GB of ram.
Seems a bit much for about 600 agents, but what the hell right?
Another group at work has already deployed SCOM 2007 in one lab and has given me rights to all the boxes. So when I get some free time I will start to poke around.
Our biggest issue is with the policy that allows you to store credentials locally (used to install and uninstall agents from the management server as well as MOM hot fixes). Our corporate security disables this policy. However, I am going to ask them to create another MOM OU that will have this policy enabled so that when I need to install or uninstall agents and hot fixes, we can move the servers to those OU's temporarily, then move them back. May 18 HP releases new MP with fixesThe issue we had with the latest HP MP for EVA Storage was finally tested and released in the newest version of their MP. I am glad they got this fix out to the public for those who are trying to monitor HP EVA SANs with MOM 2005.
Maybe you can get it HERE?
Enjoy.. This thing was killing us since 3/24. April 28 HP Enterprise Storage MP 2.0 (issues and solution)Do you remember the DST patch? Happened around March 23 I think. Our Exchange SAN team was told by HP that they should probably update to the latest version of WEBES (a product that sits on the HP EVA Management Servers and happens to feed MOM with alerts via Desta). Once they did update to the latest version we stopped getting MOM feeds. Instead we were getting scripting issues.
Apparently the WEBES team changed something (probably how it feeds or what it sends via XML to MOM) and didn't tell the people at HP who make the management packs. So the engineer I worked with had me install the WEBES Listener service for SCOM 2007 (not certain that even mattered or not, but we did) on my MOM management server and then he sent me an updated WEBESListenerResponse script that I replaced the existing one in MOM with.
After we did both of these things, we were able to get alerts from EVA into MOM via XML again. Thanks HP.
The engineer said that they would do further testing and then release this version / fix to their site. April 13 HP Storage Management Pack 2.0 for HP EVAUh oh it's magic! NOT. Since March 23, after updating WEBES on our EVA systems we started having issues with alerts that were fed to MOM via XML from Desta. I didn't have time to open a case with HP until a few days ago.
What is the issue? In a nutshell TESTING. My hat is off to HP for going above and beyond to get to the root of the issue and being very honest. Apparently the WEBES engineering team told the group that makes the management pack "nothing changed". Therefore the group that made the HP management pack for their storage solution didn't bother to test it for MOM 2005. They are working on the MP for the next version of MOM, which is good news I suppose (despite not still having an environment for MOM 2005 - maybe they do maybe they don't). What difference does it make. HP has it's own product for monitoring, so for them to extend out to another platform (MOM) I have to give them credit.
I sent them the information about our systems and all the log files and they were able to recreate the issue and are working on a fix. The fix should be available in a week or so.
If you are running the latest version of WEBES and the HP management pack (probably any of them) then you probably have noticed that you are getting scripting issues and irregular alerting on your MOM management server. This is primarily due to both changes in WEBES and the script that HP provided for the response to alerts fed in via XML.
*IF* HP will allow me to post the fix, then I will. If not, then you will just have to wait for them to release it.
As Borat would say "Very Nice! High Five!" March 22 MOM 2005 in the MOVIES!If you want to see MOM 2005 in a movie, then watch Firewall with Harrison Ford. There is a scene where Harrison unintentionally spreads a computer virus via E-mail (at the command of his captor). For some reason Harrison has another monitor on his desk, and as they zoom in on it you can see that it's a MOM 2005 ops console with a diagram view displayed. Dell is all over this movie, but I guess MSFT paid to have their monitoring tool plugged as well. Kudos MSFT for getting a MOM cameo! I wonder if Harrison Ford is a MOM MVP! Sometimes I wish I could use the force to deploy agents and solve MOM issues. In the end I just go into a wookie rage and destroy my cube. March 09 John Hann MOM MVPGot to meet John in person last week. Put some pics up for your viewing pleasure. |
|
|