You are browsing the archive for MMC updates.

App-V : Sequencing the SCCM 2007 Console ( howto )

1:00 pm in AdminUi, AppV, ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, Installation, MMC updates, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 SP2, sccm2007, Virtual machine by Kenny Buntinx [MVP]

More and more customers are demanding a swift and easy install of the SCCM console , especially when it comes to upgrade your consoles when a new service pack comes along.

As my customers also have App-V in the house , witch is part of MDOP 2009 by the way , I was also interested to make the console virtualised.

After a few rounds of trying , I did not succeed in creating a virtualized SCCM console as an App-V package

Therefore , I want to explain to you all how to do it . But I couldn’t have done it without the help of Richard Ruiz from MSFT and a blog post on the technet forums.

Prerequisites : To make it yourself easy , please prepare a blank machine ( base XP SP3 with latest software updates ) into a virtualized world where you can use snapshots and revert to the original state as much as you want . I will save you an enormous amount of time.

Procedure :

1. Install all prerequisites (e.g. MMC 3.0, etc.) and your SCCM 2007 SP2 Console natively on your clean WinXP SP3 workstation, to the exact location you will be sequencing to. In this example we used D:\SCCMSP2 (stick to the 8.3 format)
2. Export the following keys and save them to a central location:

  • [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{6de537a5-7a1c-4fa4-ac3a-1b6fc1036560}]
  • [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{a77b774c-ce32-4ab0-982a-6bb3c078e5c1}]
  • [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ConfigMgr\AdminUI\QueryProcessors\WQL]

3. Turn Off your virtualized machine and delete all changes made (VHD) or if you use a physical machine , reimage your sequencer to a clean state. 
4. Install your App-V Sequencer and create your folder D:\SCCMSP2 (used in our example)
5. Install all your prerequisites for your SCCM 2007 SP2 Console (e.g. MMC 3.0, etc.) natively 
6. Start your sequencer and when you reach the “begin monitoring” and the sequencer flips to the background , start installing your SCCM 2007 SP2 Console in the previous defined path (in this case D:\SCCMSP2).

7. You could if you want install additions such as the famous “SCCM Right click tools” from Rick Houchins at

8. If you have R2 , install R2 to the same folder , ae D:\SCCMSP2

9. After your installation is complete  and before you stop monitoring, import the 3 previously exported registry keys. 
10. Launch the Console and test functionality, then complete the installation.If you have installed the right click tools , you also need to test all functionallity ! 
11. During the Application Wizard, ensure the shortcut exe path is set to the Q: or adapt the VFS path as necessary and launch the MMC to test functionality at this phase.
12. Finish the sequence and save it. 
13. Modify the OSD to include the following dependency:

———————–code snippet——————————————
echo off \n
copy /y %SFT_MNT%\<Replace with Asset Dir>\VFS\CSIDL_WINDOWS\WinSxS\Manifests %windir%\WinSxS\Manifests \n
xcopy /S /y %SFT_MNT%\<Replace with Asset Dir>\VFS\CSIDL_WINDOWS\WinSxS\Policies %windir%\WinSxS\Policies \n

———————–code snippet——————————————

14. Publish your APP-V sequenced SCCM console  and test the functionality on your App-V Client.

Hope it Helps ,

Kenny Buntinx

MMC updates for configuration manager (Software updates) Warning

10:13 am in AdminUi, ConfigMgr, ConfigMgr 2007, kb940848, MMC updates, prerequisite checker, sccm, SCCM 2007 by Kenny Buntinx [MVP]

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.



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:


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.



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:



Notice the the MMC updates line is gone, problem fixed.