In the previous part of this article series we have finished installing Management Server feature on two servers SCOMMS-01 and SCOMMS-02 as members of the same Management group, today we continue the deployment of our lab with installing the Report Server and Web Console, so let’s get started.
I have already prepared a server and named it SCOM-RSWeb, we have already installed our Software prerequisites including .Net framework 3.5 and 4 along with IIS and all it’s required Services.
Important Note If you install a stand-alone web console on a server, you will not be able to add the management server feature to this server. If you want to install the management server and web console on the same server, you must either install both features simultaneously, or install the management server before you install the web console.
Note Network Load Balancer is not supported for the Operations Manager web console or Reporting server.
Run the setup from the installation media on the Report Server.
When you install the web console, three components are installed: the Operations Manager web console itself, Application Diagnostics console, and Application Advisor console.If Application Diagnostics console is not installed, when viewing APM alerts, you will not be able to use the link embedded in the alert description to launch the APM event details. To use this feature, install the web console within the management group.
Please note that if you do not install the Report Server component along with the Web Console you will receive the below warning “The Reporting Component was not installed or is not installed. if the reporting component is not installed, Application Advisor will not work correctly”.
Click next for the default installation path.
Use Mixed Authentication for intranet scenarios.
If you install the management server on a server using a domain account for System Center Configuration service and System Center Data Access service, and then install the web console on a different server and select Mixed Authentication, you may need to register Service Principal Names and configure constraint delegations as described here ( Running the Web Console Server on a standalone server using Windows Authentication )
Confirm the health of Operations Manager reports
Open the Operations console, and select the Reporting workspace. from there open the Microsoft ODR Report Library. open one of the default reports.
Configure permissions inheritance for the web console
from the windows explorer browse to the directory ( C:\Program Files\System Center 2012\Operations Manager\WebConsole\MonitoringView )
Remove the Administrators and System permissions from the permission entries.
Let’s try to access SCOM Web Console. you are going to need to install Silver Light from here ( Download Silverlight )
An Operations Manager agent is a service that is installed on a computer. The agent collects data, compares sampled data to predefined values, creates alerts, and runs responses. A management server receives and distributes configurations to agents on monitored computers. There are several methods you can use to install an Operations Manager agent on a computer:
- You can use the Discovery Wizard in the Operations console, sometimes called a push installation. (All other methods are considered manual installations.) This method works for computers running Windows, UNIX, and Linux operating systems.
- You can run the Setup Wizard from the Operations Manager installation media and install the agent directly on a computer running Windows.
- You can install an agent directly on a computer running Windows, UNIX, and Linux operating systems by using a command line.
Agents that are installed by using the Discovery Wizard can be managed from the Operations console, such as updating agent versions, applying patches, and configuring the management server that the agent reports to. When you install the agent using a manual method, updates to the agent must also be performed manually.
Launch the Discovery Wizard
I will be user the Management Server Action account since it is a domain admin, as mentioned before the Action account is not recommended to be a domain admin, so in a production environment you can select another user with an administrative rights on the discovered computers.
We are done with the deployment, so what now ? we have an SP1 and an R2 versions released, both are supported on Windows Server 2012. so i will be upgrading this lab to those versions and after that i will be moving all SCOM 2012 R2 installed features to new servers with Windows Server 2012 R2 as the operating system while making sure to migrate my existing configurations and existing events, i don’t want to loose my existing information after all. so that’s what we will be doing in the next parts of this series. See You..