Chris Stauffer at myITForum.com

Note: This only works for IE6 Sp1 or older. Any newer versions can be found in the Registry and in Add/Remove Programs.

According to MS the correct way to find the version of IE6 is to collect the SHDOCVW.dll 
Use "Software inventory Client agent" Check the Inventory Collection tab and add the  SHDOCVW.dll   Specify the location of %windir%\system32\
Then create a collection like this:

Machines with IE6 Sp1

select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client from SMS_R_System inner join SMS_G_System_SoftwareFile on SMS_G_System_SoftwareFile.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SoftwareFile.FileName = "SHDOCVW.dll" and SMS_G_System_SoftwareFile.FileVersion >= "6.00.2800.1106" and (SMS_G_System_SoftwareFile.FilePath = "c:\\windows\\system32\\" or SMS_G_System_SoftwareFile.FilePath = "c:\\winnt\\system32\\")

Need IE6 SP1

select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client from SMS_R_System inner join SMS_G_System_SoftwareFile on SMS_G_System_SoftwareFile.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SoftwareFile.FileName = "SHDOCVW.dll" and SMS_G_System_SoftwareFile.FileVersion < "6.00.2800.1106" and (SMS_G_System_SoftwareFile.FilePath = "c:\\windows\\system32\\" or SMS_G_System_SoftwareFile.FilePath = "c:\\winnt\\system32\\")

And reports like this one

SELECT DISTINCT
                      v_FullCollectionMembership.SiteCode, v_GS_SYSTEM.Name0 AS [Machine Name], v_GS_SoftwareFile.FileVersion AS [IE Version],
                      v_R_System.Operating_System_Name_and0, v_GS_SoftwareFile.FilePath
FROM         v_GS_SoftwareFile INNER JOIN
                      v_GS_SYSTEM ON v_GS_SoftwareFile.ResourceID = v_GS_SYSTEM.ResourceID INNER JOIN
                      v_R_System ON v_GS_SYSTEM.ResourceID = v_R_System.ResourceID INNER JOIN
                      v_FullCollectionMembership ON v_GS_SYSTEM.ResourceID = v_FullCollectionMembership.ResourceID
WHERE     (v_GS_SoftwareFile.FileName = 'shdocvw.dll') AND (v_GS_SoftwareFile.FilePath = 'c:\windows\system32\' OR
                      v_GS_SoftwareFile.FilePath = 'c:\winnt\system32\') AND (v_GS_SoftwareFile.FileVersion > '6.00.2800.1106' OR
                      v_GS_SoftwareFile.FileVersion = '6.00.2800.1106') AND (v_FullCollectionMembership.CollectionID = 'sms00001' )
ORDER BY v_GS_SYSTEM.Name0

MS has this KB article. It use to have one that checked the version of the SHDOCVW.dll
I can not find the KB for that anymore. All i can find is this:
http://support.microsoft.com/kb/164539

Edited:

Here is the KB article that explains the DLL Versions.

http://support.microsoft.com/kb/969393

Determine the version of Internet Explorer by using the Shdocvw.dll file:

For Internet Explorer 3.0 through 6.0, the browser is implemented in the Shdocvw.dll (Shell Document Object and Control Library) file. You can use the version of the Shdocvw.dll file to determine the version of Internet Explorer 3.0 through 6.0 that is installed on your computer. To determine the version of Internet Explorer 7, you must use the version of Iexplore.exe. To do so, follow these steps:

1. Click Start, point to Find, and then click Files Or Folders.
2. In the Named box, type shdocvw.dll, and then click Find Now.
3. In the list of files, right-click the Shdocvw.dll file, and then click Properties.
4. Click the Version tab.
5. Repeat steps 2 through 4, but in step 2 type iexplore.exe. If the version of Iexplore.exe is 7.x, then Internet Explorer 7 is installed. Use the table of Internet Explorer versions earlier in this article to compare the version number to released versions of Internet Explorer 7.

This table lists the different versions of the Shdocvw.dll file and the corresponding versions of Internet Explorer.

I’ve updated the Heath check startup script to allow for the upgrade to SP2.

With the help of others we have also fixed some issues that were found.

