Thoughts on the operation manager 2012 migration or upgrade… I'll try to put here all what we need to check before launching a migration to the new OpsMgr 2012.
What about supported configuration :
- How to manage Windows 2000 servers – no more supported in OpsMgr 2012 ?
o If you have money, you can try to keep a small infrastructure with a management group in OpsMgr2007R2. Waiting the replacement of all old 2000 servers.
o You can also decide to use the agentless monitoring but you will only have a limited monitoring… Better than nothing but this can scare applications owner.
- All SCOM 2007 R2 agent must have at least CU4, or later cumulative Update applied to be migrated in SCOM 2012 agent.
o If not, you ‘ll have to update your agents before the migration.
- Check your management servers configuration – all servers that have an OpsMgr Role must be Windows 2008 R2 or later
- Check the SQL version on servers that are used for Operations Manager DB and Data Warehouse – SQL version must be SQL Server 2008 SP2 or SQL Server 2008 R2 RTM/SP
- .Net Framework 3.5.1 role must be installed.
- SCOM 2012 Windows-Based Agent has some pre-requisite too :
o File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
o Operating Systems: Windows Server 2003 SP2, Windows 2008 Server, Windows Server 2008 SP2, Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows Server 2012, Windows XP Professional x64 Edition SP2, Windows XP Professional SP3, or Windows Vista SP2, or Windows 7, POSReady, Windows XP Embedded Standard, orWindows XP Embedded Enterprise, or Windows XP Embedded POSReady, Windows 7 Professional for Embedded Systems, orWindows 7 Ultimate for Embedded Systems.
o Processor Architectures: x64, x86, or IA64.
o Windows Installer version: at least Windows Installer 3.1.
o Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required for the Operations Manager agent.
o Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell version 3.0.
Note |
Windows PowerShell is required for agents that will be monitored by a management pack that uses PowerShell scripts. |
You can also read more on supported configuration on this page Supported Configurations: System Center 2012 - Operations Manager and this other one Supported Configurations: System Center 2012 SP1 - Operations Manager.
What about your management packs :
- In order to have an up-to-date inventory, check all installed management packs you have in your OpsMgr2007 R2 environment.
o You can also check for provided MP updates that could be usefull to install in the new OpsMgr 2012 environment.
- A needed task is now to check what Rules, Monitors, Tasks or Discoveries, also Management Packs that target the RMS :
o You can use a report or a SQL query, both provided by Jean-Sebastien Duchene. This will help you to identify MPs that store a monitoring that target the RMS.
§ Next step is to activate the RMS Emulator for provided MPs that target the RMS (Microsoft Exchange Server 2010 Management Pack, Citrix EdgeSight Management Pack...)
§ For your own developed MP, you can rewrite the MP to target any MS instead of RMS if possible. Tao Yang has created a post on a way to modify your PowerShell script to automatically connect the RMS in OpsMgr 2007 R2 and connect the first MS that respond in OpsMgr 2012.
- Next step is to identify what MP is using PowerShell – All Cmdlets has been renamed in SCOM 2012 by adding a prefix SCOM. You can find the System Center 2012 - Operations Manager Cmdlet Reference.
§ Jean-Sebastion Duchene has worked on a SQL query to help us to identify what MP is using PowerShell.
§ The next step will be to re-write your scripts with the new cmdlets !
§ Load The OpsMgr 2007 Snap-in that are already installed with OpsMgr 2012. Here is post from Scott Moss that speak about that.
/!\ Please do the same work for all your PowerShell script also. Don’t forget a task in your planning to identify all your scripts.
What about your own reports :
- Please find this post from Peter Zerger this is quite old but give the OpsMgr 2012 Database Schemas & Operations Manager DW DB. It seems that some view like RelationshipGenericView does not contain the same columns than in OpsMgr 2007 DB.
This posting is provided "AS IS" with no warranties.
No comments:
Post a Comment