Brad Bird overcomes some technical challenges in configuring Microsoft's System Center Operations Manager 2007 for use in his System Center test lab. He tells you how to solve some of the problems he encountered.
As part of my System Center lab install, I decided to configure the Beta version of System Center Operations Manager (SCOM) 2007 R2.
SCOM 2007 R2 is scheduled to be released in RTM (release to manufacturing) version around the time of the Microsoft Management Summit 2009 in May.
I have two Windows Server 2008 lab servers, but only one that has both 64-bit and hardware virtualization. I decided to use the 64-bit server to install Windows Server 2008 R2 with Hyper-V R2 in their current beta releases to be used for my lab. I'll update the OSs and applications with RC (release candidate) versions or RTM as they become available.
Based on past experience, SQL 2005 does not perform well when virtualized. Since I do not have the DBA experience with SQL Server 2005 to tweak this application to make it perform, I needed to install it on a physical machine for my System Center projects.
There are a couple of challenges. These are not impossible challenges to overcome, but good to know about in advance.
In this case, there was a slightly limiting factor because I needed to install SQL Server 2005 32-bit for compatibility reasons and because this will be a shared DB server. I felt this was fair game since, in a production scenario, we often encounter limitations and decided to still use the 32-bit SQL install.What to look out for First, SQL 2005 32-bit runs properly only on Server 2008 with SP2. There is a compatibility dialog box (Figure A) stating this as you try to install it. You must upgrade your version of SQL Server 2005 to SP2 before using it on a Windows Server 2008 system.
The next challenge is installing IIS with ASP.NET. Well, I already had the basic Web server installed with IIS 7 along with some CGI components that I needed for Virtual Server 2005 R2 SP1. Yet, the IIS instance was still showing as not installed.
For those new to Server 2008, this version of Windows is highly security. Services are installed in the form of Roles and Features.
I re-ran the role-configuration wizard from within IIS 7 and, sure enough, ASP.NET was not present. Not present in Server 2008 does not mean the same as previous versions where that meant files were present locally but the feature was not enabled.
In Server 2008, "not present" means files are not even present locally, which is way more secure as there can be no code exploited which does not exist!
So it turns out that by enabling the ASP.NET, the SQL server 2005 install wizard now believes IIS to be installed. Weird.
However, the warning still appears for ASP.NET. Upon inspection of the warning message, here is the issue: ASP.NET is somehow registered as the 64-bit version. Maybe it has something to do with the 64-bit OS! SQL 2005 requires the 32-bit version of ASP.NET.
The solution is documented here:
- Download and install the x64 redistributable .NET v2.0 framework.
- From a command prompt, you must run the following: Cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
- Type the following to install ASP.NET 2.0 32-bit and to install the script maps at the IIS root and under: %SYSTEMROOT\Microsoft.Net\Framework\v2.0.50727\aspnet_regiis.exe -i
- Make sure that the ASP.NET version 2.0.5077 (32-bit) is set to Allowed in the service extensions within IIS.
Don't forget to install the Management Studio (Figure C) as a custom item when doing the install so that you can administer the database; it does not get added by default.