Hello Readers
As continuing on Part 4, we are now going to look at Installing System Center Operations Manager 2012 R2 before than moving on to Proactive Monitoring of your Lync Environment. As always there are a couple of pre-requisites we need to complete before inserting the media into the Server.
First of all we are going to need 4 Service Account as show below
The Service Account will need the following permissions
Account | Permission |
SCOM Action Action | Domain Administrator |
SCOM Data Access | Local Admin on SQL and SCOM Server |
SCOM Data Reader | Domain User |
SCOM Data Writer | Domain User |
We now need to use the Object Editor to the Data Access Account and edit the Attribute for servicePrincipalName
Note: If you cannot find this tab switch on Advanced Feature is Active Directory
We need to add the following;
- MSOMSdkSvc/sc01
- MSOMSdkSvc/sc01.lyncme.local
Please note: This is the server name of my SCOM Server, you need to specify your server.
Now for a bit of information from Microsoft
We recommend that you check for updates and hotfixes for Microsoft SQL Server. Note the following database considerations for Operations Manager:
- SQL Server 2008 R2 and SQL Server 2012 are available in both Standard and Enterprise editions. Operations Manager will function with both editions.
- Operations Manager does not support hosting its databases or SQL Server Reporting Services on a 32-bit edition of SQL Server.
- Using a different version of SQL Server for different Operations Manager features is not supported. The same version should be used for all features.
- SQL Server collation settings for all databases must be one of the following: SQL_Latin1_General_CP1_CI_AS, French_CI_AS, Cyrillic_General_CI_AS, Chinese_PRC_CI_AS, Japanese_CI_AS, Traditional_Spanish_CI_AS, or Latin1_General_CI_AS. No other collation settings are supported.
Step 4 is the one will care most about as the standard built of an SQL Instance doesnt match the collations supported.
We will now need to create new SQL instance for SCOM on your SQL Server.
I have now connected to my DB01 (SQL Server) and launched SQL Server Installation Server –> Click Installation –> New SQL Server Stand-alone installation or add features to an existing installation
Once Setup Support Rules has complete we can proceed, you have any failed checks please resolve before proceeding. Press OK
Install the latest updates at Product Updates Page and Press Next
If your lab machine is not internet connected, you can download updates at a later stage and install from http://catalog.update.microsoft.com/v7/site/
Once Install Setup Files has completed –> Press Install
You should now see Setup Support Rules and because there is no failed checks –> Press Next
Tick Perform a new installation of SQL Server
Press Next
Press Next to Product Key
Tick “I Accept” and Press Next
You will now need to select the following features required for SCOM
- Database Engine Services
- Full-Text and Semantic Extractions for Search
- Reporting Services – Native
- Management Tools – Basic and Complete (for running queries and configuring SQL services)
Press Next
Press Next
I will be using the name “SCOM” for my SQL Instance and using Default Storage Location
Press Next
Press Next to Storage Requirement notice
In my Labs I always use a Service Account for SQL Services. You can leave this default if you chose so
Click on the Collation Tab –> Press Customize –> Tick SQL Collation –> Select one of the compatible Collations, I will be using SQL_Latin1_General_CP1_CI_AS –-> Press OK
Press Next
Add the account you want to have rights to the SQL Instance, I have added lyncme\administrator and lyncme\svc.scomaa
Press Next –> Press Next –> Press Next –> Press Next –> Press Next –> Press Install
Please note: Installation might take a while so while your waiting add SCOM Data Access to Local Administrator Group on SQL Server
Open Microsoft SQL Server Management Studio –> Specify the SCOM Instance you will be using –> Press Connect
Right Click ServerName\Instance (DB01\SCOM) –> Properties –> Memory –> Change to low value (I changed to 8164)
In this lab is not something to be concerned about it in Production Environment it will be important for the performance of the SQL Server as the default value will eat all your all your SQL resources.
Press OK and Close SQL Management Studio
Press Close
We now need to move back to the System Center Operations Manager Server.
We are now need to add SCOM Data Access to Local Administrator Group on SCOM Server if you have completed this step already. After you have completed all the below steps will now need to download and install the pre-requisites for SCOM installation. I have put the tools required into the following OneDrive Location
In this location you will also find a Powershell Script that needs to run on the SCOM Server. The command line is listed and will restart the server after its finished installing.
Add-WindowsFeature NET-Framework-Core,AS-HTTP-Activation,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Request-Monitor,Web-Filtering,Web-Stat-Compression,AS-Web-Support,Web-Metabase,Web-Asp-Net,Web-Windows-Auth –restart
And also find SQLSysCLRTypes.exe and ReportViewer.exe which needs to be installed in that order.
After you have completed all the pre-requisites Insert the SCOM Media and run Setup.exe
As I want the latest and greatest for this SCOM Server, I have ticked Download the latest updates to the setup program.
Press Install
Tick
- Management Server
I have also ticked Operations Console, you dont have to install this on the SCOM Server. It can be installed on a SysAdmin Laptop or Desktop or Management Server
Press Next –> Press Next
Press Next to continue
Tick Create the Management server in a new management group
Enter a name and Press Next
Tick “I have read, understood, and with the licence terms”
Press Next
Enter your SQL Server Name and instance as shown below. If every thing is correct you will be able to Press Next
Enter your SQL Server Name and instance as shown below. If every thing is correct you will be able to Press Next
We now need to enter the Service Accounts we created earlier as shown below –> Press Next
Press OK to the below warning
I have ticked No, I am not willing to participate but you can select any one –> Press Next
Press Install
This will now take some time to complete, my suggestion is go grab a cup of tea or coffee
Now your Operation Manager has installed you might notice an error as shown below
This is because no product has been entered for SCOM. If you have a licence key you can enter it by doing the following
Launch Operation Management Shell and type
Set-SCOMLicense –productid <pid>
Now Press Close and Operation Console should now open successfully
This concludes this post
In Part 6 will we look at setting up Proactive Monitoring for your Lync Environment by publishing Agents and installing the Lync Management Pack.
Regards
Andrew Price