Install OpsMgr 2012 SP1 on Server 2012 and SQL 2012 SP1

This time I installed a new lab environment with new components: OpsMgr 2012 SP1, Windows Server 2012 and SQL Server 2012 SP1. All Configuration will be mentioned in this blogpost. Here we go!
 
In my setup I'm using 2 VM's: 1 Domain Controller (VDC01) with 2GB memory and 1 SQL/OpsMgr server (VOM01) with 8GB memory. Let's start with the Domain Controller first.
 
- Install Windows Server 2012 (5 minutes on SSD);
- Change computer name to VDC01 and restart;
- Add static IP-address (192.168.137.x) to the network-adapter;
- Add Roles with PowerShell cmdlets (Install-WindowsFeature -Name AD-Domain-Services,DNS,RSAT);
- Add Features with PowerShell cmdlets (Install-WindowsFeature NET-Framework-Core -Source D:\Sources\SxS);
- Promote to Domain Controller in Server Manager (Add a new forest);
- Choose Contoso.com as Root domain name (for example) and use default settings in the wizard. Only warnings are displayed in the Prerequisites check, so choose Install after read them;
- After restart login with a Domain Administrator account. Disable Windows Firewall and IE ESC for all profiles/accounts;

- Create 5 service accounts for SQL (SVC_SQL) and SCOM (SVC_SCOMSDK, SVC_SCOMDR, SVC_SCOMDW) as Domain User. Only the SCOM Action Account (SVC_SCOMAA) has Domain Admin permissions.

Let's start with the OpsMgr server now!
 
- Install Windows Server 2012 (5 minutes on SSD);
- Change computer name to VOM01 and restart;
- Add static IP-address (192.168.137.x) to the network-adapter;
- Promote to Domain Server in Server Manager (Contoso.com);
- After restart login with Domain Administrator account. Disable Windows Firewall and IE ESC for all profiles/accounts;
- Add Roles with PowerShell cmdlets (Install-WindowsFeature -Name 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,NET-HTTP-Activation -Source D:\Sources\SxS);
- Install Microsoft Report Viewer 2010 Redistributable Package: http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=6442

- Install SQL Server 2012 SP1 and make sure the collation is set to "SQL_Latin1_General_CP1_CI_AS";
- Choose: Database Engine Services, Full-Text search, Reporting Services and Management Tools (2x);
- Choose default settings where possible and start installation;
- Configure SQL Server and SQL Server Agent to run with the SVC_SQL account (SQL Server Configuration Manager);
- Configure Reporting Services to run with the SVC_SQL account (Reporting Services Configuration Manager);
- Assign maximum server memory (4096 MB) in SQL Server Management Studio in SQL Server properties.

 
At last OpsMgr installation can be started!
 
- Install all features (Management server, Operations console, Web console, Reporting server);
- Choose the default installation location;
- All prerequisites have passed;
- Management group name: CONTOSO;
- Configure the operational database: VOM01 (default settings);
- Configure the data warehouse database: VOM01 (default settings);
- SQL Server instance for reporting services: VOM01;
- Use the Default website & Mixed authentication;
- Configure Operations Manager accounts (4 service accounts, the SDK account must have local admin permissions on the SCOM server);
- Choose the Microsoft Update setting of your choice;
- Installation is done within 30 minutes on SSD.

If you installed .NET Framework 4 before installing the IIS you’ll get an error:
- The ASP.NET 4.0 handler is not registered with IIS
- Web Console cannot operate properly because the ISAPI and CGI Restrictions in Internet Information Services (IIS) are disabled or missing for ASP.NET 4.0.
To fix this, you should run: %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -enable -r

Above steps can be done in just one day. After that a new lab environment is running with new components: OpsMgr 2012 SP1, Windows Server 2012 and SQL Server 2012 SP1. Have fun!

How to upgrade OpsMgr 2007 R2 to 2012 SP1

This week I received a question if OpsMgr 2007 R2 can be upgraded to 2012 SP1. The answer is Yes, that's possible! However you have the choice between an in-place upgrade or a side-by-side upgrade. Both options has their own benefits, disadvantages and configuration steps. Let's start to have a look at them.

Your first start is here: Microsoft TechNet

It's all about the existing configuration, how many OpsMgr servers there are, custom management packs, used Windows version, used SQL version and SQL Collation set, which must be SQL_Latin1_General_CP1_CI_AS. There are a few "Upgrade Process Flow Diagrams" which can be used during the upgrade process. They can be found HERE.

Another choice is about having pollution in the existing database. Do you want a new, nice and clean installation with new management packs and configuration, or do you want to use your existing environment with all custom management packs and configuration in it? Is history/trending important or do you want to start all over again? It depends on the situation I guess.

The upgrade to OpsMgr 2012 SP1 is a two way step. First a migration from OpsMgr 2007 R2 to 2012 is needed. Then the 2012 SP1 setup can be started for the next upgrade. To help you with the upgrade, a "Upgrade Helper Management Pack" is available on the OpsMgr 2012 installation media. Just use it, and follow the steps in the right order. More information can be found HERE.

For the first upgrade to 2012, the minimum cumulative update (CU) for OpsMgr 2007 R2 must be CU4. It's recommended to use the latest version available, which is CU7. Just download it HERE.

There are a few prerequisites which are needed before the upgrade: Just make sure there is a full backup of the Management Server and OpsMgr database, install DotNet Framework 4.0 and Report Viewer 2010 redistributable. Also make sure both Management Server and database is upgraded to the last patch level. A few manual steps are needed also, which can be found HERE. (Manual operations that must be performed after you update the root management server and the data warehouse).

After following all needed steps for prerequisites, the upgrade can be started. When ALL is configured right, this might not be a problem. In my LAB environment things went very well, but hey that's an almost clean environment. In a real situation I prefer a clean installation or side-by-side upgrade above an in-place upgrade. That way you can startover again and their is less risk for issues.

Hope it helps!