Avatar of DscpTech
DscpTech
 asked on

KB977384 not recognized by SCCM 2007 R3 installer

I am trying to upgrading the SCCM 2007 Console on a Windows 7 Enterprise x86 workstation from SP2 to R3. To do this, KB977384 must be installed first. Since I ran into trouble early on, I reinstalled the SCCM client on the workstation and upgraded it to R3 level, by using the following commands:

Ccmsetup.exe /uninstall (confirmed success in ccmsetup.log)
Ccmsetup.exe (confirmed success in ccmsetup.log)
msiexec.exe /p sccm2007ac-sp2-kb977384-x86-enu.msp /L*v %temp%\sccm2007ac-sp2-kb977384-x86-enu.msp.log REINSTALL=ALL REINSTALLMODE=mous (confirmed success in sccm2007ac-sp2-kb977384-x86-enu.msp.log)

Then I tried to upgrade the SCCM Console with this command:

msiexec.exe /I CONFIGMGR2007R3.MSI /l*v “%temp%\SCCMR3.log

I gives me a the error "R3 requires Configuration Manager 2007 QFE KB977384”.

But I confirmed that KB977384 *is* INSTALLED! Configuration Manager in Control Panel reports v4.0.6487.2157, which indicates that KB977384 is installed. Also, c:\windows\system32\ccm\compver.ini reports SMSPowerManagement=4.0.6487.2157, and c:\windows\system32\ccm\climsgs.dll shows v4.0.6487.2157.

Why isn’t the CONFIGMGR2007R3.MSI picking up on the fact that KB977384 is installed?
Here is the bottom of SCCMR3.log:

MSI (c) (04:00) [15:06:16:173]: Doing action: CheckForSP2QFE
Action 15:06:16: CheckForSP2QFE.
Action start 15:06:16: CheckForSP2QFE.
MSI (c) (04:00) [15:06:16:173]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'CheckForSP2QFE'
MSI (c) (04:3C) [15:06:16:219]: Invoking remote custom action. DLL: C:\Users\ha91898\AppData\Local\Temp\MSI98E8.tmp, Entrypoint: CheckForSP2QFE
[15:06:16] CheckForSP2QFE() started.
[15:06:16] CheckForSP2QFE() completed successfully.
[15:06:16] ERROR: Error code 25022 reported, hr = 0x80004005
Error 25022. Microsoft System Center Configuration Manager 2007 R3 requires Configuration Manager 2007 QFE KB977384.
MSI (c) (04!A8) [15:06:26:732]: Product: Microsoft System Center Configuration Manager 2007 R3 -- Error 25022. Microsoft System Center Configuration Manager 2007 R3 requires Configuration Manager 2007 QFE KB977384.
CustomAction CheckForSP2QFE returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 15:06:26: CheckForSP2QFE. Return value 3.
MSI (c) (04:00) [15:06:26:732]: Doing action: InstallErrorDialog
Action 15:06:26: InstallErrorDialog.
Action start 15:06:26: InstallErrorDialog.
MSI (c) (04:00) [15:06:26:732]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'InstallErrorDialog'
Microsoft Server OSWindows 7Microsoft Server Apps

Avatar of undefined
Last Comment
George Simos

8/22/2022 - Mon
Kezzi

Does your local console install have the sp2 applied to it as well?
DscpTech

ASKER
Yes, my SCCM local console was installed from the ConfigMgr 2007SP2 installer. The local console Help About says v4.00.6487.2000.
George Simos

Do you see the KB977384 installed in your "Programs and Features" control panel area?
If yes then i suggest to uninstall it along with the CM Client and the console and then install them in the correct order which is:
1) SP2 Client Installation
2) SP2 Console Installation
3) KB 977384 Installation
4) R3 Client and Console Installation

Also I would clean any remnants after removing the old client/console/patch and any registry entries related also.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
DscpTech

ASKER
Gsimos, KB977384 is not listed in Programs and Features. I’ve never seen it listed, even on a successful upgrade of the SCCM console to R3.

I followed your sequence anyway:

1) SP2 Client Installation
2) SP2 Console Installation
3) KB 977384 Installation. I did this with
msiexec.exe /p sccm2007ac-sp2-kb977384-x86-enu.msp /L*v %temp%\sccm2007ac-sp2-kb977384-x86-enu.msp.log REINSTALL=ALL REINSTALLMODE=mous
I confirmed that the Client now is at R3 level, since Control Panel Configuration Manager reports v4.00.6487.2188, and c:\windows\system32\ccm\compver.ini shows SMSPowerManagment=4.00.6487.2157, SMSSoftwareUpdate=4.0.6487.2188, CCMFramework=.2155, SmsInventory=.2184, SMSSoftwareDistribution=.2154, other components=.2000
4) Console upgrade. I did this with
msiexec.exe /I CONFIGMGR2007R3.MSI /l*v “%temp%\SCCMR3.log

