locked
A custom MMC cannot create this snap-in error in XP RRS feed

  • Question

  • I am creating these custom mmc for delegated users that are producing the typical 'mmc cannot create this snap-in error'  The workstations are XP.  I do not want to install any of the adminpak tools on these machines hence why creating custom mmc's, but do I have to?  I know I am missing something big here, but don't know what it is.

    Wednesday, July 28, 2010 2:32 PM

Answers

  • Usually you end up having to install the snap-ins locally, but unless
    they have administrative permissions, then they will not be able to
    modify (and sometimes not be able to view) anything with the other
    snap-ins that are installed.
     
    Sometimes you can use software restriction policies to block MMCs by
    blocking the DLLs, but this can cause problems if there are dependencies.
     
    You could always create a custom MMC and serve it a as a Terminal
    Services RemoteApp,
     
     

    -- Mike Burr
    • Marked as answer by Tim Quan Tuesday, August 3, 2010 2:16 AM
    Thursday, July 29, 2010 10:28 PM

All replies

  • If the MMCs required by the console that you are creating are installed
    with the administration tools for Server 2003, then they would need to
    be installed on the user's desktop to use the console, otherwise the
    required DLLs and registry entries will not be present.
     

    -- Mike Burr
    Wednesday, July 28, 2010 3:41 PM
  • Then what is a better way to provide mmc's for AD administration.  Ideally I don't want them opening up the whole mmc especially seeing they won't have access to the entire AD structure?

    Do you just give them the AD tool or create custom mmc's and hide the AD tools somehow?

    Thursday, July 29, 2010 6:00 PM
  • Usually you end up having to install the snap-ins locally, but unless
    they have administrative permissions, then they will not be able to
    modify (and sometimes not be able to view) anything with the other
    snap-ins that are installed.
     
    Sometimes you can use software restriction policies to block MMCs by
    blocking the DLLs, but this can cause problems if there are dependencies.
     
    You could always create a custom MMC and serve it a as a Terminal
    Services RemoteApp,
     
     

    -- Mike Burr
    • Marked as answer by Tim Quan Tuesday, August 3, 2010 2:16 AM
    Thursday, July 29, 2010 10:28 PM