Upgrading to SCOM 2019 Step-by-step

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at UmbracoSquaredUp.Core.Models.ViewModels.Media.ImageViewModel..ctor(IPublishedContent image)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at System.Activator.CreateInstance(Type type, Object[] args)
   at UmbracoSquaredUp.Core.Extensions.PublishedContentExtensions.AsNestedContent[T](IPublishedContent node)
   at ASP._Page_Views_Partials_RTEImage_cshtml.Execute() in C:\home\site\wwwroot\Views\Partials\RTEImage.cshtml:line 14
   at System.Web.WebPages.WebPageBase.ExecutePageHierarchy()
   at System.Web.Mvc.WebViewPage.ExecutePageHierarchy()
   at System.Web.WebPages.WebPageBase.ExecutePageHierarchy(WebPageContext pageContext, TextWriter writer, WebPageRenderingBase startPage)
   at System.Web.Mvc.RazorView.RenderView(ViewContext viewContext, TextWriter writer, Object instance)
   at System.Web.Mvc.BuildManagerCompiledView.Render(ViewContext viewContext, TextWriter writer)
   at Umbraco.Core.Profiling.ProfilingView.Render(ViewContext viewContext, TextWriter writer)
   at System.Web.Mvc.HtmlHelper.RenderPartialInternal(String partialViewName, ViewDataDictionary viewData, Object model, TextWriter writer, ViewEngineCollection viewEngineCollection)
   at System.Web.Mvc.Html.PartialExtensions.Partial(HtmlHelper htmlHelper, String partialViewName, Object model, ViewDataDictionary viewData)
   at UmbracoSquaredUp.Core.Helpers.TemplateHelper.ParseImages(String text, HtmlHelper helper, Int32 maxWidth)
   at UmbracoSquaredUp.Core.Helpers.TemplateHelper.OptimizeRTEContent(String content, HtmlHelper Html, Boolean isBlog)
   at ASP._Page_Views_Partials_grid_editors_rte_cshtml.Execute() in C:\home\site\wwwroot\Views\Partials\grid\editors\rte.cshtml:line 7
   at System.Web.WebPages.WebPageBase.ExecutePageHierarchy()
   at System.Web.Mvc.WebViewPage.ExecutePageHierarchy()
   at System.Web.WebPages.WebPageBase.ExecutePageHierarchy(WebPageContext pageContext, TextWriter writer, WebPageRenderingBase startPage)
   at System.Web.Mvc.RazorView.RenderView(ViewContext viewContext, TextWriter writer, Object instance)
   at System.Web.Mvc.BuildManagerCompiledView.Render(ViewContext viewContext, TextWriter writer)
   at Umbraco.Core.Profiling.ProfilingView.Render(ViewContext viewContext, TextWriter writer)
   at System.Web.Mvc.HtmlHelper.RenderPartialInternal(String partialViewName, ViewDataDictionary viewData, Object model, TextWriter writer, ViewEngineCollection viewEngineCollection)
   at System.Web.Mvc.Html.PartialExtensions.Partial(HtmlHelper htmlHelper, String partialViewName, Object model, ViewDataDictionary viewData)
   at System.Web.Mvc.Html.PartialExtensions.Partial(HtmlHelper htmlHelper, String partialViewName, Object model)
   at ASP._Page_Views_Partials_grid_editors_base_cshtml.Execute() in C:\home\site\wwwroot\Views\Partials\grid\editors\base.cshtml:line 20

Upgrading to SCOM 2019

1. Mount the Operations Manager 2019 ISO image to the SCOM management server that we will perform the upgrade on.

2. Run the SCOM_2019.exe (Run as administrator) to start the extraction wizard of the SCOM 2019 installation files.

3. Click Next to continue.

4. Check the I accept the agreement and then click Next.

5. Specify a location where to extract the SCOM 2019 installation files.

6. Click Extract to start extracting the SCOM 2019 installation files.

7. Once done click Finish to exit the extraction wizard.

8. Next up, head to the location where the SCOM 2019 installation files were extracted to.

9. Now right-click the Setup.exe and choose Run as administrator..

10. Select Install to start the installation wizard of SCOM 2019.

11. Click Next to continue.

12. Check the I have read, understood, and agree with the license terms and then click Next.

13. Specify an installation location or use the default installation location, then click Next.

14. If all prerequisites have passed click Next.

Note: If you have a pending reboot it will be shown on here, it is recommended to perform the reboot before the installation.

