Partager via

Sequencing the Microsoft System Center Configuration Manager Admin Console

  • Article

This seems to be a relatively popular question so I thought I'd post a quick heads-up here in case you're thinking about trying this in the future.  If you want to virtualize the ConfigMgr 2007 admin console then follow these steps:

========

1. Install all prerequisites (e.g. MMC 3.0, etc.) and SCCM 2007 Console natively on your clean WinXP workstation, using the same install path as you'll use when sequencing.

2. Export the following keys and save 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 and Delete all changes (VHD) or Reimage your sequencer to a clean state if you're using a physical sequencing computer.

4. Install the Sequencer

5. Install all prerequisites for ConfigMgr 2007 Console (e.g. MMC 3.0, etc.) natively on the sequencing computer.

6. Start your sequence. While monitoring, install the ConfigMgr 2007 Admin Console. After installation is complete, before you stop monitoring, import the 3 exported registry keys you created in step #2 above.

7. Launch the Console and test functionality, then complete the installation.

8. During the Application Wizard, ensure the shortcut executable path is set to the Q: drive or the VFS path as necessary and launch the MMC to test functionality at this phase.

9. Finish the sequence and save it.

10. Modify the OSD to include the following dependency:

<DEPENDENCY>
<SCRIPT TIMING="POST" EVENT="STREAM" PROTECT="TRUE" WAIT="TRUE" TIMEOUT="0">
<SCRIPTBODY LANGUAGE="Batch">
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
</SCRIPTBODY>
</SCRIPT>
</DEPENDENCY>

11. Publish the sequence and test the functionality on your SoftGrid Client.

*NOTE: All prerequisites need to be installed natively on the clients as they were on the sequencer prior to sequencing.

Cesar Nunez | Manageability Support Engineer

Comments

  • Anonymous
    January 01, 2003
    I'm curious as to what that OSD edit is doing exactly. I haven't added this part yet. Have you tried this on Server 2003 with TS / Citrix? I sequenced it pretty much as you said, on a 2K3 virtual machine with TS installed, since we deploy our Citrix apps through App-V. I can run the application just fine. Another tester can run it, but it ends up generating a whole load of Event ID 577 in the Security log and pulling about 50% CPU. Lookups on this pull up articles about Windows XP before SP2. Any ideas? I'm going to try and give him local admin rights to see if that resolves the issue, but that will not even be used as a work around, just a troublshooting step. -jon

  • Anonymous
    January 01, 2003
    http://blogs.technet.com/softgrid/archive/2008/05/21/sequencing-the-microsoft-system-center-configuration

  • Anonymous
    January 01, 2003
    Thank YOU! I was able to sequence the console install for SCCM 2007 R3 (including the right-click tools) in our App-V 4.6 SP1 environment using this post. Very helpful!

  • Anonymous
    January 01, 2003
    What about sequencing for Windows 7?  The <scriptbody> seems to get access denied and the console fails with: MMC cannot initialize the snap-in.

  • Anonymous
    December 03, 2010
    Are these steps also needed for system Center Service manageR?