Kevin, Thank you for this information. I have moved to Windows OS 2008 R2 and SQL 2008. I have to remove the last MS server, but it is the AD agent server, which has all the machines on it. Can I just shut it down and the agents will failover to the new MS? Also, do I have to run MomADadmin to point to the new RMS?
Sincerely, Greg Lumpkin IT Specialist Windows Projects Support Team OESAE/DESEI/EWIB/WPST [email protected]<mailto:[email protected]> Desk Phone: 410 966-7820 From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Holman Sent: Thursday, March 13, 2014 3:52 PM To: [email protected] Subject: [msmom] RE: SCOM 2012 and SCOM 2007 You cannot move directly from SCOM 2007 R2 on WS 2003 and SQL 2005 to Windows Server 2012 and SQL 2012. Aint happening. Our upgrade documentation covers this. You should perform a side-by-side migration. The amount of work it will take to "upgrade" from your current management group would be a nightmare. To add insult to injury - SQL 2012 is NOT supported for SCOM 2007. If you moved a SCOM 2007 DB over to a SQL 2012 server, that is not supported by Microsoft: http://technet.microsoft.com/en-us/library/bb309428.aspx Here is an upgrade "path" that you'd have to take to move 3 SCOM versions up: -------------------------- Update SCOM 2007 R2 to CU7, infrastructure and agents Move SQL databases from SQL 2005/WS2003 to SQL2008R2SP1/WS2008R2SP1 Move SCOM Reporting from SQL 2005/WS2003 to SQL2008R2SP1/WS2008R2SP1 Decommission old SQL server Install two new Management servers with WS2008R2SP1. Move RMS to one of the new management servers Ensure all roles are moved, such as Web Console, any special functions or services, such as Exchange 2010 MP correlation engine, etc. Decommission both WS2003 management servers. You are NOW at an OS and SQL version that supports an upgrade to SCOM 2012. Upgrade management group to SCOM 2012, infrastructure and all agents. Apply SCOM 2012 UR4, infrastructure and all agents. Upgrade management group to SCOM 2012 SP1, infrastructure and all agents. Apply SCOM 2012 SP1 UR4, infrastructure and all agents. Upgrade management group to SCOM 2012 R2, infrastructure and all agents. Apply SCOM 2012 R2 UR1, infrastructure only. Now, you can start moving things to SQL 2012/WS2012. Move SQL database Move SCOM reporting Install two new management servers on WS2012 Ensure all roles are moved, such as RMSe, Web Console, any special functions or services, such as Exchange 2010 MP correlation engine, etc. Decommission both WS2008R2SP1 management servers. --------------------------- Can you spell nightmare? Or, you just deploy SQL 2012, and two management servers, such as: http://blogs.technet.com/b/kevinholman/archive/2013/10/18/opsmgr-2012-r2-quickstart-deployment-guide.aspx Then multi-home your agents, and move MP's over that you really need/want, and shut down SCOM 2007. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Lumpkin, Gregory Contractor Sent: Thursday, March 13, 2014 1:03 PM To: '[email protected]' Subject: [msmom] SCOM 2012 and SCOM 2007 We currently have SCOM 2007 R2. The RMS is on a Windows 2003, MS is also on Windows 2003 and SQL is 2005 on a Windows 2003. I have 3 Windows 2012 servers. I installed SQL 2012 and was able to move the database. I know want to install SCOM 2012, but it can't see the operational manager database. Can you tell me what my options ours? Sincerely, Greg Lumpkin IT Specialist Windows Projects Support Team OESAE/DESEI/EWIB/WPST
