%3CLINGO-SUB%20id%3D%22lingo-sub-1532815%22%20slang%3D%22en-US%22%3EInstallation%20of%20SCOM%20Reporting%202019%20after%20UR1%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1532815%22%20slang%3D%22en-US%22%3E%3CP%3ELately%2C%20we%20have%20observed%20a%20strange%20issue%20with%20users%20unable%20to%20install%20SCOM%20reporting%202019%20when%20Update%20Rollup%201%20is%20installed%20in%20the%20environment.%20Below%20are%20the%20steps%20to%20successfully%20install%20the%20component.%20Please%20make%20sure%20that%20you%20are%20using%20the%20correct%20Build%20numbers%20of%20Update%20Rollup.%20They%20are%20available%20at%20%3CA%20title%3D%22System%20Center%20-%20Operations%20Manager%20build%20versions%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsystem-center%2Fscom%2Frelease-build-versions%3Fview%3Dsc-om-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESystem%20Center%20-%20Operations%20Manager%20build%20versions%3C%2FA%3E.%20%3CU%3ELastly%2C%20this%20problem%20may%20occur%20with%20future%20update%20rollups%20too%3C%2FU%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EIssue%3C%2FSTRONG%3E%3A%20SCOM%20Reporting%202019%20cannot%20be%20installed%20after%20the%20Management%20servers%20are%20upgraded%20to%202019%20UR1.%26nbsp%3B%20The%20following%20error%20message%20appears%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%E2%80%9C%3CFONT%20color%3D%22%23FF0000%22%3E%3CEM%3EThe%20management%20server%20is%20a%20different%20version%20than%20the%20current%20setup%20build.%20Please%20use%20a%20different%20management%20server%20or%20the%20correct%20version%20of%20setup.%20Server%20Version%3A%2010.19.10349.0.%3C%2FEM%3E%3C%2FFONT%3E%E2%80%9D%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EWorkaround%3A%20%3C%2FSTRONG%3ETo%20resolve%20this%2C%20use%20the%20following%20steps%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EOn%20the%20server%20machine%2C%20modify%20the%20registry%20key%20%22%3CEM%3E%3CSTRONG%3EHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5CSystem%20Center%20Operations%20Manager%5C12%5CSetup%5CServer%3C%2FSTRONG%3E%3C%2FEM%3E%22%20data%20%22%3CSTRONG%3ERTM_UR%20version%3C%2FSTRONG%3E%22%20from%20%22%3CSTRONG%3E10.19.10311.0%3C%2FSTRONG%3E%22(UR1%20or%20latest%20UR%20version)%20to%20%22%3CSTRONG%3E10.19.10050.0%3C%2FSTRONG%3E%22%20(RTM%20version).%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CTABLE%20border%3D%221%22%20width%3D%22100%25%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22100%25%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AakashMSFT_1-1595240977051.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F206342i2249BE76A8F2589D%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22AakashMSFT_1-1595240977051.png%22%20alt%3D%22AakashMSFT_1-1595240977051.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ERestart%20the%20%3CSTRONG%3Ehealth%20service%3C%2FSTRONG%3E.%3C%2FLI%3E%0A%3CLI%3EEnsure%20that%20the%20server%20version%20in%20%3CSTRONG%3EOperations%20Manager%20Products%3C%2FSTRONG%3E%20-%26gt%3B%20%3CSTRONG%3EManagement%20Servers%3C%2FSTRONG%3E%20is%20reset%20to%20RTM%20version.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CTABLE%20border%3D%221%22%20width%3D%22100%25%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22100%25%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AakashMSFT_2-1595240977056.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F206340i81742C94C28088B5%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22AakashMSFT_2-1595240977056.png%22%20alt%3D%22AakashMSFT_2-1595240977056.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EProceed%20with%20Reporting%2FWeb%20console%20installation.%20After%20installation%2C%20patch%20the%20components%20to%20Update%20Rollup%20(UR1%20or%20latest%20UR%20version).%3C%2FLI%3E%0A%3CLI%3EOnce%20completed%2C%20reset%20the%20%22%3CSTRONG%3ERTM_UR%20version%3C%2FSTRONG%3E%22%20reg%20key%20from%20RTM%20version%20to%20the%20appropriate%20UR%20version%20and%20restart%20the%20health%20service%20(In%20this%20case%2C%20it%20is%20UR1%2010.19.10311.0).%3C%2FLI%3E%0A%3CLI%3EOnce%20done%2C%20verify%20that%20the%20product%20version%20of%20the%20server%20is%20updated%20back%20to%20the%20UR%20version.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CTABLE%20border%3D%221%22%20width%3D%22100%25%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22100%25%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AakashMSFT_3-1595240977060.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F206343i14C9679DB95BED62%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22AakashMSFT_3-1595240977060.png%22%20alt%3D%22AakashMSFT_3-1595240977060.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1532815%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20to%20install%20SCOM%20Reporting%202019%20successfully%20when%20UR1%20is%20installed.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1532815%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESCOM%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESystem%20Center%20Operations%20Manager%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

Lately, we have observed a strange issue with users unable to install SCOM reporting 2019 when Update Rollup 1 is installed in the environment. Below are the steps to successfully install the component. Please make sure that you are using the correct Build numbers of Update Rollup. They are available at System Center - Operations Manager build versions. Lastly, this problem may occur with future update rollups too.

 

 

Issue: SCOM Reporting 2019 cannot be installed after the Management servers are upgraded to 2019 UR1.  The following error message appears:

 

The management server is a different version than the current setup build. Please use a different management server or the correct version of setup. Server Version: 10.19.10349.0.

 

Workaround: To resolve this, use the following steps:

  • On the server machine, modify the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations Manager\12\Setup\Server" data "RTM_UR version" from "10.19.10311.0"(UR1 or latest UR version) to "10.19.10050.0" (RTM version).
AakashMSFT_1-1595240977051.png

 

 

  • Restart the health service.
  • Ensure that the server version in Operations Manager Products -> Management Servers is reset to RTM version.
AakashMSFT_2-1595240977056.png

 

  • Proceed with Reporting/Web console installation. After installation, patch the components to Update Rollup (UR1 or latest UR version).
  • Once completed, reset the "RTM_UR version" reg key from RTM version to the appropriate UR version and restart the health service (In this case, it is UR1 10.19.10311.0).
  • Once done, verify that the product version of the server is updated back to the UR version.
AakashMSFT_3-1595240977060.png