There is already a very good deployment guide posted on TechNet here: http://technet.microsoft.com/en-us/library/hh457006.aspx The TechNet deployment guide provides an excellent walkthrough of installing OpsMgr 2012 for the “all in one” scenario, where all roles are installed on a single server. That is a very good method for doing simple functionality testing and lab exercises.
The following article will cover a basic install of System Center Operations Manager 2012 as well. The concept is to perform a limited deployment of OpsMgr, only utilizing as few servers as possible, but enough to demonstrate the new roles and capabilities in OM2012. For this reason, this document will cover a deployment on 3 servers. A dedicated SQL server, and two management servers will be deployed. This will allow us to show the benefits of the RMS removal, and the management server pools concepts. This is to be used as a template only, for a customer to implement as their own pilot or POC, or customized deployment guide. It is intended to be general in nature and will require the customer to modify it to suit their specific data and processes.
Windows Server 2008 R2 SP1 Enterprise edition will be installed as the base OS for all platforms. All servers will be a member of the AD domain.
SQL 2008 R2 ENT edition with SP1 will be the base standard for all database and SQL reporting services. (Note: SP1 is not technically required, however it is strongly recommended to always apply the latest *supported* SP and CU to SQL when deploying.)
High Level Deployment Process:
1. In AD, create the following accounts and groups, according to your naming convention:
2. Add the “OMAA” account and the “OMDAS” account to the “SCOMAdmins” global group.
3. Add the domain user accounts for yourself and your team to the “SCOMAdmins” group.
4. Install Windows Server 2008 R2 SP1 to all server role servers.
5. Install Prerequisites and SQL 2008.
6. Install the Management Server and Database Components
7. Install the Reporting components.
8. Deploy Agents
9. Import Management packs
10. Set up security (roles and run-as accounts)
1. Install Windows Server 2008R2 SP1 to all Servers
2. Add the .NET 3.5.1 feature to windows. Use the Server Manager UI, or use PowerShell:
Open PowerShell (as an administrator) and run the following: Import-Module ServerManager <then> Add-WindowsFeature NET-Framework-Core
Open PowerShell (as an administrator) and run the following:
3. Install .NET 4.0 to all servers
4. Install the Report Viewer controls to all Management Servers. Install them from http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=6442
5. Install all available Windows Updates.
6. Join all servers to domain.
7. Add the “SCOMAdmins” domain global group to the Local Administrators group on each server.
8. Install IIS on any management server that will also host a web console:
Open PowerShell (as an administrator) and run the following: Import-Module ServerManager <then> 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
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
9. Install SQL 2008 R2 to the DB server role
Step by step deployment guide:
1. Install the Management Server role on OMMS1. You can also refer to: http://technet.microsoft.com/en-us/library/hh301922.aspx
2. Install the second Management Server on OMMS2. You can also refer to: http://technet.microsoft.com/en-us/library/hh284673.aspx
3. Install OM12 Reporting on the SQL server. You can also refer to: http://technet.microsoft.com/en-us/library/hh298611.aspx
4. Deploy an agent to the SQL DB server.
5. Import management packs. Also refer to: http://technet.microsoft.com/en-us/library/hh212691.aspx
6. Create a dashboard view:
7. Manually grow your Database sizes and configure SQL
8. Continue with optional activities from the Quick Start guide on TechNet:
9. Enable Agent Proxy
I prefer to simply enable agent proxy for all agents. You can do this by running a script on a schedule, either via scheduled task, Orchestrator, or embed into a management pack. http://blogs.technet.com/b/kevinholman/archive/2010/11/09/how-to-set-agent-proxy-enabled-for-all-agents.aspx
I prefer to simply enable agent proxy for all agents. You can do this by running a script on a schedule, either via scheduled task, Orchestrator, or embed into a management pack.
Where can I download SCOM 2012 RTM version?
Thank's for sharing
Handy Work for step by step guide. Awesome.
Very nice quick and dirty walk-through!
The links for "Deploy an agent to the SQL DB server", "Import management packs", and "Create a dashboard view" no longer work, though. Can you point us to the updated links?
Working on it!
Now this is a good write-up Kev. That's what I'm talkin' bout
Sam - you see my old EDS documentation style, eh?
Ah yes. It has your name all over it. Good job!!
BTW: Per the msg I sent you Thursday there's no need to get back to me yet. Let me first digest some of the pointers and tips you articulated so well in this blog. If I have further questions I'll let you you know. But thanks again for sharing your thoughts.
Any hints on what to do when an upgrade from a cluster 2007 R2 RMS does wrong? or at least in my case fails the prereqs due to devices still claiming to report to the RMS but the only thing the DB shows reporting to the RMs are the secondary management servers.
Thanks for sharing, very useful!
I am trying to add second management server but getting below error even though Data Access service is running on other management server.
Error- Setup was unable to to connect to a management server in this management group. Please make sure that the Data Access service is running on at least one management server in this management group.
the guide is awesome i just used it to deploy the scom 2012 in our organization.
Hi Kevin, currently I am running SCOM 2007 R2 CU4 as a single management group with two management servers. I am building a brand new SCOM 2012 CU1 with 4 VMs and a physical SQL server. My question is since I am not upgrading my existing SCOM2007R2 environment, will I be able to move my Data Warehouse DB from 2007 r2 to SCOM 2012 and run the upgrade on it? If yes what steps do I need to follow without impacting my existing 2007 r2 production scom environment? We have almost two year worth of historical data in our data warehouse that can’t lose at any cost…please advice!
I believe Graham Davies answered my question: