Following is an overview of the Configuration Manager 2007 support for the different SQL Server versions:

SQL Server 2005:

• ConfigMgr RTM and SP1 support SQL 2005 SP2 and SP3. Currently, no hotfix is required.
• ConfigMgr R2 supports SQL 2005 SP2 and SP3, with hotfix 959975.

SQL Server 2008:

• ConfigMgr RTM supports upgrading an existing SQL 2005 site database to SQL 2008, with hotfix 955229; but does not support new installation using a SQL 2008 instance to host the site database.
• ConfigMgr SP1 supports SQL 2008, with hotfix 955262.
• ConfigMgr R2 supports SQL 2008, with hotfix 957576 and 959975.

After a look at the forums, it seems that Symantec’s virus definitions dated June 21, 2010 r2 have identified various components of the awesome SCCM Right Click Tools (which i personally couldn’t survive without) as “Trojan.Gen” Since this is a generic detection name “for many individual but varied Trojans for which specific definitions have not been created. A generic detection is used because it protects against many Trojans that share similar characteristics” this has to be a false positive. This is just another example of how definition based anti-virus tools are a out dated concept.

1. Backup the database.

2. Find the entries for the DP package share:

Select * from pkgservers where NALpath like ‘%\<server>%’
Select * from pkgstatus where pkgserver like ‘%\<server>%’
Select * from contentdpmap where serverpath like ‘%\<server>%’
Select * from DPinfo where servername like ‘%<server>%’

3. Delete any entries from any of the above tables that point to the nonexistent share:
Delete from pkgservers where NALpath like ‘%\<server>%’
Delete from pkgstatus where pkgserver like ‘%\<server>%’
Delete from contentdpmap where serverpath like ‘%\<server>%’
Delete from DPinfo where servername like ‘%<server>%’

Keep in mind – This metod is NOT supported by Microsoft

error:

SMS Site Component Manager failed to deinstall all SMS server components from site system “\servername“.

SMS Site Component Manager failed to reinstall this component on this site system.

If logging is enabled for the SMS_SITE_COMPONENT_MANAGER service, entries similar to the following are found in the SmsLogsSitecomp.Log file:

The error:

MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory.

Possible cause: The IIS IWAM account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IWAM account.  (i.e.: “net user IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation.  Note:  You can use “net user” to modify the account properties.

Possible cause: The IIS IUSR account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IUSR account.  (i.e.: “net user IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation.  Note:  You can use “net user” to modify the account properties.

Possible cause: The designated Web Site is disabled in IIS.
Solution: Verify that the designated Web Site is enabled, and functioning properly.

Solution:

This worked for me:
1. Remove BITS
2. Reboot
3. Add BITS
4. Trigger installation (Stop and Start SMS_SITE_COMPONENT_MANAGER using the ConfigMgr Service Manager)