I'm having some terrible time with installing SCCM on my Server 2008 machine. I setup and installed SQL Server 2005 and added myself to the sysadmin role. I go through the motions of installing SCCM, but before the installation begins the pre-requiste check runs and I receive these messages form the ConfigMgrprereq log: Error - Could not connect to SQL Server -Unsupported Operating System version **This one doesn't make any sense since I'm using Server '08 -Pre-SMS 2003 SP2 direct child sites Error **I tried installing SMS SP2 and SP3, but is unable to install -Short File Name 8.3 Support Error **I have changed this countless times, but it still reports this as an error. I think it has something to do on the SQL side, but according to a few tutorials I have seem to have SQL setup correctly, but something is a miss. Any help..???? Thanks.

First, get the ConfigMgr 2007 SP2 media -- SP1 was superseded by SP2 two years ago. Is this a clean install of Windows? What was installed previously? Delete the SMS registry keys; should be HKLM\Software\WOW6432Node\Microsoft\SMS (on a 64-bit system) and try the install again.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Jason - Yes, it is a clean install of Windows and I did remove the SMS registry key you listed. I tried installing SP2 and I was only given the option to install a secondary site instead of a primary site. What does this tell me and how can I fix it? Thanks.

Verify that the media you are using is for ConfigMgr 2007 with SP2 integrated and not just the SP2 media.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

The one I downloaded is ConfigMgr07SP2Upgrade_RTM_ENU If that is not the one I need, could you provide a link to the right one to download? Thanks.

That is just the SP2 install/upgrade media. The full install is available from your MVLS site.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I'm not able to get to the SP2 install/upgrade media. I am now retrying SP1 and it passed the Pre-req check. I think deleting the SMS registry key helped that out. Right now, installation is at the 'Install SMS provider components'. It has been here for atleast 15 minutes. It might be stuck, but I don't want to cancel the install just yet. So far, the first four steps have completed: Create Accounts, Transfer files, Configure registry, Create/initialize site database, but then it jumped down to the SMS part. How long does the install take...30 -45 min.?? Do you think the install has stalled at the spot mentioned above??

It all depends on the speed of your system. I have never seen setup up completely stall out.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

The last item that is written in the ConfigMgrSetup log is 'Windows Automated Installation Kit is being installed' This was reported about an hour ago and we are still at Install SMS Provider components. The server I'm running on is a 3.07 GHz quad core processor with 12GB of RAM. So one would think the install should be moving faster..? If I cancel and start over again, I need to remove that registry key again, right?

Note that the install is not a serial thing, it is installing multiple things in parallel. The WAIK is large and always takes a while to run. Also, installation is mostly about writing files to disk, so the performance of your disks is more crucial than RAM or CPU.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I had to restart the installation w/SP1, but it did finish with errors. The SMS_Component_Manager failed to install. Any ideas for a fix? Thanks again for your help. **My original question has been answered by removing the SMS registry key. I'm marking it as the answer**