Chris Stauffer at myITForum.com

Holy Pre-Requisites Batman

I just started building My SCCM 2007 server in the lab with the 120 day evaluation and all I got to say is wow there are a lot of prerequisites for this product. Why can't MS include them with the product.

Here is a list of the prerequisites I have discovered so far. If I find any more I will update this post.

Config Manager server 2007:

• Windows Server 2003 SP2 and all patches
• MMC 3.0
• .net framework 2.0 or greater ( I installed 3.0)
• MS06-030
• IIS 6.0 or greater (hinting at server 2008 that isn't out yet)
• Bits 2.5 or greater
• WebDav
• Active Server pages support
• Office Web Components for Office 2000 -2007

• IE 5.0 or greater (went with IE7)
• SQL 2005 SP2 and all patches
• WSUS 3.0
• Windows installer 3.1

These 2 prerequisites are listed in the readme file but you have to have a TAM to get them. Why didn't MS include them or at least open them to the public if they are needed.

There are two prerequisites that are not detected by the prerequisite checker and are not listed in other prerequisite documentation. You must manually apply the following hotfixes prior to running Setup: http://go.microsoft.com/fwlink/?LinkID=98349 and http://go.microsoft.com/fwlink/?LinkID=98350.

Hotfix 98350 doesn't seem to exist. I'm trying to find out what it is now.

Will update this post as I get further into the install.