Can't upgrade to R3
Hi, I can't upgrade to R3. I keep getting error message saying that Microsoft System Center Configuration Manager 2007 R3 requires Configuration Manager 2007 QFE KB977384. I downloaded this and installed http://support.microsoft.com/kb/977384 but I still get the error message. Please help. Thanks
October 19th, 2010 7:49am
I have the exact same problem. All clients are on version 4.00.6487.2000 and so is the server with SP2 insatlled. I was able to install the hotfix on the server and have it automatically setup the program and advertisement for deploying. About 80% of the clients get error "This hotfix does not match the installed language version of Configuration Manager 2007". About 20% of he clients are able to install the update without a problem. All the clients were deployed directly from the server using command line. Anyone know what the deal is with this? -Matt
November 4th, 2010 12:40pm
Just kick off the patch (taken from the package that was created automatically) manually on the client and see if there's something useful in the installation logfile.
November 4th, 2010 12:50pm
It's weird. The log shows that it installed succesfully but if I try to remove it through add/remove programs I get the same error, "This hotfix does not match the installed language version of Configuration Manager 2007". Then the entry in add/romove programs goes away. I don't know if it's really installed correctly and if it is, if it was really removed after the error testing the removal. Any ideas? -Matt
November 4th, 2010 1:51pm
Hello Matt, I had the same error when trying to install the downloaded SCCM2007-SP2-KB977384-ENU.msi patch. Then I extracted the sccm2007ac-sp2-kb977384-x86-enu.msp patch out of it and was able to install it with no problem on the client computers. The msi patch itself installed for me fine on the SCCM site server. Hope this helps, Hristo
November 11th, 2010 2:05pm
I can confirm that Hristo's resolution works... extracting the MSP file from the MSI.. I really don't know why Microsoft have packaged up the MSP in the first place to be honest... Can anyone shed any light here? It seems as though the MSI is incorrectly configured. Interestingly (slightly) is that when the MSI is invoked, the 64Bit version of msiexec launches, however when the MSP is invoked the 32Bit version of msiexec is launched, so perhaps the fault with the MSI is related to OS architecture??? I used the following to extract the MSP file: msidb /d "SCCM2007-SP2-KB977384-ENU.msi" /x patch.cab N.B. MSIDB is part of the Windows Installer SDK This will extract the cab file which you can then extract sccm2007ac_sp2_kb977384_x86_enu_msp from the CAB file and simply rename this to sccm2007ac_sp2_kb977384_x86_enu.msp To apply the MSP I used the following commandline: msiexec /q /norestart /update sccm2007ac_sp2_kb977384_x86_enu.msp Hope that this helps someone else in deploying this apparently badly engineered MSI!
December 1st, 2010 4:45am
SCCM2007-SP2-KB977384-ENU.msi ... sccm2007ac_sp2_kb977384_x86_enu.msp There is usually no need to extract the msp from the msi manually. Installing SCCM2007-SP2-KB977384-ENU.msi on the siteserver will create a new ConfigMgr package that contains sccm2007ac_sp2_kb977384_x86_enu.msp. SCCM2007-SP2-KB977384-ENU.msi is not intended to be installed directly on the clients.
December 1st, 2010 6:12am
Hi Torsten. Thanks for the reply, but your statement seems to contradict the hotfix information at the following link: http://support.microsoft.com/kb/977384 Here it clearly states that the hotfix is also intended and required for Client computers, and significantly: Note The power management function of System Center Configuration Manager 2007 R3 does not work on System Center Configuration Manager 2007 SP2 client computers if this hotfix is not installed. So, if we are not supposed to extract the MSP and the MSI hotfix isn't installing on SCCM clients, how are customers supposed to get the hotfix applied, are you saying that we need to perform a new client push from the site server or a new scripted\GPO based re-install of the client? Or that the clients will perform a self update when they clock in to the upgraded infrastructure. IMO this is poor, why should a client reinstall be required to enable a few classes in WMI? Why haven't Microsoft supplied a hotfix that will actually install correctly? This appears to be a significant problem and many customers have reported failure of the installs.. I have a side note in my previous post. It appears as though I am actually unable to create a package in SCCM with the command line I specified for the MSP. The MSP does install correctly, however the status messages reported back into SCCM are 10021 - Program Failed (unexpected restart) however the program configuration is set to suppress the reboot, and the 'After Running' option is set to "Program Restarts Computer" (although I have also set this to "No action required" with the same result). I am presuming that this error is produced as the Client is restarted as the machine doesn't actually reboot, although don't have any technical proof of this. It still appears to me as though there is a problem with the entire "hotfix" process and there is certainly no clear and\or conflicting documentation about how to upgrade! This is certainly poor from my personal perspective as I have spent quite some time persuading my client of the benefits of implementing SCCM from the Altiris solution and after having the system in place and operational for a few months, there is an update that gives my client some potential cost savings which we are unable to deploy! Here is the upgrade information from the new CHM file from the R3 iso. Configuration Manager 2007 R3 System Requirements Primary and secondary site servers in the hierarchy, remote Configuration Manager consoles, and remove providers must install the update described in Article 977384 (http://go.microsoft.com/fwlink/?LinkId=199896) at the Microsoft Support site before you install Configuration Manager 2007 R3. Other than the hotfix, Configuration Manager 2007 R3 does not introduce significant changes to supported site system and client requirements from those required for Configuration Manager 2007 R2 and Configuration Manager 2007 SP2. Configuration Manager 2007 R3 Client System Requirements To use power management in Configuration Manager 2007 R3, you must first install the update described in Article 977384 (http://go.microsoft.com/fwlink/?LinkId=199896) at the Microsoft Support site to client computers in your organization. Other than the hotfix, the Configuration Manager 2007 R3 client requirements and supported operating systems are the same as the Configuration Manager 2007 SP2 client requirements. For more information about client requirements, see Configuration Manager 2007 SP2 Supported Configurations.
December 1st, 2010 6:41am
There's no need to reinstall the client. Just use software distribution to distribute the hotfix (that is included in the package that is automatically created when installing it on the siteserver) to them. There's just no need to *manually* extract the .msp as this is done automatically for you. I can't see conflicting information between my statement and the text you quoted. The ConfigMgr client gets upgraded and the service is restarted during that process. That's why you will see the message that the client was rebooted. The auto-created package takes care of that by using status mif files. See also http://blogs.msdn.com/b/shitanshu/archive/2010/05/04/part-1-configuration-manager-r3-beta-deployment-in-microsoft-it.aspx for further details.
December 1st, 2010 7:07am
Hi Torsten, Not really wanting to get into a bun fight here I wasn't targetting my post directly at your statement, but you did state that the hotfix MSI is not intended to be installed directly on clients, but the hotfix article and the SCCM CHM for R3 both state that it is. To me, that is a conflict of information ;¬) Perhaps I was not clear about my scenario: I haven't actually gone through the R3 upgrade on the site server, just installed the hotfix in preparation for the upgrade. Installing the hotfix on the site server(s) does not appear to create a package containing the MSP file for client installs (well at least not from what I can see by querying the DB for packages created on the date of the installation of the hotfix, nor running the inbuilt Status Message Query for "Packages Created, Modified or Deleted"). I also do not see any MSP in the client installation source "Program Files (x86)\Microsoft Configuration Manager\Client\" Perhaps you can point me in the right direction here? Basically I want to deploy the MSP\Hotfix to my clients before I upgrade the site servers so that I know that there will not be any issues with having the new features available immediately and that the clients will have all the pre-requisites defined in the documentation. Even applying the MIF information to my MSP package (by pointing it to the MSI) still generates the false negative "Program Failed (unexpected restart)". Can of worms springs to mind!
December 1st, 2010 7:49am
See http://blog.coretech.dk/confmgr07/error-extracting-files-from-kb977384/. It seems that the hotfix installer sometimes fails to create the package/program. See also http://myitforum.com/cs2/blogs/bgharbi/archive/2010/10/30/part-i-how-to-install-configuration-manager-r3-package.aspx. It does show you the process of installing the hotfix on the siteserver and the automatic creation of the ConfigMgr package.
December 1st, 2010 8:02am
Thanks Torsten, useful links :¬) Amusing that the first link is pretty much what I posted up earlier (with exception of doing an admin based extract via msiexec) ;¬) Perhaps the failure of package creation is related to 1 or both of the following? 1: AV (Trend is mentioned on a number of posts) is blocking something (I can't prove this as our AV is McAfee, however I did disable this prior to installing the MSI). 2: The MSI is installed via commandline with the /q /norestart options (this is certainly how I installed). When I have run the MSI manually, I do see the package creation wizard, and I have gone through this and am currently testing deploying the "generated" package and program (although on the face of this looks exactly the same as the manual package\program I have already created). This hotfix is screaming BUG to me!!
December 1st, 2010 8:45am
Thanks Torsten, useful links :¬) Amusing that the first link is pretty much what I posted up earlier (with exception of doing an admin based extract via msiexec) ;¬) Perhaps the failure of package creation is related to 1 or both of the following? 1: AV (Trend is mentioned on a number of posts) is blocking something (I can't prove this as our AV is McAfee, however I did disable this prior to installing the MSI). 2: The MSI is installed via commandline with the /q /norestart options (this is certainly how I installed). When I have run the MSI manually, I do see the package creation wizard, and I have gone through this and am currently testing deploying the "generated" package and program. Although on the face of this looks exactly the same as the manual package\program I have already created manually with the following exceptions: commandline of generated package: msiexec.exe /p sccm2007ac-sp2-kb977384-x86-enu.msp /L*v %TEMP%\sccm2007ac-sp2-kb977384-x86-enu.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous So basically has configured the MSP to forcibly re-install all components and provided a verbose log file location. I still can't see how the MIF is working for this package though as there is nothing entered for the Windows Installer tab!! This hotfix is screaming BUG to me!!
December 1st, 2010 8:45am
This is my scenario: I installed KB977384 - Software Update for ConfigMgr 2007 SP2 (KB977384) as I installed it (manually) in my primary site it created the package called KB977384 - Advanced Client Hotfix - <Site Name>, I distributed this package to my my test collection and showed as completed sucessful, check the ConfigMgr Client and it notice it changed the client version from 4.00.6487.2000 to 4.00.6487.2157 . as I deploy the task to my secondary sites, I also received the success status, the configMgr client showed 4.00.6487.2157 but when I try to install ConfigMgr R3(SW_DVD5_Sys_Ctr_Config_Mgr_Svr_2007_R3_English_MLF_X16-29339) I received the error "Microsoft System Center Configuration Manager 2007 R3 requires Configuration Manager 2007 QFE KB977384" so I did a little browsin' and I came across this post. The Fix: I extracted the files: msiexec /a "SCCM2007-SP2-KB977384-ENU.msi" /qb TARGETDIR=C:\SCCM_KB977384\ after this I ran msiexec.exe /p sccm2007ac-sp2-kb977384-x86-enu.msp /L*v %temp%\R3_Hotfix_Installation.log /q REINSTALL=ALL REINSTALLMODE=mous FSP=<Site Name> Thanks: Hristo and BlUNt
December 1st, 2010 8:49am
To clarify: On site systems or other systems where you want to install R3 (i.e. admin servers with ConfigMgr console) you should install the full hotfix KB977384. On computers only acting as clients you should use the msp automatically created, or extracted as mentioned above.
January 29th, 2011 8:52am