Windows Server Operating System Management Pack for Operations Manager 2007
http://www.microsoft.com/download/en/details.aspx?id=9296
The Windows Server Operating System management pack consists of the following five management packs: Microsoft Windows Server Library, Microsoft Windows Server 2008 Discovery, Microsoft Windows Server 2008 Monitoring, Microsoft Windows Server 2003, and Microsoft Windows 2000 Server. The Microsoft Windows Server management packs monitor the performance, health, and availability of Windows Server 2008, 2008 R2, 2003, 2003 R2 and Windows 2000 Server. By detecting, alerting on, and automatically responding to critical events and performance indicators, these management packs reduce resolution times for issues and increase the overall availability and performance of your systems running the Windows Server operating systems, thereby helping to reduce the total cost of ownership.Feature Summary
Setting Up the Operations Manager SharePoint Web Part
20 April 2012: Updated with notes on configuration with SSL.
Why would you want to do this?
General Prerequisites
Installing the Web Part
Setting up a Target Application in the SharePoint Secure Store (Optional)
Setting up the Web Part Environment
The PowerShell method
The UI method
Adding the Web Part to a Page
Configuring the Web Part on a Page
Final Result
Maintaining Security
The Operations Manager Web Part allows you to host dashboards on your SharePoint site. Unlike the web console, these dashboards are “look, but don’t touch”. You can view info, but not navigate elsewhere or run tasks. This is really good for giving people outside of the operations team a look at some operations data. You also don’t need to add all the users of the dashboard to an Operations Manager Role. Instead you can add the groups you want to give access to the dashboard to SharePoint and have them all share a single Operations Manager account and connection.
There are a lot of steps here, but this is a one-time thing. Once its setup, it’s easy to maintain and add new dashboards. Technet describes how to do this, but it’s missing roles, motivations, and pictures so here ya go.
You’ll need to setup Operations Manager 2012 with its Web Console installed. You need a SharePoint 2010 site on a different machine. SharePoint is not supported on the same machine as the Web Console as they both want port 80 and anyway it would be slow as tar. You’ll also want some dashboard you want to share. I’m just going to use a built in one as an example.
Role: For this step you must be the SharePoint admin. This step requires running a power shell script to install the Operations Manager SharePoint project on your site(s).
Prerequisites: you’ll need the Operations Manager 2012 installation media.
On the Operations Manager installation media, look under Setup\Amd64\SharePoint. It’s easiest to copy that directory to your SharePoint Server.
On the SharePoint Server, open the SharePoint 2010 Management Shell.
Change to the SharePoint directory you just copied and run install-OperationsManager-DashboardViewer.ps1
You’ll be prompted for two things: the directory the Operations Manager project is in (which is the full path to your current directory) and the sites you want to install the project on (hit Enter for all). In my example above I just entered D:\SharePoint and hit Enter.
This script adds the project and deploys it to all sites. If you add a site later you may have to rerun this. The directory also contains a script to uninstall the project. That script removes the code from SharePoint, but it leaves 2 temp files in a cache that .Net maintains. If you want to reinstall or upgrade, run the install script and follow it’s instructions to get rid of the temp files.
Notes on configuration with SSL-enabled Operations Manager web console:
Reason: You’ll need to do this if the SharePoint server is in a different domain from the Web Console or if you want to use a single shared credential in Operations Manager for all your dashboard users.
Role: The first part of this step is setup by the SharePoint admin. You need to setup a Target Application in the Secure Store.
Prerequisites: You’ll need
1) The email of the contact for the operations team for your management group.
2) The Operations Manager Admin to give you an account in the read-only role of you management group for use in reading the dashboards.
3) Any windows group(s) that you want to grant permission to look at the dashboard.
Note: the Secure Store feature requires the Standard or Enterprise SharePoint 2010. You can’t get this feature with SharePoint Foundation.
To find the Secure Store, open the SharePoint Central Administration site and navigation to Application Management/Secure Store Service/Secure Store Service (see pics).
If you haven’t already, you’ll need to generate an encryption key for the store. Just press Generate New Key and fill in a pass phrase.
On the same ribbon hit New to create the Target Application. Give it an easy name, fill in a contact email, and choose the Group type. Group type allows anyone in the included groups to access your dashboard. It’s easier to maintain than individual accounts.
The next page configures the field names for the credential you use to connect to OM. Don’t fill in your user name or password. You really don’t need to change anything here and it will just be confusing if you do. Just hit Next.
The Application Administrators are the people who can give users and groups access to the dashboard. The Members are the users and groups who can connect to SharePoint and access the dashboard. Fill in the accounts you want for these.
Now that you’ve created the Target Application ID, you’re not quite done. You need to set username and password it’s going to use to connect to OM. Select the checkbox for the application and hit Set.
Now fill in the user name and password of the account that SharePoint will use to talk to the Operations Manager SDK. This account needs to have at least read-only access in the Operations Manager Management group.
Reason: You need to setup a connection to Operations Manager that can be used by any number of web pages in SharePoint. This connection info is stored in a SharePoint list on the Admin site.
Role: This step must be done by the SharePoint admin.
Prerequisites: the Operations Manager Web Console must be installed and you’ll need its URL. If you are using a secure store key then you’ll need access to or a copy of the web.config file for the Operations Manager Web Console.
The web.config file is normally under Program Files\System Center Operations Manager 2012\WebConsole\WebHost on the web console machine.
There are 2 ways to setup the web part environment. The first is to use the UI. The second is to use a provided PowerShell script. The script is a little easier and can be automated so let’s start with that.
In the same PowerShell window you were using above run the script below with parameters.
add-OperationsManager-WebConsole-Environment.ps1
- title “the name of the connection dashboard users will see. A config group is good.”
-webconsoleUNC “The path to the web.config file, not including the filename”. This is only needed if you use a secure store credential.
- targetApplicationID “optional: the ID you created above if you are using the secure store”
From the start menu, open the SharePoint Central Administration site and choose Site Actions\View All Site Content.
Click on the Operations Manager Web Console Environments list.
Now create a new list item for your management group. The only entries you need to add are the title and Host URI.
If you are using a secure store, you’ll need the OverrideTicketEncryptionKey and the value for its validation algorithm from the Web.Config as well as the TargetApplicationID. Make sure you get the correct IDs (there’s a comment in the web.config point to the correct keys (which are the 2nd set, not the first)
Below is an example without the target id. Note the HostError timeout, which defaults to 15 seconds. If your Web Console and SharePoint servers are not on the same clock time. If they differ by more than 15 seconds, the connection to the Dashboard will fail. It’s best to sync the times, but you can also increase this timeout if you have to. The greater the timeout, the greater the window that is open for a spoofing attack, so it’s best not to make it too large.
Role: This can be done by any SharePoint author.
Prerequisites: the web part must be installed.
In IE, navigate to the main SharePoint site. Do NOT use the Admin site, the web part is not trusted for use on the Admin site (there’s really no need). Select Site Pages\Add a New Page. Fill in a name for the page and create it.
In this example, I insert the dashboard at the top of the page by going straight to Insert\Web Part\Microsoft System Center\Operations Manager Dashboard Viewer as in the picture below.
Prerequisites: An Operations Manager web console server must be setup and the environment for it must be setup on the SharePoint Admin site. You need the URL of the dashboard that comes from the Operations Manager web console.
To get your dashboard URL, point a tab of IE at your web console (http://myOMWebConsole/operationsmanager) and navigate to your dashboard. Now copy the URL from the address bar in IE.
Back in SharePoint, select the Web Part\Edit Web Part as below.
In the web part properties, select the environment and filling the full URL.
Optionally, you can choose to change the title of the dashboard and you can choose to have a direct link to the web console added, however that link doesn’t use the secure store. It’s just a normal link, so it won’t work if the Web Console is behind a firewall or if your user account doesn’t have permissions in OM.
Note that once you hit Apply or OK, the URL will be truncated to a URI that only includes the address after the # sign. This is expected as the connection info part of the environment list item.
Remember to Save your page! If you navigate away now it’s lost.
Some companies have a policy to periodically change the encryption keys used on secure connections.
Use the PowerShell script update-OperationsManager-WebConsole-Environment.ps1 to update the Override ticket keys same as you created them above.
Most companies would expect to change the password on the account that accesses the Operations Manager Server periodically. Change this password in one place by setting the password in the secure store (see above).
As you’ve likely seen or heard, System Center Operations Manager 2012 contains significant enhancements in the ability to display data through the use of its new dashboard technologies. This post is the first in a series of dashboard-related posts introducing these new abilities.
Why did we decide to invest in Dashboards?
Tenants of dashboards
There are several key tenants of the dashboard investments that are important to realize.
Examples of the same dashboard in 3 experiences:
Creating a new dashboard
Before we get into the steps of creating a new dashboard, let’s go over a bit of terminology. A dashboard has a particular layout, which specifies the arrangement of the cells that actually host content. The layout could be fixed grid layout, for example one cell on the top and one on the bottom, a two-by-two grid of four cells, etc. It can also be a column layout where the user specifies the number of columns and cells are added dynamically as needed.
The content is displayed within the dashboards using widgets. A widget is basically a combination of a user interface control (e.g. a grid or chart) and a data provider (which defines what data to retrieve). Examples of these widgets in current builds include a widget to show the health state of a collection of managed objects, a widget to list alerts and a widget to show a chart of performance data. When the user adds a widget to a dashboard, the new widget instance also gets the configuration specified by the user.
Let’s see how this actually all works…
Specify the dashboard layout
Note: I’m going to show all of this happening in the Operations Console. You can do all the same dashboard creation and manipulation in the web console too!
Step 1: This looks a lot like Operations Manager 2007 R2 – same place the user goes to create dashboards:
Step 2: this opens the New Dashboard and Widget Wizard, where the first step is to select the dashboard layout:
Step 3: having selected grid layout, let’s try a 3 cell arrangement, and after this we confirm that this is what we want and click “Create” on the next page of the wizard.
When completed, the new dashboard will look like this. Each of the dashboard cell has a link in it which the user can click to add a new widget:
Adding widgets to the new dashboard
Step 1: click on the “Click to add widget…” link in a dashboard cell. This will open the New Dashboard and Widget Wizard.
Step 2: Now you will see the widgets available. Let’s try the state widget.
Step 3: After giving the new widget a name, select the objects to display:
and then
Step 4: Specify the criteria (e.g. which health states to show) and the columns to show, and you have a fully defined widget:
Repeating this again with the Performance Chart and Alert widget, we quickly get a fully configured dashboard:
Manipulating Dashboards and Widgets after creation
After a dashboard is created, you can still adjust the dashboard to meet your needs. For each widget you’ll these options:
Clearing the content will remove the widget so you can replace it with a new widget.
“Swap with next widget” and “Swap with previous widget” will allow you to reorganize the locations of widgets on a page:
Finally, Configure and Personalize allows the widget to be configured differently (which affects all users) and personalized (e.g. display preferences such as columns, column order, sorting and grouping) by each user.
Stay tuned…
I hope this is helpful getting you started on your exploration of System Center Operations Manager 2012 dashboards!
Keep watching the Operations Manager Team Blog for more information about these our out-of-the-box dashboards, how partners will ship their dashboards, the new widgets and for more details on using SharePoint with Operations Manager dashboards!
Thanks!
Congratulations to our 2 SCOM 2012 Beta Survey Sweepstakes winners:
Vedran Matica and Silvio Di Benedetto
They each won an XBox 360 and Kinect!
Thank-you to everyone that completed surveys, your feedback will help us deliver a better product for RTM and in the future!
If you know Dan Rogers from the Operations Manager forums and industry events in the OM space, you'll want to subscribe to his new blog here:
http://blogs.msdn.com/b/manageability_aint_easy/
On Tuesday, October 4th Technical Evangelists Symon Perriman and Rick Claus are hosting an online conference on Virtualization Career Training with Microsoft Learning. This half day virtual event (8am – 11am PST) will offer a Level 100 to 200 introduction for anyone who wants to learn more about Microsoft Virtualization and how it can help their career. It is free and public so sign up for this warm-up for the Jump Start event on October 6th.
Learn More: http://mctreadiness.com/MicrosoftCareerConferenceRegistration.aspx?pid=270 Register: http://mctreadiness.com/MicrosoftCareerConferenceRegistration.aspx?pid=288
Instructor Bios: http://mctreadiness.com/MicrosoftCareerConferenceRegistration.aspx?pid=287
On Thursday October 6th Technical Evangelist Symon Perriman and Technical Instructor Philip Helsel will host an online 8-hour deep dive training event for the Microsoft 70-659 Technical Specialist exam, Windows Server 2008 R2, Server Virtualization. This virtual event runs from 8am to 5pm PST and will include presentations, demos and live Q&A with the attendees. It costs $99 to attend, but includes a free exam voucher worth $150! It is public so sign up for some great training to help improve your career here: http://mctreadiness.com/MicrosoftCareerConferenceRegistration.aspx?pid=272. Register early to make the most of a weekly virtualization coaching newsletter!
Module 3 focuses on System Center Operations Manager and how it can monitor the virtualization environment. Learn more about VMM integration, virtualization monitoring needs, Performance & Resource Optimization (PRO), PRO-Tips, triggering live migrations, managing OpsMgr in a virtual environment and more!
Technologies that we will cover include: Windows Server 2008 R2, Hyper-V, System Center Virtual Machine Manager (VMM), System Center Operations Manager (OpsMgr), System Center Data Protection Manager (DPM), Windows Server Backup, Failover Clustering, Remote Desktop Services, Active Directory, Microsoft Assessment & Planning Toolkit (MAP), Virtual Machine Servicing Tool (VMST), Windows Server Update Services (WSUS) & more!
Learn More: http://mctreadiness.com/MicrosoftCareerConferenceRegistration.aspx?pid=274
Register: http://mctreadiness.com/MicrosoftCareerConferenceRegistration.aspx?pid=272
Exam Information: http://www.microsoft.com/learning/en/us/Exam.aspx?ID=70-659
Thanks!Symon PerrimanTechnical EvangelistPrivate Cloud TechnologiesMicrosoft
See videos on TechNet
Follow announcements @SymonPerriman
In our documentation for authoring Operations Manager management packs, we regularly reference the Management Pack Development Kit, mainly the Module Type Reference that includes reference documentation for the modules that are included in the standard Operations Manager 2007 R2 libraries. Once you know how to build a custom discovery, monitor, or rule in a management pack, then your next question is often what modules are available to provide the various logic that you need. Of course, when you find such a module you need to know how it works. While we had most of the modules documented for some time though, there were some critical modules that were not included.
http://blogs.technet.com/b/mpauthor/archive/2011/09/21/new-module-documentation.aspx
There are many questions on which components of network devices are monitored for System Center network monitoring. This post will hopefully clear up some of those questions as the post will cover what gets monitored and the conditions where the monitoring will apply. What components of the network device are monitored depends on three things:
Devices will be discovered differently depending on the manufacturer, model, and device system Object Identifier (OID). For example a Cisco Catalyst 3560 will be discovered with interfaces, processors, memory, fans, power supplies and temperature sensors. But a Cisco 2950 will only get interfaces, processors, and memory even though the device may have other components like fans, power supplies and temperature sensors. Other devices may only discover the interfaces on the device and no peripheral components will be discovered. The best way to determine what is discovered is to open the diagram view on a network node. Below you can see the memory (MEM), Processor (PSR), and ports discovered in the diagram view.
Interfaces are not all discovered equally. Interfaces that have implemented the interface MIB (RFC 2863) and MIB-II (RFC 1213) standards can have more monitoring available than other devices. This can include OperStatus, AdminStatus and performance counters like percent utilization and error packets. Devices that don’t implemented these MIBs may only have the existence of the interface discovered, or the OperStatus may depend on a vender specific MIB. To figure out if a particular interface is monitoring the standard interfaces you can open the health explorer on an interface from the diagram view of the device.
Port 1 is able to be monitored using the standard MIBs. Under the rollup monitor “Interface Status” you can see monitors for AdminStatus and OperStatus are present. Under the Performance monitor you can see the High Discard rollup monitor contains specific monitors to check the health of input and output rates the port is processing. However, in the picture you can see that even though the interface can be monitored using the standard MIBs in this case no monitoring is enabled.
Interface 30 on the device is an example of an interface where performance counters will not be collected or monitored. The interface is monitored only through AdminStatus and OperStatus as seen by the two monitors for status under the Interface Status aggregate monitor. Looking under the High Discard Percentage aggregate monitor you can see the High Input Rate Discard monitor is missing compared to Port1 above indicating performance counters won’t be collected.
Processor and memory can be monitored out of the box on devices where components are discovered. http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26831 has information on which devices will have processor and memory monitored. Other peripherals like fans, power, cards, and temperature will not get monitoring out of the box when discovered. Through the Authoring Pane in the Operations Manager console SNMP based rules and monitors can be created to monitor these components.
Rather than monitoring every interface out of the box only those interfaces that were discovered as connected are monitored. This is done to avoid noisy alerts on interfaces that are not connected, and to avoid excess monitoring on interfaces that won’t return a valid performance counter. This means the default state for an interface is to have all the monitoring disabled. For those interfaces that are known to be connected monitoring will be enabled. Interfaces you want to monitor the monitoring can also be enabled. Interfaces are only monitored if they are a member of one of three groups in Operations Manager. All three groups enable all the standard interface workflows assuming the standard MIBs were supported. These groups will also enable any vender specific workflows for the interface.
Relay Network Adapters Group
This group contains interfaces that are connecting two devices. When a full discovery is run containing both the devices, then the interfaces linking the two devices are added to this group and monitoring will become enabled.
Managed Computer Network Adapters Group
An agent computer that is directly connected to a device will have the connecting interface added to this group. For this to work the management group must have the Windows Operating System management pack for the agent’s operating system, the Windows Client Network Discovery management pack and the Windows Server Network Discovery management pack. The full discovery of the agent’s operating system has to be completed including the discovery of the agent’s network adapters. Then when network discovery runs for the device it should stitch the port on the device to the network adapter on the computer and add the port to this group.
Critical Network Adapters Group
This group can be updated through the Operations Manager console under authoring. You can add any of the interfaces to this group and the monitoring will be enabled. If the interface connected to your web server isn’t monitored then adding the interface to this group will give you alerts on problems with the interface connected to the web server.
Advanced Network Adapters Group
There is also a fourth group which behaves a little differently than the other three groups mentioned. This group turns on some extra advanced workflows for interfaces that won’t be enabled by the other groups. These workflows are disabled out of the box because they are they are often a duplication of performance counters already collected. These are advanced performance counters like Cisco Collision packets which are already reported as part error packets in the monitoring by the other three groups. If you want visibility into a particular performance metric than adding the interface to this group is one way to get that extra data.
When trying to figure out whether your Network monitoring is working correctly ask these questions to see what monitoring is taking effect.
Did Discovery Work?
Before any monitoring starts the discovery of the device needs to be completed successfully. The network monitoring has very similar dependencies to the discovery methods as both are SNMP based. Be sure in the discovery rule you specified the device should be monitored via SNMP Only or SNMP and ICMP. A future blog post should cover trouble shooting the network discovery.
What was Discovered?
The next thing to check is what was discovered on the network device. Use the Diagram view of the network device in the console to see what components of the device were discovered. Use the health explorer on the interfaces to see if performance counter and status monitoring is available or not. If your device is not getting components discovered and not getting performance counters monitoring than likely the device doesn’t support the standard MIBs.
Interface Monitoring Enabled?
Check to see if the interface you want to be monitored is a member of one of the network monitoring groups. You can view this in the Authoring pane of the console under groups.
Network Monitoring Management Pool Availability
When the Network Discovery rule was created a management pool was specified to use to monitor the devices. By default this will be the All Management Servers pool, but using a specific pool for Network Monitoring servers is advised. If the Network Device is behind a firewall or remote, then using a specific pool will be necessary. Check the Discovery rules in the Administration Pane of the Console to see which management pool should be monitoring the devices. Then check the Resource Pools in the Administration Pane to be sure the management server resource pool only contains servers that can contact the network device. It might be necessary to create multiple network discovery rules and management server resource pools to be sure your network monitoring is being fired from the correct locations.
11013 Event - SNMP Get Timeout
When the SNMP workflows timeout because a reply from the device was not received in time the Health Service will log 11013 events to the Operations Manager Log. With the out of the box workflows, Operations Manager will retry to the SNMP query on the nextinterval. There is a monitor in Operations Manager to detect these events.
Log Name: Operations Manager
Source: Health Service Modules
Event ID: 11013
SNMP GET request to IP Address 10.11.64.25 has timed out. This can be due to the device being offline or to the workflow using incorrect credentials.
Possible Resolutions:
11009 Event – SNMP Get failure
When a network device is queried for a particular value it might not be present. Then the Health Service will log an 11009 event in the Operations Manager log. The workflows that were using this value will be unloaded.
Event ID: 11009
Error in SNMP GET response from IP Address: 10.11.64.68, Status: noSuchInstance(129).
One or more workflows were affected by this.
OID: .1.3.6.1.2.1.10.7.2.1.2.268
Workflow name: System.NetworkManagement.MIB2_dot3.NetworkAdapter.InputPacketErrorPct
Instance name: PORT- 268
Possible Resolutions
Disclaimer
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included utilities are subject to the terms specified at http://www.microsoft.com/info/copyright.htm.
For the Operations Manager 2012 release, we have made some big changes in the setup and upgrade areas to make the deployment experience more simple, intuitive, and easy to use. In this post, I’m going to go through some of the major changes in the deployment experiences to help you better prepare for OM 2012.
Operations Manager 2012 Setup
If you are familiar with previous versions of Operations Manager, you are likely familiar with the MSI installer-based setup process. One of the biggest changes we have made is to abstract out the MSI installers into a single setup experience, launched via setup.exe. Most components can be installed directly through this setup experience, without having to use MSI installers. By launching setup.exe, you get the bootstrapper screen:
From the screen, you can use the “Install” link to launch install for components such as the management server, operations console, reporting, and web console. Additionally, the bootstrapper allows you to launch the MSI installers for agent, gateway server, ACS, and ACS for Unix/Linux.
Let’s walk through some of the screens within the setup experience.
On this screen, we can select the components to install in setup, as well as view descriptions of the different components. You will notice on this list that the operational database and data warehouse database are not explicitly listed out. This is because both of these operational database and data warehouse are now installed by default when installing the first management server in a management group. The operational database has always been a mandatory component in a management group; a new change in 2012 is that the data warehouse is also mandatory. This is done in order to enable key scenarios, such as dashboards, out of box for all users even if they have a very simple all-in-one management group.
Another big change from prior releases is that in 2012, the prerequisite checker is integrated right into the setup experience. Additionally, right within the setup wizard, resolutions are provided to resolve prereqs to help you resolve potential problems much more easily.
Lastly, this screen, which shows if you are installing a management server, asks whether you are creating the first management server in a management group, or adding management servers to an existing management group. The first option implies that you are creating a new management group, and you will be asked to provide the necessary information to create an operational database and a data warehouse for this management group. If you go with the second option, it implies that you already have a management group, and you are adding an additional management server to it. As you know from a prior post on Topology Changes in 2012, adding a second management server to a management group is all you need in order to enable high availability of the SDK and Configuration services in OM 2012.
Agent Configuration Changes
Aside from the setup experience, another place where we have made major changes for 2012 is agent configuration. In the past, one of the biggest problems has been that there is no easy way to determine which management groups an agent reports to, as well as no easy or automatable way to change (add/remove) management groups that an agent reported to without going into Add/Remove Programs. The first part of the Agent Configuration changes is the Agent Control Panel applet, available in the Control Panel under “Operations Manager Agent”.
The applet lists all management groups that the agent belongs to, and provides the ability to add and remove management groups.
If you are interested in automating the process of adding or removing management groups from an agent, we have also added the Agent API that allows you to write scripts that can automate the agent configuration process. The Agent API is documented, along with samples on how to use it within scripts; for more information on how to use the Agent Configuration Library, please refer to http://msdn.microsoft.com/en-us/library/hh328987.aspx.
R2 --> 2012 Upgrade
NOTE: OM 2007 R2 --> OM 2012 Beta Upgrade is NOT supported; please do not try out this upgrade in production environments.
The upgrade procedure from OM 2007 R2 to OM 2012 is design with the mentality of leaving no management group behind; no matter what your R2 management group looks like, there is an upgrade path to bring it forward to OM 2012 without losing your data.
While the specific steps you will use to upgrade will depend on what your management group looks like, the high-level steps for upgrading your management group are the same in all cases:
1. Bring your secondary management servers and gateway servers up to (OM 2012) supported configuration. If needed, move your agents so that they report to servers of supported configuration.
2. Upgrade manually installed agent to OM 2012.
3. Upgrade secondary management servers to OM 2012.
4. Upgrade gateway servers to OM 2012.
5. Upgrade push-installed agents to OM2012.
6. If the RMS meets supported configuration, run upgrade from RMS, which will upgrade the RMS to an OM 2012 management server, upgrade your database, and upgrade your data warehouse (or add one if one doesn’t exist).
7. If the RMS does not meet supported configuration, run upgrade from an OM 2012 management server, which will upgrade your database, and upgrade your data warehouse (or add one if one doesn’t exist), and remove the RS from the management group.
8. Upgrade Reporting server, console, web console, ACS.
The upgrade process can be complicated at times, particularly if your environment is complex and distributed, so the best place to start is with the upgrade flow diagrams available now. A sample is shown below, and the rest of the flow diagrams are available at http://technet.microsoft.com/en-us/systemcenter/om/hh204730.aspx.
One additional point to call out in the OM 2007 R2 à OM 2012 upgrade process is the Upgrade Helper MP. This MP is designed to help you walk through the upgrade process by giving you, via monitors and health states that you are already used to, whether your management servers, gateway servers, and agents (both Windows and XPlat) are upgraded.
Relevant Links
Be sure to check out the OM 2012 Beta deployment guide, available now at http://technet.microsoft.com/en-us/library/hh278852.aspx. Also, check out the new supported configurations document for 2012, available at http://technet.microsoft.com/en-us/library/hh205990.aspx. Use the documents to help you get ready for upgrading at release time by making sure that you get your OM 2007 R2 management group up to supported hardware and operating system/service pack requirements as needed; this will help to ensure that your final upgrade goes much more smoothly. Also, for clean installs, use these documents to plan out what you will need for your 2012 management group, being sure to account for having at least 2 management servers to ensure that you have high availability.
I hope this post helps get you ready for building out or upgrading your environments. Stay tuned for the next post in our series about the Operations Manager 2012 Topology, which will cover resource pools.
Thanks,
Nishtha