none
split single server into multiple servers SCOM 2007r2

    Question

  • I have a single server scenario, all roles and SQL are on the same box. We need to separate out the roles across at least two servers and re-purpose the original server as a sql server. My thought process on this was to spin up a couple of vm's and make them management servers, then using the guide promote one of the new management servers to root management server. 

    At that point I *should* be able to uninstall SCOM from the original box, leaving my newly prompted RMS and a lone MS in my group. Does that sound about right?

    Then finally I would like to rename the original scom box to something else, I've not gotten far enough in my searching to see what needs to change for that.

    If I'm missing something or am horribly misinformed, please let me know.

    Thanks!


    Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.com

    Thursday, January 17, 2013 8:29 PM

Answers

  • Hi Jeffrey

    You'll see these technet links on how to move each component:

    http://technet.microsoft.com/en-us/library/hh456421.aspx

    For the SQL components, Kevin Holman provides the best real-world guides:

    http://blogs.technet.com/b/kevinholman/archive/2010/08/26/moving-the-operations-database-my-experience.aspx

    http://blogs.technet.com/b/kevinholman/archive/2010/08/25/moving-the-data-warehouse-database-and-reporting-server-to-new-hardware-my-experience.aspx

    You are correct in your initial post about moving the Management Servers.

    Cheers

    Graham


    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

    Saturday, January 19, 2013 7:27 AM
    Moderator

All replies

  • Just going to add this link to the thread so I don't lose it. Very nice article with a couple of different walk through's.

    http://scomskills.com/blog/?p=59


    Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.com

    Thursday, January 17, 2013 9:09 PM
  • This looks like what is needed in order to rename the old server.

    http://technet.microsoft.com/en-us/library/cc540368.aspx


    Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.com

    Thursday, January 17, 2013 9:30 PM
  • A listing of all the SCOM SPN's you should see.

    http://scomskills.com/blog/?p=105


    Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.com

    Thursday, January 17, 2013 10:07 PM
  • Hi Jeffrey

    You'll see these technet links on how to move each component:

    http://technet.microsoft.com/en-us/library/hh456421.aspx

    For the SQL components, Kevin Holman provides the best real-world guides:

    http://blogs.technet.com/b/kevinholman/archive/2010/08/26/moving-the-operations-database-my-experience.aspx

    http://blogs.technet.com/b/kevinholman/archive/2010/08/25/moving-the-data-warehouse-database-and-reporting-server-to-new-hardware-my-experience.aspx

    You are correct in your initial post about moving the Management Servers.

    Cheers

    Graham


    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

    Saturday, January 19, 2013 7:27 AM
    Moderator
  • Thanks Graham I had found a couple of those already, and I had meant to post back up to this the other day. I had promoted a newly created MS to RMS and i used the option to delete the old one, but it apparently sticks around for a while? I had stopped the services on the old server, but when i would open the console all agents were gray. this was around 5p so i went home and when i came back in the morning all agents were green. when i looked at the times of when the alerts were generated and such it appears that the agents were in fact reporting to the new RMS but for whatever reason i was getting data from the old one. This was after specifying the new server name under tools and connection on the console.

    anyway that step is done and i'm going to backup all the sql databases then either reload that box and re-install everything, or just uninstall the scom bits and rename it. i have read keith's stuff before and it's very good, i don't think i've read the two you linked in yet.

    questions i have at the moment are, if i do reload eveything i assume i'll need a new spn (no biggie) but if i want to spin this up as an instance instead of using MSSQLSERVER i assume there are places that will need to be updated as well?


    Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.com

    Saturday, January 19, 2013 1:39 PM

  • questions i have at the moment are, if i do reload eveything i assume i'll need a new spn (no biggie) but if i want to spin this up as an instance instead of using MSSQLSERVER i assume there are places that will need to be updated as well?

    question answered in step 7 :)

    "In step 7, I edit the registry of each RMS\MS server, with my new server\instance name.  (SQLDB1\I01"


    Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.com

    Saturday, January 19, 2013 1:43 PM