'================================================================
'
' NAME: SCCM_Client_Health_Check
'
' AUTHOR: Chris Stauffer, Commonwealth Of Pennsylvania
' DATE  : 12/17/2009
'
' COMMENT: Version 1.7
'
' 1.0 - all features enabled
' 1.1 - additional Credit Given
'      - Minor error in one of the email functions was fixed.
' 1.2 - Script was modified to run as a Startup script
'      - Email Function was disabled
'      - If SCCM Reg key is missing it will now trigger a client install
'      - Client install source points to the SCCM Site Share  SMS_(Sitecode)\Client\CCMSetup.exe
' 1.3 - Removed Advertisement check that was used in original health check advertisement script.
'
' 1.4 - Fixed service check thanks - Trevor Sullivan
' 1.5 - added support for SCCM 2007 SP2
' 1.6 - Fixed Version check -- Thanks to Paul Strain
' 1.7 - Fixed other bugs associated with version check and cleaned up script
'
' Features To be added:
'        - Do we actually need augments For client install since they should be In AD If site Is constructed properly
'        - WMI Solution
'
'***********************************************************************************
'***********************************************************************************
'  Special Thanks to:
' 1E And Richard Threlkeld  For the original Health Check tool
' David Turner For cache expander Function
' DudeWorks For script functions from their original Health Check scripts
' Sherry Kissinger For Error checking And Function editing
' Authors of SMS 2003 Recipes (a must have book For any SMS admin)
' My beta testers. I've been asked by some to not mention there names so I will not.
' The rest know who they are and I will gladly give them recognition if they want it.
' The guys And gals On the MyITForum MSSMS list For chiming in when needed
' And anybody Else that added their 2 cents :-)

'
'===========================================================
'===========================================================

This script was designed to help SCCM admin fix machines that are failing the install due to some network issue.

'===============================================================

'

' NAME: Client Network check

' AUTHOR: Chris Stauffer

' DATE : 12-17-09

'

' Description

' This script is designed to check a list a machines that are missing the SCCM client

' It will check the following:

' 1. Does it ping

' 2. If it pings does is the same name come back when you run nbtstat-a

' 3. If the same name is returned can you connect to Admin$

' 4. If you can access Admin$ is the needed SCCM admin present?

' 4. If all tests passed install client with the Health check startup script

' Note: this is do just as a precautionary step you could just trigger CCMSetup.exe

'

' Once the checks are done if the machine passes the test it continues in the script.

' If it fails it is put into a log for later remediation either by another script Or

' by some other solution yet to be determined.

'

' COMMENT: Version 1.14

'

' Version Notes:

' Version 1 -- Got all tasks working and figured out logic

' Version 1.1 -- added logging and separating out issues for easier resolutions

' Version 1.2 -- added headings to all 5 logs

' Version 1.3 -- added admin account check and repair if possible

' Version 1.4 -- Install client remotely if everything else passes

' Version 1.5 -- Redid logic for installing client and cleaned up some other things

' Version 1.7 -- Added NSLoopup check

' Version 1.8 -- Changed Client install method

' Version 1.9-1.12 -- cleaned up some logic

' Version 1.13-- Fixed Client install method and added some additional logic

' Version 1.14 -- Cleaned up some notes

'==============================================================

How to use the script:

Create a list of machines that you can not get the client to install on and put them in the machines.txt file. Then execute the script. It will scan each computer with your admin rights. If it finds problems it will attempt to resolve them. If it is able to resolve all of the issues then it will attempt to install the client.

Let me know if you find issues. This was beta tested by me in my environment but not in the real world.

Microsoft released 3 important upgrades for SCCM over the last several months.

It is recommended that you test these updates in a lab if possible.

SCCM 2007 upgrade Installation Directions

Please install the upgrades in the following order:

1. Backup your SCCM Server
2. Disable Mcafee AV (or what ever AV you are using)
3. Install WSUS 3.0 SP2
1. Instructions not included, this is a simple next, next, next, install.
2. Close the configuration console when it open
3. Let the server rest for about 15 min
4. This will allow the server to finish updating things in the background once the installation is completed
5. Install SCCM 2007 SP2
   1. Instruction Directions Included in a separate Document
6. Let the server rest for about 15 min
   1. This will allow the server to finish updating things in the background once the installation is completed
7. Reboot System
8. Install MDT 2010
   1. If you are not using OSD to deploy your images you do not need to install MDT 2010.
   2. If you are using OSD with MDT integration you will need to update and integrate the new MDT 2010. This will add support for Windows 7 and Server 2008 R2.
9. Re enable Mcafee AV

Note: if you modified your Mof files be sure to reapply your changes.

Attached are documents for running the SCCM upgrades

This topic has been covered before but i wanted to publish a copy here incase i cant find it again.

Just remove the XXX extensions from the attached zip file

Then create a single collection with these 3 query's

Dup guid 1

select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client from SMS_R_System join SMS_GH_System_System on SMS_R_System.ResourceID = SMS_GH_System_System.ResourceID where SMS_R_System.Name <> SMS_GH_System_System.Name

Dup guid 2

select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client from SMS_R_System join SMS_G_System_System on SMS_R_System.ResourceID = SMS_G_System_System.ResourceID where SMS_R_System.Name <> SMS_G_System_System.Name

Dup guid 3

select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client from SMS_R_System where SMS_R_System.ResourceID  in (select SMS_GH_System_System.ResourceID from SMS_G_System_System join SMS_GH_System_System on SMS_G_System_System.ResourceID = SMS_GH_System_System.ResourceID where SMS_G_System_System.Name <> SMS_GH_System_System.Name)

Then simply advertise the package to them.