You need to implement the planned reporting changes after the Reporting server in the London office is deployed. What should you do?

The Security settings in the Operations Manager console control role-based access and account permissions, not the registration of a reporting server endpoint.

The Enable-SCOMOperationalDataReporting cmdlet enables the flow of operational data to reporting but does not configure the connection to a newly deployed Reporting server location.

Uploading a report model (.smdl) file directly to SSRS bypasses the Operations Manager integration layer and does not register the server within the OpsMgr console Reporting settings.

The Operations Manager console includes a dedicated Reporting settings section under Administration where administrators register and configure the SQL Server Reporting Services URL for the reporting server. Configuring these settings after deploying the London Reporting server connects OpsMgr to the new SSRS instance so reports can be published and accessed. This is the standard post-deployment step required to make a new reporting server operational within OpsMgr.