OpsMgr 2012 Beta: Topology Simplification

Things that I have taken away from the September 6 Video Conference.

A question I asked, was if the Maintenance Mode will allow for re-occurring scheduling for a system(s). Example a script is ran on a certain day and time each month, can we pre-schedule this in advance? If I get a response I’ll apply to the comments.

• OM 2012 removes the RMS and makes all Management servers as Equals.
• SDK & Configurations Services runs on all management servers
• Console can be use any management server to connect
• Store configuration  data in the database instead of memory
• Faster start up and a smaller demand on local resources.
• Server Pools  distributes the workloads across multiple management servers.

• Some major changes to Maintenance Mode

• A NEW ROLE – RMS Emulator; to help if a dependencies rely on a RMS such as a management pack.
• Never place more than 50% of your Management Servers in maintenance mode at once – do half and wait until they all come out before you do the other half.

- Okay now, got some homework to do

Next Meeting: September 20, 8:00 AM PT Dashboards

OpsMgr 2012 Beta Setup and Upgrade Meeting Notes

Here are some notes & things that I’ve taken from the the OM 2012 Beta Video Conference.

• When upgrading your agents from OpsMgr 2007 R2 to OpsMgr 2012; you’ll be asked if you want to upgrade all your agents if it discovers that there are OpsMgr 2007 R2 Agents out there. You may choose to move forward, but you’ll not get monitoring. You’ll need to update each of these machines.
• SQL permissions for:

 

• If you installed the OM 2012 Beta, you have to upgrade to OM 2012 RC before your can install the OM 2012 RTM. You cannot go straight to the RTM from Beta.
• SKD and Config account needs to be a local administrator on each system.
• You can not change the name of your Management Group

• System Center Operations Manager 2012 Beta Upgrade Process Flow Diagram

Zombie Question #1: Domain GPO Modifications?

 

I want to ask everyone if they had to identify and all modifications that had to make to support SCOM.

What are some recommendations to run SCOM over a domain with the proper permissions, functions and so forth from a domain GPO?

Please leave your comments:

SCOM Zombie PSA#22: A reason 4 Multi-Homed Agents

 

One of my customers gave me a requirement some time ago that they wanted to upgrade their MOM 2005 infrastructure to SCOM 2007 R2. There only requirement was that was provided was that there must be a fail-over system incase there is a site isolation.

So after reviewing their current capabilities and other available resources to support their requirements, the option that was best for their environment was two separate management groups separated by geographic locations.

To keep the systems identical, the duplication of work can be a pain at times. And when the site became isolated due to a hurricane, flooding, power outages and other nature disasters that occurred; monitoring continued.

There you go, nothing complicated, just something to think about when you have to provide continuous monitoring for a customer(s). Just happy customers

HAPPY BIRTHDAY TO ME!!!!

 

BIG 40!!!!!

 

I can see everything from up here. Well I guess it is time to start heading down.

Back from vacation & survived hurricane Irene

The family and I went out of town for the week of vacation one last time before everything goes back to a normal routine. We went to Pigeon Forge, Tennessee, stayed in a log cabin and did a lot of sight seeing. We really had a great time there.

But now I have a lot to catch up on now.

SCOM Zombie PSA#21: SCOM Agent Health “Not Monitored”

 

A while back a zombie pushed a large number of agents out to be installed. Without waiting until the job completed on the first management group, the zombie pushed the agents out to the same systems from another management group.

The end result was some of the systems showed up in one of the management groups as “Healthy”  while the other system either failed to install the agent or it showed up as “Not Monitored”.

Here is what Worked for me:

• Stop and disable the Agent Service (System Center Management). This also worked for some of the agents that I couldn’t successfully deploy a second agent on.
• From the management group with the “Not Monitored” agent I deleted the agent from my Agent Managed or from the Pending Management.
• if you delete the agent before the agent service is stopped/disabled it may reshow back up in the Pending Management. Even if you approve the agent, it will show back up as Not Monitored in the Agent Management.
• Next I rediscovered & redeployed the agent to the system (I did not uninstall the agent).
• My agent successfully installed and now it is properly reporting to multiple management groups with healthy status.

This worked for SCOM 2007 R2 and I bet SCOM 2012 it would resolve the same issue.