This is the fourth of a five part series discussing lessons learned through installing System Center Operations Manager onto a fully Windows 2008 environment (DC, RMS, SQL, and Reporting servers). You can see previous posts in this series at:
- http://weblog.bassq.nl/?p=233 OpsMgr by Example – Server 2008 POC – Part 1 (Domain Controller)
- http://weblog.bassq.nl/?p=236 OpsMgr by Example – Server 2008 POC – Part 2 (Database Server)
- http://weblog.bassq.nl/?p=238 OpsMgr by Example – Server 2008 POC – Part 3 (Root Management Server)
We previously installed and configured the Operations Manager database and the Root Management Server (see parts 2-3 of this series). The next step is installing the Data Warehouse server, followed in Part 5 by the series, which discusses the most difficult of the steps – the reporting server installation.
Hotfixes for OpsMgr 20007 – Windows 2008 Servers with Agents
Each of the servers in this configuration needed to have three hotfixes applied to them:
After applying these hotfixes, you will need to reboot the system.
The prerequisites were checked for the Data Warehouse in part 2 of this article (http://ops-mgr.spaces.live.com/blog/cns!3D3B8489FCAA9B51!710.entry ), since the same server is hosting both the Operations database and the Data Warehouse components in this environment.
OpsMgr Data Warehouse installation
The installation of Operations Manager’s Data Warehouse worked the same as on a Windows 2003 platform.
The SQL firewall change discussed in part 2 of this series (http://ops-mgr.spaces.live.com/blog/cns!3D3B8489FCAA9B51!710.entry ) provides the documentation for the firewall rule change required to allow connectivity to the SQL Server.
There were no surprises when installing the Data Warehouse server on Windows Server 2008.