The Product Team is currently working on Operations Manager Service Pack 2. What do you think? What would you like to see personally in Service Pack 2? Please comment
Saturday, June 14, 2008
Subscribe to:
Post Comments (Atom)
skip to main |
skip to sidebar
NiCE Management Pack for SCOM
In a world of true chaos and 4am emergency wake-up calls, comes an answer to my sleepless nights. Discovering Microsoft Operations Management Server was a blessing. The eye bags have minimised, my eyes are visible and i can think straight. This is my personal experience with the MOM server and I hope that it may help someone, somewhere.... somehow.
SCOM Management Packs
NiCE Management Pack for SCOM
Search This Blog
The Don
- Raymond Chou
- Raymond is a Microsoft Most Valuable Professional in System Center Operations Manager and System Center Essentials. He has been working in the Management space since 2001 and have vast experience with the Microsoft System Center family. He is also an MCT and regularly speaks at Partner Trainings, Tech Ed and TechNet events. He is also the first in Malaysia and the first batch in the world to be certified as a MCTS: Operations Manager 2007 and MCTS: Configuration Manager 2007
View Stats
Visits
Me Twitts
Blog Roll
- System Center Forum
- Cameron Fuller's Blog
- Anders Bengtsson Blog Site
- Andy Dominey's MOM Blog
- Maarten Goet's Techlog
- John Hann - The SC Guru
- Rory McCaw's Blog Site
- Pete Zerger Management Blog
- Marcus Oh's Organic Fertilizers
- Justin Incarnato
- Blake Mengotto - Discuss IT Now
- MOM Resources
- My IT Forum
- MOM Community
- Andrzej's IT Thoughts
- Daniel Lai - The Management Solution
- MOM Product Team Blog
- Stefan Stranger's Weblog
- Power Shell your way to System Center
- The System Center Connector
My Rants
- books (1)
- capacity planner (1)
- cloud (1)
- community (1)
- connectivity (1)
- connectors (1)
- cross platform (2)
- gadgets (2)
- gateway (1)
- hotfix (1)
- intel (1)
- interop (1)
- Intune (2)
- linux (1)
- management pack (7)
- mms (2)
- mom2005 (2)
- non-windows (1)
- opalis (2)
- opsmgr (20)
- opsmgr design (2)
- opsmgr R2 (2)
- partner solutions (1)
- reinstall (1)
- reporting (1)
- sccm (3)
- sccp (1)
- scom (13)
- scsm (1)
- service pack (1)
- softgrid (2)
- sp1 (2)
- tech ed sea (4)
- troubleshooting opsmgr (1)
- unix (1)
- utilities (1)
- vmm (1)
- vpro (1)
- Windows 8 (1)
7 comments:
Great post, i have some suggestions:
- Faster console. SP1 helped, but it's still slow. I can live with it, but it gives my colleagues who are not as familiar with the system as me, the perception that the product does not perform properly.
- Custom initial resolution states on alerts (like we could in MoM2005). This is critical to us because it would enable us to, for example, filter specific alerts directly to our 2nd Level or Monitoring department instead of our Service Desk who monitors our systems 24/7.
- Better Group Population. If you have a group containing 400 explicit Windows Computer objects and add 1 the whole group has to repopulate. This makes adding computers to groups very slow.
- Better documentation and implementation of baselining. We feel that the feature was hyped when SCOM2007 was first introduced but it's been pretty silent ever since.
i'm sure i have some more. I'll add them later if i remember :-)
Make it so that alerts created by monitors that are auto resolved can't be closed manually.
I am more about the quality than the quantity. One BIG WISH:
-Ability to EASILY create reports which use dynamically updating computer groups for the chart series members.
Compare to MOM2005:
-Create a computer group that updates dynamically
-Create a monthly report about processor usage using the computer group
-Then you have a report with a chart that has SEPARATE series for each of the computers in the dynamically updating computer group
So I can accept that it's logical in SCOM at the moment that you have the average of all of the computers cpu time in the computer group, but come on! This is still so basic stuff that it has to be built-in!
Second minor update (ofcourse more than one ;) could be the possibilty to use some sort of queue when creating alerts if you forward the alerts to another system, so if you have big problem in your network you wouldn't kill the next system with the alert rush. Also useful if you use somekind of commandlines that are fired upon alerts -> if you have 10 per second limit when firing notifications, then the alerts would build a queue and launch the notifications from the queue with the maximum rate.
Looking forward for the SP2!
-Tero
There are a few things I would like in future releases.
1. A process monitoring MP.
2. The ability to create alert views with delays (like notifications).
3. A decent MP development tool. Something thing like Visual Studio for MP creation.
1. Fixing of a message about agent proxying.
2. Fixing an error in set-maintenancemode command with time zones.
3. More simple reports targeting system.
4. More extended web console.
5. Fixing an error of e-mail alerts. When the alert closed soon after opening (< 30 sec.) comes only messagage about closing of alert (without message about opening).
Definitely improved reporting. Seems like I have to spend a WHOLE lot of time trying to get basic reports to produce the information I want. The templates should be more idiot proof as I am apparently pushing the idiot boundary with reporting.
NetBIOS name ... we still use pagers for alerts and using NetBIOS as computer name is short and direct. Also to use NetBIOS name in customizing alerts.
Post a Comment