Today I ran in an unexpected problem at a customer. My mission was to install a SCOM 2012 SP1 Proof-of-Concept to show the customer what is possible and what information he can get out of SCOM. My last couple of installation were of course on Windows Server 2012. This customer was using Windows Server 2008 R2 SP1 and more or less on the latest patch level. So I started my mission installing SCOM 2012 SP1 therefore I checked all the necessary prerequisites for SCOM on the TechNet page, although I installed SCOM many times before it is just a habit of mine.
All prerequisites were installed and the wizard ran without any issue until the end and the installation started successfully. Right at the point where the wizard wanted to install the management server the installation ended with this error…
I checked all prerequisites and also the installation logs over and over and finally, after some time I ended up with the same troubleshooting steps and the same solution like Christopher Keyaert in his blog post here:
http://scug.be/christopher/2013/01/24/scom-2012-sp1-omserver-msi-returned-error-1603/
Let’s see why you might hit this problem or not…
If you check the SCOM 2012 SP1 prerequisites only .NET Framework 4.0 is required…
If you check the SCOM 2012 prerequisites .NET Framework 3.5.1 AND .NET Framework 4.0 is required….
But in fact is does not matter if you install SCOM 2012 or SCOM 2012 SP1 you need in both cases .NET Framework 3.5.1 installed on your management server. The documentation for SCOM SP1 is wrong!
You might not hit this problem when you install the web console at the same time you install the management server on the same server, because if you are adding all required IIS features as described in TechNet the .NET Framework 3.5.1 will be installed automatically because of the IIS feature dependencies.
So what does that mean at all? For your convenience I just designed a small table:
| MS + Console installation on the server | MS + Console + Web Console installation on the server | |
|
Windows Server 2008 R2 |
SCOM installation wizard will not check for .NET Framework 3.5.1 you need to add it manually |
– |
| Windows Server 2012 | SCOM installation wizard will not check for .NET Framework 3.5.1 you need to add it manually |
– |
Conclusion: If you just install SCOM SP1 management server and SCOM console you need to add .NET Framework 3.5.1 although the setup wizard does NOT alert you on that prerequisite and the documentation on TechNet does also not explicitly mention it. If you don’t add this feature you will end with a failed installation of SCOM 2012 SP1.
All upcoming Microsoft .NET Framework is providing many features. But 4.5 has provide more benefits like Improved handling of client script through bundling and minification for improved page performance which is more important.
Reblogged this on System Center Fan and commented:
Was bitten by this one this morning when bringing up a new Operation Manager 2012 R2 site on Server 2008R2. Microsoft really should update the pre-requisite documentation