Embed Size (px)
Citation preview
Lessons from the field:
Migrating to System
Center 2012 Operations Manager
Cameron Fuller Principal Consultant
@CFullerMVP
Agenda
What’s new in OpsMgr 2012? Why Migrate?
What’s new in OpsMgr 2012 SP1?
Integration of System Center 2012
Migration Options and Lessons Learned
Touring OpsMgr 2012 SP1
What’s new in OpsMgr 2012?
• Network Monitoring
• APM (.NET, J2E)
• Architectural changes (RMS out, Pools in), RMSe
• Integrated Dashboards
The Highlights
What’s new in OpsMgr 2012 SP1? (Beta)
• APM Extended: – Windows Services based on .NET
– Automatic Discovery of ASP.NET MVC3 and MVC4 Applications
– New Transaction Types: MVC Pages and WCF Methods
– APM for SharePoint 2010!
• Integration with Team Foundation Server 2010 and Team Foundation Server 2012
• Conversion of Application Performance Monitoring events to IntelliTrace format
• Management Packs and Support for Windows Server 2012 and IIS 8
• Support for SQL 2012
The Highlights (Page 1)
What’s new in OpsMgr 2012 SP1? (Beta)
• 360 .NET Application Monitoring Dashboards
• ACS support for Dynamic Access Control
• Additional UNIX and Linux Monitoring Capabilities:
– Support for CentOS, Debian, and Ubuntu Linux
• Improved Heartbeat Monitoring
• Multi-step web availability monitoring
• [See http://technet.microsoft.com/en-us/library/jj656650.aspx for details]
The Highlights (Page 2)
What’s new in OpsMgr 2012 SP1? (Beta)
Global Service Monitoring
- Pre-SP1 displayed
- With SP1 using Microsoft datacenters through Azure
The Highlights (Page 3)
Integration: A key to System Center moving forward
• Microsoft is selling System Center as one product with multiple components so integration is key
• Integration next steps are occurring
• With SP1 more consistency in supported Operating Systems, SQL platforms and more.
Integration Example:
• Patching and Maintenance Mode
• Monitoring and alerting for ConfigMgr issues
• Deployment of OpsMgr Agents
• Deployment of OpsMgr Consoles
Configuration Manager & Operations Manager
Integration Example:
• Service Manager now effectively sits in the center of the components of System Center
• Now integrating CI’s from OM like: – Databases
– Network Devices
– Even Vmware hosts
Service Manager & Operations Manager
Configuration Manager CI’s
Operations Manager Alerts
Operations Manager CI’s
Active Directory
Orchestrator
Virtual Machine Manager
Exchange
And more… like Savision Live Maps
What to do before migrating?
• Backup and document your environment (including RMS key)
• Perform a Health Check of your OpsMgr installation
• Compare management packs for SCOM2007 and SCOM2012 to identify any critical risks
– Important items to consider: • xSNMP and any other MP’s which used the original SNMP
functionality in OpsMgr 2007 R2
• Backward compatibility required MP’s
• (http://technet.microsoft.com/en-us/library/hh205980.aspx)
(AKA – I wish I had thought about… Page 1)
What to do before migrating?
• Identify other critical considerations – for upgrade migration
– Clustered RMS
– Verify OpsMgr DB at least 50% free space
– Manual upgrade agents, remove agents reporting to RMS
– Remove Exchange 2010 correlation service
– Disable any connectors during upgrade
– Disable Notification Subscriptions during upgrade
– Improve Upgrade performance by running FREEPROCCACHE SQL statement
– Remove the BizTalk Management pack, before upgrade due to long name requirement
(AKA – I wish I had thought about… Page 2)
Living in Operations Manager 2012
• RMS gone, but RMSe lives
• Pools – All Management Servers Resource Pool (automatic): removal of MS
from this is somewhat problematic
– Notifications Resource Pool (automatic): every MS in this pool needs to be able to provide the notifications!
– AD Assignment Resource Pool (automatic)
– Dedicated pools for Unix/Linux
– Dedicated pools for Network
• Change AV exclusions due to new path to OpsMgr files
• Install Veeam collectors on Management Servers for best performance
Lessons learned
Migration Options and Lessons Learned Been there, done that, got the t-shirt
Operations Manager 2012
• Fresh installation
• Existing Installation: Upgrade
• Existing Installation: Multi-Homed
Deployment Paths
Migration Options and Lessons Learned
• Nuisance alerts about agent overhead from OpsMgr 2007 R2 environments in a multi-home configuration
• Run As Administrator when installing
• Install OpsMgr 2012 databases with default size, update after installation
• Multi-homed migrations and moving MP’s – a server isn’t a server, it’s a guid
– an override isn’t targeted at a server but at the guid
Migration Lessons Learned (Page 1)
Migration Options and Lessons Learned
• Utilizing the Upgrade Helper Management Pack to help with upgrade path
• Post Upgrade: clean up the Localizedtext and
Publishmessage table
• AD Integration rules: – Disable AD Integration during migration – to avoid multi-
home back to 2007 MG, re-create
Migration Lessons Learned (Page 2)
Deployment Path – Fresh Installation New Environments: Fresh installation • Requires Windows 2008 R2 (64
bit) • SQL 2008 SP2 and above • .NET 4.0 • SQL Full Text Search • SQL Server Agent Service –
Automatic • Report Viewer Redistributable
2010 • SQL Collation:
SQL_Latin1_General_CP1_CI_AS Positives:
Clean Installation – starting fresh Negatives:
Starting from scratch
Deployment Path – In-Place Upgrade Existing Environments: In-Place Upgrade – same requirements as a fresh installation Positives: • Preserves existing OpsMgr environment
(R2 CU4+) • Can upgrade from OpsMgr 2012 Beta – RC
– RTM Agent requirements:
Server 2000 Support using Agentless Monitoring Server 2003 SP2 and above excluding Server 2008 SP1
Negatives: • Most complicated migration option • Does not provide co-existence – downtime
will occur during the migration
Deployment Path – Multi-Homed Migration
Positives: • Minimizes impact
on current monitoring
• Phases the migration
Negatives: • Increased overhead
of two monitoring products during the transition
• Longer transition potentially
Operations Manager 2012 Migration
Silect: MP Studio • Backup of SCOM 2007 MPs for use when moving to SCOM 2012
• MP and override MP configuration reports to all your stakeholders
• Compare test results across versions to determine if your SCOM 2012 MPs are performing the same (or better) than in 2007
• Create an audit history to see recent changes
• Identify any changes/additions/deletions as part of your migration to SCOM 2012
Vendor tools?
Operations Manager 2012 Migration
Catapult Systems • System Center 2012 Partner of the year!
• Performed over 10 production and proof of concept System Center 2012 deployments (before RTM release) for clients in the Retail, Medical, Education, Software Development, Energy, Transportation, Construction and shipping industries - more than any other partner in the U.S.
Catapult Systems & Savision • Partnered with Savision who provides essential add-ons for
System Center
Vendor assistance?
Must-have OpsMgr tools
Catapult & Savision LiveMaps
Must-have OpsMgr tools
Savision LiveMaps: BingMaps
Must-have OpsMgr tools: Vital Signs
Operations Manager 2012 Migration
• Known issues when upgrading from OM 2007 R2 to OM 2012 http://blogs.technet.com/b/mihai/archive/2012/05/23/know-issues-when-upgrading-from-om-2007-r2-to-om-2012.aspx
• Nuisance alerts during upgrade: http://blogs.catapultsystems.com/cfuller/archive/2012/07/19/tuning-to-consider-when-multihome-migrating-opsmgr-2007-and-2012-environments-scom-sysctr.aspx
• TechNet Live videos:
– http://technet.microsoft.com/en-us/video/prepare-yourself-to-move-to-scom-2012.aspx
– http://technet.microsoft.com/en-us/video/should-i-upgrade-to-scom-2012
• FREEPROCCACHE SQL statement (http://technet.microsoft.com/en-us/library/hh205980.aspx)
• Remove Exchange 2010 correlation service (http://technet.microsoft.com/en-us/library/hh205984.aspx)
• Clean up the Localizedtext and Publishmessage table http://technet.microsoft.com/en-us/library/hh241300.aspx
Reference Links
Q & A
