System Center Operation Manager 2012 – Installation and Tips
The Beta of SCOM was released the day 20/jul and as a participant of the CEP, which is the product trial program, I started testing with the new tool. This first post will be to drill through the installation process, but adding tips. If you wish participate in program click http://connect.microsoft.com/site1211/Survey/Survey.aspx?SurveyID=12787
The first step is preparing the Setup prerequisite requiring care or special configuration.
The SCOM 2012 is no longer compatible with SQL Server 2005, only those versions of SQL 2008 and SQL 2008 R2.
However, it requires that the collation (code page used) is SQL_Latin1_General_CP1_CI_AS when normally we use the SQL_General_CI_AS. The figure below shows the correct configuration for SQL Server:
And if your SQL is installed with a different collation? The ideal is to install a new instance rather than to change the current and the reason is that when you change the collation of user databases will be desatachados, i.e. continued on disk but left of the catalog.
If you wish, you can change using the following command and then run the “Attach” to return the previous databases.
Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=domain\user
The command must be run from the SQL installation directory, subdirectory Bootstrap Setup.
Internet Information Server (IIS)
IIS must be installed with the default features used to support portals that use.NET Framework, which will require the manual installation.NET 4.0 on Windows 2008 R2.
However, additional configuration is required to run the ISAPI Framework 4.0, as shown in the figure below:
To do this go to IIS Manager and Restrictions ISAPI option and use Allowed option in ASP.NET 4.0.
Installing the SCOM 2012
The initial screen of the installer is typical of current products from Microsoft, with the options to install agents, audit collector and gateway. The right side of the screen you cannot access the supporting documents for the installation.
Then choose the options you want, that are part of the main structure of the environment, noting that option as audit collection and gateway are installed directly on the main screen above.
The next step is to run the system prerequisites, which has the advantage compared to SCOM 2007 that it is not necessary to give the names of servers that will be used and it is possible to re-run the scan without the need to exit and return to installation. Moreover, it indicates what to do to resolve the problems of prerequisites. If you want details click on the link Full System Requirements to bring the online page with all the necessary data.
The next screen allows you to create a new management group or join one that already exists. If you choose the option to add a new server will be prompted for the server name that already exists.
In the sequel is set the name of the SQL Server and database to be created, remembering the version restrictions and collation terraces at the beginning of the post.
Finally, we define the accounts that will be used to climb the services and make the connections. If you want to create specific accounts for each role click the Security Guide link that will bring details of the required permissions for each role.
Installation started and successfully terminated quickly.
In the next posts we will see the SCOM 2012 running, wait!