sccm先决条件检测,MMC更新一项安装了相应的补丁仍提示报警存在,问题在于热修复程序中将相关键值的字符写为KB940848-v3 ,而先决条件检测时检测的是KB940848,在注册表中修改相关项即可。
 
下载附件,解压,编辑,把所有的KB940848-v3 替换为KB940848,保存,导入注册表,OK!
 
原文: 
 
 
 
Hi all,
Would you like to install Configmgr 2007 for once with a complete clean Pre-requisite checker? Do you want to eliminate all warnings?
Has this dreaded MMC updates for configuration manager warning been there for every sccm installation you do? Read on to learn, what is going on, and how to fix it.
The message is reportedly fixed by installing software update KB940848, which you can find here:
Issue 1: There are 2 server 2003 hotfixes with this kb article per processor architecture, the SP2 version is part of SP2 and hence applies to Windows Server 2003 SP1 machine. The SP3 version will be part of SP3 when it gets released, and hence applies to Windows Server 2003 SP2 machines.
Now even after you run this update and re-run the check, you still see this line in the prerequisite checker.
mmcupdatewarning01
 
Additionally you'll have the following line in your configmgrprereq.log:
Failed to connect to registry for KB940848 with 203.
What is going on here? Do I need to reboot? Nope, the reboot isn't needed and doesn't fix the issue. Let's re-run the check and use process monitor to investigate what is going on.
If you re-run the check this is what process monitor shows you:
mmcupdatewarning01.5
NAME NOT FOUND on HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB940848.
Odd, I installed the update just fine, and it does appear in add/remove programs, although it shows with a -V3 attached.
Let's search the registry ourselves, and lo and behold the key indeed does not exist, yet a very similar key with -V3 attached does exist.
mmcupdatewarning02
 
Turns out that the pre-requisite checker is looking in the wrong spot. Ok, now let's fix this, I exported the registry to a .reg file, which you can find attached to this post. Modified it to write to KB940848 instead of KB940848-V3. I subsequently re-imported that reg file. and if we re-run the check after that we get this:
mmcupdatewarning05
 
Notice the the MMC updates line is gone, problem fixed.