But it still give me the same error
"R3 requires Configuration Manager 2007 QFE KB977384"
George Simos

Could you please attach those logs here?
Also could you try running the oh977384 just by double clicking it and report it's output please?
DscpTech

ASKER
Gsimos, see attached <<sccm2007ac-sp2-kb977384-x86-enu.msp.LOG>> and <<SCCMr3.log>>
sccm2007ac-sp2-kb977384-x86-enu..LOG
SCCMr3.log
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
DscpTech

ASKER
Gsimos, also you cannot simply run the kb977384 patch just by double clicking. It comes as an MSI which you install on the SCCM server, it creates a SCCM package that is supposed to run on each workstation with a command line that runs an MSP. You can run that command line manually instead of as an SCCM advertisement.

But KB977384 does not then appear as a software update under Programs and Features. The best I could figure out is that you know its installed if c:\windows\system32\ccm\compver.ini has an entry that says, SMSPowerManagment=4.00.6487.2157, and that c:\windows\system32\ccm\climsgs.dll shows v4.0.6487.2157. This is what my system shows.

The best post I've found on this topic is http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/a9976a22-0317-47e4-9f4f-f219d51baf77/, maybe you can get a clue from there, but I've exhausted all those ideas.
George Simos

DscpTech, I'm aware about the ways you can run an MSP file, I assure you that you can right click on it and choose "Install" from the context menu.
However your issue lies in the fact that you have already a console installed, you should install the same Patch that you've installed on the site server (the MSI one and not the MSP that it created automatically -along with the package for deployment-).
Try this and report back please :)
George Simos

Just a note about the MSP installation via right click in windows explorer, the context menu is "Apply" and not "Install" because it's a patch file applied by the windows installer service (or engine if you prefer).
Your help has saved me hundreds of hours of internet surfing.
fblack61
ASKER CERTIFIED SOLUTION
George Simos

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
DscpTech

ASKER
1) I uninstalled SCCM console and SCCM client
2) Installed SP2 Client
3) Installed SP2 Console
4) KB 977384 Installation using the link you gave me http://support.microsoft.com/kb/977384, I installed the MSI SCCM2007_SP2_KB977384_ENU.msi directly onto the Windows 7 workstation, and not the MSP sccm2007ac-sp2-kb977384-x86-enu.msp. After the install c:\windows\system32\ccm\compver.ini still shows v4.0.6487.2000 for all components. But KB977384 shows up in Program and Features under View Installed Updates.
5) Upgraded to R3 Client by right clicking sccm2007ac-sp2-kb977384-x86-enu.msp and choosing Apply. I did not do the SMS package line this time “msiexec.exe /p sccm2007ac-sp2-kb977384-x86-enu.msp /L*v %temp%\sccm2007ac-sp2-kb977384-x86-enu.msp.log REINSTALL=ALL REINSTALLMODE=mous”. Now compver.ini shows SMSPowerManagement=4.0.6487.2157, SMSSoftwareDistribution=4.0.6487.215, CcmFramework=4.0.6487.2155, other components still at .2000, Control Panel Configuration Manager reports 4.00.6487.2157.
6) Upgraded SCCM Console by running “msiexec.exe /I CONFIGMGR2007R3.MSI /l*v “%temp%\SCCMR3.log”. It worked without the error "R3 requires Configuration Manager 2007 QFE KB977384". Hurray!

So gsimos is correct when he says you need three things to upgrade your SCCM client and console to R3:

a) the KB977384 MSP to patch the SCCM client,
b) the KB977384 MSI as a prereq for upgrading the admin console,
c) then the CONFIGMGR2007R3.MSI to do the actual admin console upgrade to R3.

Great job, gsimos.
DscpTech

ASKER
SCCM Console Help About still says 4.00.6487.2000, but I’m pretty sure its at R3 level because when I click on Site Management > Site Settings > Discovery Methods > AD System Group Discovery > Polling Schedule tab, it displays the “Enable delta discovery” checkbox, which is a R3 feature per http://blogs.technet.com/b/justin_gao/archive/2010/01/19/what-s-new-in-configmgr07-r3.aspx.
George Simos

You're welcome DscpTech and thanks for accepting my solution!
I'm glad it worked out, I will blog this in my blog at http://gsimos.wordpress.com because there is a vagueness about those patches :)

Your console version is perfectly fine and as you noticed the R3 features are there :) Check also the site wide setting for "Power Management".

As you saw by yourself the client patch is not displayed in the control panel "Prorgams and Features" or "Add/Remove Programs" but this is not the case for the console/site server patch and this got me worried when you answered negatively.

It was a pleasure helping you out!
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.