A long time since my last post.
today I read the last post of Marnix and I must say that this is exactly the topics that interest me in our field. As always Marnix presents the subject in his unique way.
“Wow! On my HP Elitebook notebook with an I7 Intel CPU, SSD HD and 16 GBs of RAM I run Windows 8 RTM version with Hyper-V enabled. On the SSD I run all my VMs which – guess what – run some System Center 2012 components like SCOrch and OpsMgr 2012.
On itself it’s already awesome: when I put my notebook into hibernation, the VMs will be set into a saved state, basically meaning when I start my notebook again, the VMs will run from the moment they were paused.
So my VMs are running for more then a few weeks now, without any glitch at all. All the screens which I had opened in all my VMs before hibernating my notebook, are found back in the exact same way after my notebook is on again. Even better, all processes which I started run from where they left off…
And that’s really something very good Microsoft pulled of here. So no more need for any other hyper-visors on my Windows 8 machine! Again, awesome! Respect. This feature on itself is for me enough to migrate ALL my pc’s to Windows 8!”
The WordPress.com stats helper monkeys prepared a 2011 annual report for this blog.
Here’s an excerpt:
The concert hall at the Syndey Opera House holds 2,700 people. This blog was viewed about 17,000 times in 2011. If it were a concert at Sydney Opera House, it would take about 6 sold-out performances for that many people to see it.
As you see I didn’t add any new posts for a long time.
I’ve joined Microsoft services at the beginning of October 2011 and I’m still learning my new position as a consultant.
Hope to add more knowledge about System Center products later on.
Standard Dataset Maintenance troubleshooter for System Center Operations Manager 2007
“Standard Data Set Maintenance is a workflow that runs against the Data Warehouse to aggregate, optimize, and groom data. This workflow runs on the RMS and is triggered every 60 seconds. There is a hard-coded timeout for the workflow and under many circumstances can fail, resulting in 31552 events in the RMS Operations Manager event log.”
I had this problem in several sites before and I needed to gather information from many sources to resolve the issue.
J.C. Hornbeck did a great job as usual.
the following advertising expresses (the competition?! ) the change in thinking in transit to cloud computing.
Is virtual computing is considered to be a cloud? Time will tell, but until then, enjoy …
Microsoft released a KB article that intend to help us deal with best practice and known issues with the new management pack.
“This article is intended to give some best practice guidance along with workarounds to known issues involving the Exchange 2010 Management Pack (MP) running on System Center Operations Manager 2007 (SCOM). Please look through this document before calling for support or posting to the forums as the issue may be covered below. If you find that these issues are particularly troublesome or find additional issues that you want fixed please call into Microsoft Support and raise a Request For Hotfix with the Exchange group.”
For more information :http://support.microsoft.com/kb/2592561#phrss
In the old days when we used Operations Manager 2007 R2 to monitor network device we ware limited to network device availability (online or offline). if we wish to know more, we could used the xSNMP management pack .this MP helped us monitor the availability of ports and interfaces and performance related issues. But xSNMP MP covers only few devices like Cisco, HP ProCurve , Juniper etc. moreover discovery of network devices is limited to SNMP V1 & V2 only. if we wish to monitor SNMP V3 we must use third party applications that extend OM2007 (like JalaSoft).
So what changes have been made to network monitoring in OM2012 ?
- Extended device monitoring
- Multi vendor support and multi protocol support.
- Resource pools
- Server to network dependency
- Dashboards and reporting
Extended Device monitoring
Unlike Operations Manager 2007, Operations Manager 2012 is a game-changer with a new network device monitoring engine. OM2012 extend those capabilities to a large number of vendors and devices (provide port monitoring for devices that implement interface MIB (RFC 2863) and MIB-II (RFC 1213) standards.)
OM2012 provides the ability to discover and monitor network routers and switches, including the network interfaces and ports on those devices and the virtual LAN (VLAN) and Hot Standby Router Protocol (HSRP) groups that they participate in. further more, OM2012 can monitor Firewalls and load balancers.
Multi vendor support and multi protocol support
Microsoft published an Excel spreadsheet that lists the devices, vendors, model names, and versions of network devices that have extended monitoring capability. The Devices worksheet includes processor and memory columns for each device to indicate whether Operations Manager can provide extended monitoring for either or both aspects for each device.
Resource Pool is a feature in OM2012 which gives us the ability to monitor non-windows devices in a high availability mode. The concept behind this feature is that we can select management servers and group them in a pool, and then assign network devices to be monitored by the pool. If a server goes down from that pool, it will automatically failover any monitoring that is occurring on that management server to the other members of the pool.
The network discovery process is a great change compared to SCOM2007, it allows us to discover multiple devices using discovery rules. the discovery deals with different community names just like run as account and allows us to discover sets of devices and individual network devices in the same rule.
There are 2 types of discovery:
Explicit – OM will discover specific network device that was specified in the rule.
Recursive – OM will discover the devices specified as well devices found in the ARP table of those devices.
I preferred explicit rather then recursive discovery, because recursive will discover devices that we don’t need to monitor and as a result, will increase the administrative workload and the management server workload.
Server to network dependency
Server and network dependency is part of the vicinity dashboard, and it’s actually a dynamic map that show us contextual network map. we can choose whether to display computers that connected to the network devices. the map can be scoped to number of hopes from the selected network node.
Dashboards and reporting
Well, how can one explain this ? I thought that a a picture is worth a thousand words…
Useful links :