Hello ! I just tried to install SCCM 2007 R3 on my test site. R3 requires KB977384 as prerequesite but when I try to install it, I get an error : "This hotfix is not valid for this version of configuration manager" Is ICP2 still not supported ? Regards, Michel

Hi, I have seen this issue since the R3 beta version. The version of the ConfigMgr SP2 site server is 4.00.6487.2000, so when installing the ICP2 it changes to 4.00.6487.2700 (this info is stored in the "Full version" key under HKLM\Software\Microsoft\SMS\Setup) and for this reason you get the message error and actually I don't see any final solution for that. If you're trying to work with the R3 in a test lab, so you can install a ConfigMgr SP2 server without installing the ICP then test the R3. Otherwise, you can also open a case with Microsoft CSS.

Hello ! I just tried to install SCCM 2007 R3 on my test site. R3 requires KB977384 as prerequesite but when I try to install it, I get an error : "This hotfix is not valid for this version of configuration manager" Is ICP2 still not supported ? Regards, Michel Same problem here...Windows 7 rulez!

Hi Joop, Don't worry, as soon as possible I will update this thread when I recieve news.

Hi all, Actually the KB977384 is not supported on ConfigMgr with ICP. So you should wait until Microsoft provides a solution, otherwise you can always install the KB on ConfigMgr wSP2 but without ICP.

Thanks for your answers. There is now a blog post : http://scug.be/blogs/sccm/archive/2010/10/19/configmgr-2007-r3-installing-hotfix-prerequisite-kb977384-on-a-site-server-with-icp-pack-will-fail.aspx Still have to wait before using R3 :-(

I was able to install this hotfix on my primary server, but I am getting this same error when I try to install it on my other sites servers. Can I go ahead with the R3 install or will it cause problems?

You have to install that hotfix before installing R3. Which error are you getting and what ConfigMgr SP and ICP version are you using?

I am getting the following error: "this hotfix is not valid for this version of configuration manager 2007" And we are running SCCM R3. The site servers that can not install the patch have the following roles: S1: DP,FSP,SUP S2: OOBSP,DP,FSP These two site servers only service computers with english speaking people. Is there a way to remove the ICP or modify the registry in a non harmful way to get the patch to install?

These two site servers only service computers with english speaking people. Is there a way to remove the ICP or modify the registry in a non harmful way to get the patch to install? No way to remove ICP. You should wait until Microsoft provides a solution.Bechir Gharbi | http://myitforum.com/cs2/blogs/bgharbi/default.aspx

Ok, but dang.. I hate waiting. ______________________________ DanSpec | http://www.danspec.com

It's now avaible ! http://myitforum.com/cs2/blogs/bgharbi/archive/2010/11/12/configmgr-r3-what-about-kb977384-and-icp.aspx

It's now avaible ! http://myitforum.com/cs2/blogs/bgharbi/archive/2010/11/12/configmgr-r3-what-about-kb977384-and-icp.aspx Absolutly yes :)Bechir Gharbi | http://myitforum.com/cs2/blogs/bgharbi/default.aspx

I downloaded the new hotfix, but now on the same site servers Im still getting the following error: "This hotfix is not valid for this version of configuration manager 2007" ______________________________ DanSpec | http://www.danspec.com

I was finally able to get this patch to install. Neither of the hotfixes I downloaded would install. But it seems I remember someone on another thread somewhere was having problems installing this patch on site computers. So they used the msp that the installer creates on the main server. When I installed this hotfix on main server it ask to create a package, I did that and pushed it, and the patch installed. Be sure to read how to build the package! The default path for this hotfix is: \\servername\sms_sitecode\Client\hotfix\KB977384

Is there a special version of KB977384 other than this one?: http://support.microsoft.com/kb/977384 I still get the message: "This hotfix is not valid for this version of configuration manager 2007"

You can download 10 different versions (depending on the language and ICP1 / ICP2). Make sure you downloaded the version that matches your setup.

Is there a special version of KB977384 other than this one?: http://support.microsoft.com/kb/977384 I still get the message: "This hotfix is not valid for this version of configuration manager 2007" If the ICP is already installed, so you should download the right hotfix (for ICP 1 or 2) from the same link.Bechir Gharbi | http://myitforum.com/cs2/blogs/bgharbi/

Ahh. Of course. So used to select language based on OS language. Selected the ICP2 version of the package, and it works like a charm.

I am also experiencing this issue although with an additional variable. We were also fighting with an AI patch KB2444668 which increases the sccm client version to 4.00.6487.2161. It seems if you have ICP2 installed that raises your sccm client version to 4.00.6487.2700 and the R3 prereq is a lower client version so the upgrade never happens. After several days of trying all sorts of variations our team agreed to do away with ICP. we replaced the client install files with original R2 client files without any ICP updates and then created a collection to target all 4.00.6487.2700 clients. We ran a package to uninstall sccm from these machines and then forced a client push back to the original R2 version of sccm client 4.00.6487.2000. The patch applied properly and we can receive AI information now.

I am also experiencing this issue although with an additional variable. We were also fighting with an AI patch KB2444668 which increases the sccm client version to 4.00.6487.2161. It seems if you have ICP2 installed that raises your sccm client version to 4.00.6487.2700 and the R3 prereq is a lower client version so the upgrade never happens. After several days of trying all sorts of variations our team agreed to do away with ICP. we replaced the client install files with original R2 client files without any ICP updates and then created a collection to target all 4.00.6487.2700 clients. We ran a package to uninstall sccm from these machines and then forced a client push back to the original R2 version of sccm client 4.00.6487.2000. The patch applied properly and we can receive AI information now.