Let’s get started: System Center 2012 SP1 and later is supported in the Windows Azure Virtual Machine environment (infrastructure-as-a-service). Reference link.
In 2 Part series, we will cover the installation of SCOM 2012 R2 in Windows Azure and Monitoring Windows Azure Environment using Ops Mgr. System Center Operation Manager is powerful tool for monitoring Application and Services running in Datacenter, Hybrid cloud and Windows Azure.
Installation of SCOM 2012 in Windows Azure Virtual Machine:
In this blog, we will focus of Single Instance deployment of SC Operation Manager 2012.
You already have configured Windows Azure Subscription with Affinity Group (Region), Virtual Network, Storage Account.
There will be Active Directory Domain Controller and SCOM VM will be a domain member.
In my scenario, I have configured in Windows Azure Subscription:
Affinity Group: SCOMAG (Southeast Asia).
Storage account linked to SCOMAG affinity Group.
Virtual Network linked to SCOMAG affinity group. Virtual Address Space subnet: 10.20.1.0/24
Register DNS: 10.20.1.4.
Existing Contoso.com Doman Controller: Running in Windows Azure in Separate Virtual machine. (IP address: 10.20.1.4)
Created a new Extra Large Virtual Machine (8 Cores, 14 GB Memory) in Windows Azure for SCOM 2012 R2 (VM named OpsMgr2012r2).
Single Instance will also host SQL Server 2012. I picked Windows Server 2012 R2 Datacenter Image from the gallery. For production environment, SQL server should be separate installation.
SQL Server license is already included with System Center 2012 License. We are not going to use SQL image from the gallery due to cost factor.
For right SCOM sizing, use System Center 2012 Operations Manager Sizing Helper Tool . Download
- Joined the Virtual Machine to existing Contoso.com Domain.
- In Contoso.com Domain Controller, create the following accounts and groups, according to your naming convention:
- Contoso.com\SCOMadmin SCOM Server action account
- Contoso.com\SCOMDAS SCOM Config and Data Access service account
- Contoso.com\SCOMWRITE SCOM Reporting Write account
- Contoso.com\SCOMREAD SCOM Reporting Read account
- Contoso.com\SQLSVC SQL service account
- Contoso.com\SCOMGroup SCOM Administrators security group
- In AD, Add SCOMAdmin and SCOMdas to SCOMgroup global Security group
- On OpsMgr2012r2 Server, add SCOMgroup and SQLsrv to local administrator group.
- On OpsMgr2012r2 server, installed Prerequisite for SQL Server using Powershell Script:
Open Windows PowerShell with Administrator and run:
Add-WindowsFeature NET-Framework-Core,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Request-Monitor,Web-Filtering,Web-Stat-Compression,Web-Mgmt-Console,Web-Metabase,Web-Asp-Net,Web-Windows-Auth -Restart
- Download and install: Microsoft Report Viewer
- Install SQL Server 2012 on OpsMgr2012r2. Use SQLSRV for SQL Service account during installation. After Finish Installation.
- Install System Center 2012 R2 operation Manager:
- Login with SCOMAdmin account.
- Run Stepup.exe.
- Choose: Management Server, Web Console, Operation Console.
SCOM reporting Server is an optional.
- Click Next.
- On the specify an installation screen – choose to create the first management server in a new management group. Eg. “OpsMgrMgmtSrv” Click Next
- On database screen, specify localhost name. Continue with Installation.
- On the Account Screen, Choose Domain Account for all services and specify account created:
1. Contoso.com\SCOMadmin SCOM Server action account
2. Contoso.com\SCOMDAS SCOM Config and Data Access service account
3. Contoso.com\SCOMWRITE SCOM Reporting Write account
4. Contoso.com\SCOMREAD SCOM Reporting Read account
- Proceed and complete the installation.
For reference, TechNet article for Single-Server Deployment of Operations Manager
In Part 2, we will cover Monitoring Windows Azure from Operations Manager.