15. Configure the account for the System Center Configuration service and System Center Data Access service or use the builtin Local System.

Note: If the management server and the operational database are on different computers, the System Center Configuration service and System Center Data Access account have to be changed to a domain account.

16. Click Upgrade to start the upgrade process.

17. Once the upgrade is complete, click Finish.

18. Let’s open up the Operations Console and check the version installed by going to Help > About.

Post-upgrade tasks

Now that we have successfully upgraded to SCOM 2019, we will need to perform a few post-upgrade tasks, as we disabled a few things prior to the upgrade.

High-level overview of the post-upgrade tasks

  1. Re-enable the Notification Subscriptions.
  2. Restart or re-enable the Connector Services (if needed).
  3. Re-enable Audit Collection Services (ACS) on agents that were upgraded (if needed).
  4. Reset agent HealthService Cache size.
  5. Start the application pools of Operation Manager and MonitoringView in the IIS.
  6. Verify the upgrade was successful.

Detailed overview of the post-upgrade tasks

1. Open the Operations Console and head to the Administration pane and select Subscriptions.

1.1. In the Subscriptions pane, right-click the subscriptions that should be enabled and select Enable to enable them.

2. If any integrations to the SCOM environment exist, we will need to start the services of the connectors.

2.1. Go to Start > search for “Services” and hit Enter to access the services.

2.2. Look for the service(s) of the connector(s), right-click the service and choose Start.

3. If you had Audit Collection Services (ACS) enabled for an agent or multiple agents prior to upgrade, it was disabled as part of the agent upgrade process. Re-enable ACS as appropriate.

4. If the agent HealthService cache size was modified in the registry we will have to change it back.

4.1. Go to Start and search for “Regedit” and hit Enter to open the Registry Editor.

4.2. Head to the following path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlsSet\Services\HealthService\Parameters\Management Groups

4.3. Modify the value of the maximumQueueSizeKb to it’s default value: 15360(15MB).

Note: If the maximumQueueSizeKb registry key had another default value, change it to that value.

5. Now we will start the IIS application pools of the OperationsManager and OperationsManagerMonitoringViews within the Internet Information Services (IIS) Manager.

5.1. On the SCOM management server, go to Start and search for “IIS” and hit Enterto open the Internet Information Services (IIS) Manager.

5.2. In the Internet Information Services (IIS) Manager expand the local serverand then expand the Application Pools.

5.3. Right-click the OperationsManager application pool and choose Start, do the same with the OperationsManagerMonitoringView application pool.

5.4. Once both OperationsManager and OperationsManagerMonitoringViewapplication pools are started, we can continue to the last task to check the health of our new SCOM 2019 environment!

6. Verify that the upgrade was successful by checking the health of the SCOM environment and other monitors.

6.1. Open the Operations Console, and head to the Monitoring pane, then expand the Operations Manager folder, and select the Management Group Health dashboard view.

6.2. Now check the Management Group Health in the center of the screen.

6.3. If everything looks healthy, let’s have a final look at the Operations Managerevent log, if you do have errors, take action to see what the error is about.

6.4. Right-click on Start and choose Event Viewer, then expand the Applications and Services Logs and select the Operations Manager log.

Note: If any errors are found in the Operations Manager event log, analyse them and check if they need resolving.

 

Configuring the license for SCOM 2019

When we upgrade from an earlier version of SCOM, our newly upgraded SCOM will be an evaluation version, this means that we will need to set the license once again.

1.  Open the Operations Manager Shell (Run as administrator) on the SCOM management server, and type in the SCOM PowerShell command below and then hit Enter to run the command.

Set-SCOMLicense -ProductId " XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"

2. The command will ask for the SCOM management server, enter the the FQDN of the SCOM management server and then hit Enter.

3. We will now be asked for credentials, enter a username who has write access to the OperationsManager database, next we will be asked if we want to continue performing this operation, select A (Yes to All).

4. The command will run for a short while and once it’s completed we should receive the message below:

5. Now we will have to restart the System Center Data Access service on all the SCOM management servers for the license to take effect.

6. Go to Start and search for “Services” and then hit Enter to open it.

7. Look for the System Center Data Access service, select it and then right-click it and choose Restart.

8. Now open the Operations Console (close it if it was already open and re-open it), then go to Help > About, and we should now see that our SCOM 2019 is fully licensed!

We have now successfully upgraded from SCOM 2016 to SCOM 2019!

Happy SCOMming! 😉