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!
No comments:
Post a Comment