none
SCOM 1801 to 1807 RRS feed

  • Question

  • Hi All,

    I am creating one test environment of scom 1807 . 

    First installed SCOM 1801 on windows 2106 with SQL 2016. 

    Getting error while upgrading patch manually. 

    

    Thursday, February 7, 2019 5:23 PM

Answers

  • Hi,

    The KB4090987 is part of the Update Rollup 5 for System Center Operations Manager 2016 which is a Long-Term Servicing Channel (LTSC) release. 

    SCOM 1801 and SCOM 1807 are Semi-Annual Channel (SAC) releases and don't have Update Rollups.

    This is why you are receiving an error that it "the upgrade patch may update a different version of the program".


    You can update from SCOM 1801 to SCOM 1807 directly by downloading the SCOM 1807 setup files from here:

    https://www.catalog.update.microsoft.com/Search.aspx?q=4133779

    Some useful links:

    How to upgrade to Operations Manager version 1807
    https://docs.microsoft.com/en-us/system-center/scom/upgrade-1801-to-1807?view=sc-om-1807


    Overview of System Center release options

    https://docs.microsoft.com/en-us/system-center/ltsc-and-sac-overview


    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, February 7, 2019 7:59 PM
  • Hi,

    As Leon stated, we can follow the steps in the articles to perform the upgrade. Some notes during the upgrade:
    1, the .msp must be run with evaluated privilege. We can open a command prompt (run as Administrator) and run the .msp file. See below example screenshot
    2, the upgrade process must be in a fixed order: management server, acs, web console, gateway, operations console, report server, apply the SQL scripts, import the management packs. If a server contains more than one role, also follow the order. If the role is not available, just skip.
    3, after the server is upgraded, the agents will appear in Administration, Device Management, Pending Management, we may choose them, right-click, choose "Approve"



    Hope the above information helps.

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Friday, February 8, 2019 7:08 AM

All replies

  • Hi,

    The KB4090987 is part of the Update Rollup 5 for System Center Operations Manager 2016 which is a Long-Term Servicing Channel (LTSC) release. 

    SCOM 1801 and SCOM 1807 are Semi-Annual Channel (SAC) releases and don't have Update Rollups.

    This is why you are receiving an error that it "the upgrade patch may update a different version of the program".


    You can update from SCOM 1801 to SCOM 1807 directly by downloading the SCOM 1807 setup files from here:

    https://www.catalog.update.microsoft.com/Search.aspx?q=4133779

    Some useful links:

    How to upgrade to Operations Manager version 1807
    https://docs.microsoft.com/en-us/system-center/scom/upgrade-1801-to-1807?view=sc-om-1807


    Overview of System Center release options

    https://docs.microsoft.com/en-us/system-center/ltsc-and-sac-overview


    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, February 7, 2019 7:59 PM
  • Hi,

    As Leon stated, we can follow the steps in the articles to perform the upgrade. Some notes during the upgrade:
    1, the .msp must be run with evaluated privilege. We can open a command prompt (run as Administrator) and run the .msp file. See below example screenshot
    2, the upgrade process must be in a fixed order: management server, acs, web console, gateway, operations console, report server, apply the SQL scripts, import the management packs. If a server contains more than one role, also follow the order. If the role is not available, just skip.
    3, after the server is upgraded, the agents will appear in Administration, Device Management, Pending Management, we may choose them, right-click, choose "Approve"



    Hope the above information helps.

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Friday, February 8, 2019 7:08 AM
  • Do you know why the link to catalog is not working?

    https://www.catalog.update.microsoft.com/Search.aspx?q=4133779

    Monday, February 11, 2019 10:29 AM
  • It appears that the update is currently unavailable from the Microsoft Update Catalog, I guess it's temporary, maybe check back later to see if it's back.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, February 11, 2019 10:38 AM
  • The SCOM 1807 update is once again available at: https://www.catalog.update.microsoft.com/Search.aspx?q=4133779

    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, February 13, 2019 8:02 AM
  • yeah, thanks a lot for an update!

    Best regards,

    Dmitry

    Wednesday, February 13, 2019 8:05 AM
  • Hi Vin,

    May we know the current status of the problem? Is there any other assistance we can provide?

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Thursday, February 14, 2019 7:13 AM
  • Hi Alex , 

    Thanks for sharing but still i am facing issue.

    I have installed all the roles in single server along with SQL . 

    as you suggested i have downloaded the kb4133779-amd64-enu-server_919cb3900ee96f0e9ed2864f57a617acd9297d9b.cab from the https://www.catalog.update.microsoft.com/Search.aspx?q=4133779.

    I open a command prompt (run as Administrator) and run the .msp file as shown below.  Suddenly screen disappears while installing . 

    

    Please suggest 

    Not able to find any useful info in event logs. 
    • Edited by It's Vin Thursday, February 14, 2019 1:29 PM
    Thursday, February 14, 2019 1:28 PM
  • It disappears automatically because it most likely finished the installation (it goes pretty quick).

    Open the console and check your installed version under About.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, February 14, 2019 1:30 PM
  • I took files from WSUS, installed without any issues (in manual install I had same issue described in first post).
    Thursday, February 14, 2019 1:53 PM