In all the videos about installing SCCM 2007, Virtual PCs are used and the program is installed on drive C:.

Operating System - Windows 2003 SP2 R2 32-bit

Drive C: - 72 GB Raid 1 - Operating System only

Drive D: - 270 GB Raid 5 - SQL 2005 SP2  and WSUS including all the WSUS content.

Drive E: - 270 GB Raid 5 - SCCM 2007 including Package share, Distribution Point, Images, Applications, etc.

I have tested this in a virtual environment and it seems to work reasonably well.  Is this a viable solution?  Any comments or suggestions would be greatly appreciated.

The videos are on C because they are Virtual PC 2007 images. You would not want to do that in production. 8 GB should be ok.The OS should support over 4 GB and you have quad core processors. SQL will  rip that box if all the roles are used, so you may want to set the memory useage to 1/2 of the total amount of RAM.  Your drive config looks good, so I think that should do it.

Which flavor of 2003?  Standard will only support 4GB RAM.  I'd lean toward putting the SQL logs on C since the OS doesn't do much (space and IO wise) and that would keep them off of your Raid5 sets.

I will likely install it on 2008 64bit Standard for the additional memory support (to support 8 GB with Standard Server) and because 64bit is supposed to be more efficient with memory management.  All applications you list support 64bit.

 I have begun our testing with an ESX VM using the above configuration (excluding disks) since they are on our SAN.

 Just be aware that if you do decide to use a 64bit OS SCCM is a 32bit application and won't be able to take advantage of the 64 bit technology.  With saying that you will be able to install SQL 64bit on the same box which will utlize it.  I would also advice not putting anything on the C:\ other than your OS, be very careful when you are installing SQL to make sure you install everything to the same directory and not let it place the Master DB or TempDB on the C:\.  I have seen cases where the TempDB will take up your C:\ due to a runaway query or badly created collection.  Not saying that will happen in your environment but it's best to be aware of it.  Are your D & E drives on the same channel if not split your log and DB between the 2 Raid 5 drives.  If they are is this the reason you are suggesting to place the logs on the C:\?  The good thing is if you place it their to start you can always move it at a later date.

lcpc78 :

 Good call on the C drive filling up.  In times past we have created two partitions on the first mirror so that C would be for the OS and then assign the second partition (L) for Logs after the OS was setup.  We (specifically the DBA) like to keep the logs for any SQL intensive application on a RAID 1 due to the poor write performance on RAID 5.  If we don't do this, he perfers a RAID 10 for everything.  I may use this for the OS, SQL, and App.  Then, create a seperate RAID 5 for the software distribution (read optimized).