locked
SCOM 1801 to 2019 UR1 upgrade RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    We have two SCOM versions , 1801 and 2012 R2. SCOM 1801 - used for windows 2008 and above , and SCOM 2012 r2 for windows 2000/2003.

    Red hat linux version 4,5,6,7 - SCOM 1801.

    Now , we are planning to upgrade to 2019 UR1. And planning to move Windows 2008 severs to SCOM 2012 r2. Also Linux version 4,5,6.

    What would be best possible steps to follow.


    Tuesday, May 19, 2020 5:18 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    1. Install SCOM 2012 r2 agent on existing SCOM 1801 agents on windows 2008 and linux 4,5,6 servers?

    You won't be able to install an older version of an agent on top of a newer one, so you'll need to uninstall the SCOM 1801 agents and then install the SCOM 2012 R2 agents. SCOM 2012 R2 can coexist with SCOM 1801 so the agents should work with SCOM 2012 R2.

    2. Both version of SCOM (1801 and 2012 r2) agent can exist in these servers?

    You cannot have two different versions of agents installed.

    3. Can we push SCOM 2012 r2 agent from Operations console to these servers?

    You can either use the SCOM 1801 agents, or uninstalled the SCOM 1801 agents and then push the agents SCOM 2012 R2 agents from SCOM 2012 R2.

    4. After SCOM 2012 r2 agents are installed , we can remove them from SCOM 1801? or we uninstall it?

    Yes just remove them, no need to uninstall.

    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by Madhavi_Sekar Thursday, May 21, 2020 1:27 PM
    Wednesday, May 20, 2020 10:31 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    You have two upgrade options for your SCOM 1801 environment:

    1. In-place upgrade

    Perform an in-place upgrade of your current SCOM 1801 to 2019, this is the easy way, you keep all historical data and very little configurations are needed.

    2. Side-by-side migration

    The preferred method is always to clean install, this would be installing a SCOM 2019 environment on the side and migrate everything from SCOM 1801 to SCOM 2019.

    -----------------------------------------------------------------------------------------------------------

    In your case it also depends what Windows Server & SQL Server version your SCOM 1801 environment is currently running on.

    If your SCOM 1801 is currently running on Windows Server 2016 or later, and using SQL Server 2016, you can perform an in-place upgrade, however I would not recommend an in-place upgrade if you have performed an in-place upgrade previously to SCOM 1801.

    If you are running on a Windows Server 2012 R2, then you would also require to perform an in-place upgrade of your Windows Server, this adds another big step to your planning, and it also involves more risk, in this case I would recommend performing a side-by-side migration.

    I have written a step-by-step guide on how to upgrade to SCOM 2019:
    SCOM 2019 Step-By-Step: Upgrading

    SCOM 1801 supports co-existence with SCOM 2019, so by doing a side-by-side migration it would involve no downtime, but it would require more configuration work, but it also gives you a chance to redo things properly if your SCOM 1801 environment has bad configurations.

    Best regards,
    Leon

    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, May 19, 2020 5:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

     Thank you.

     As we have SCOM 1801 on windows server 2012 r2. Then will plan for side-by-side migration.

     So in this case , we are planning to move Windows 2008 servers, LInux version 4,5,6 to SCOM 2012 R2, as they are not supported in SCOM 2019.

     1. Install SCOM 2012 r2 agent on existing SCOM 1801 agents on windows 2008 and linux 4,5,6 servers?

     2. Both version of SCOM (1801 and 2012 r2) agent can exist in these servers?

     3. Can we push SCOM 2012 r2 agent from Operations console to these servers?

     4. After SCOM 2012 r2 agents are installed , we can remove them from SCOM 1801? or we uninstall it ?.

    Regards

    Madhavi

     

     

    Wednesday, May 20, 2020 10:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    1. Install SCOM 2012 r2 agent on existing SCOM 1801 agents on windows 2008 and linux 4,5,6 servers?

    You won't be able to install an older version of an agent on top of a newer one, so you'll need to uninstall the SCOM 1801 agents and then install the SCOM 2012 R2 agents. SCOM 2012 R2 can coexist with SCOM 1801 so the agents should work with SCOM 2012 R2.

    2. Both version of SCOM (1801 and 2012 r2) agent can exist in these servers?

    You cannot have two different versions of agents installed.

    3. Can we push SCOM 2012 r2 agent from Operations console to these servers?

    You can either use the SCOM 1801 agents, or uninstalled the SCOM 1801 agents and then push the agents SCOM 2012 R2 agents from SCOM 2012 R2.

    4. After SCOM 2012 r2 agents are installed , we can remove them from SCOM 1801? or we uninstall it?

    Yes just remove them, no need to uninstall.

    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by Madhavi_Sekar Thursday, May 21, 2020 1:27 PM
    Wednesday, May 20, 2020 10:31 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

     Thanks a lot Leon Laude

     Just one last question

    When you say "SCOM 2012 R2 can coexist with SCOM 1801 so the agents should work with SCOM 2012 R2".

    -- We just have to add the SCOM 2012 r2 management group on SCOM 1801 agent installed 2008 servers.

     Does this work for Linux also ?

    Regards

    Madhavi

    Wednesday, May 20, 2020 10:55 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Linux agents can only report to one management group, multihoming is not officially supported.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, May 20, 2020 10:57 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

     Ok. Thanks a lot. This really helps. :)

    Wednesday, May 20, 2020 11:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Linux agents can only report to one management group, multihoming is not officially supported.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Even though it's not officially supported, it works fine and it's not much of a challenge. Read here : http://www.systemcentercentral.com/can-a-crossplat-unixlinux-agent-be-multihomed-in-opsmgr-scom-sysctr/ 
    Wednesday, May 20, 2020 11:57 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

     Thanks , we will be mutlihoming the linux SCOM agents till SCOM 2019 is all setup.

     After migrating to SCOM 2019 , will removing agents from SCOM 1801. As we donot want any downtime for any of the agents.

     Regards

    Madhavi

    Wednesday, May 20, 2020 12:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All

    We have come up with plan to add additional management servers with Windows server 2016, to existing SCOM 1801 and move all agents to these MS . Once agents are moved , we will upgrade to SCOM 2019. Will this work ?

    Regards

    Madhavi

    Friday, May 22, 2020 4:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Should work yes.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, May 22, 2020 4:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you. Regards Madhavi
    Friday, May 22, 2020 5:04 PM