How to install the Administration Pack when Shared Configuration is turned on? RRS feed

  • Question

  • User-798375457 posted


    This link:


    Issue:  Cannot install Administration Pack when Shared Configuration is turned on

    Seems to Indicate that there is a workaround to this issue that can be found on http://www.iis.net.  Is there a workaround?  I can't find it.




    Tuesday, April 28, 2009 12:12 PM

All replies

  • User1073881637 posted

    I don't think you'll be able to install while Shared configuration is enabled.  You'll need to take a machine out of shared configuration, install the component, export the shared configuration.  I'm checking with the IIS team and see what they say about the article link, it is not clear.

    Wednesday, April 29, 2009 6:07 AM
  • User1073881637 posted

    Here are some ideas that came from a few gurus.

    1-copy the shared config files (say \\server\share\configurationv1\*) back to the local machine \windows\system32\inetsrv\config folders (so you have the latest config locally, including schema)

    <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>
    <o:p></o:p>2-disable shared config on a node

    3-install the extension on that node<o:p> 

    4-create a new folder on the shared config file share with for the new version of config and copy the updated local config files to this share (for example \\server\share\configurationv2\ )<o:p> 

    5-re-enable shared config against the new version of configuration

    6-on subsequent nodes you can skip step #1 and #4, simply disable shared config, run the installer (so the binaries get placed on disk) and then point the machine at the new version of shared config<o:p> </o:p>

    BTW, this process also works for staging config changes across a shared configuration farm.  The obvious way to update shared configuration for a Web farm is to edit the shared configuration file directly, and all machines will automatically pick up the configuration change and apply it at the same time.  But if you want to stage configuration changes for some reason, you can create a new version of shared config in a separate folder, as described above and then just change the \\windows\system32\inetsrv\config\redirection.config file on each node to point to the new config – file change notification on this file will kick in and refresh the node’s configuration.

    Another idea.

    a)      Take one server out of the pool (use local config)

    b)      Update the binaries on that server

    c)       Publish that shared config to a new folder on the shared server (e.g. a “v2” folder)

    d)      Change the server to use the newly published shared v2 config

    e)      Repeat steps (a), (b) and (d) for every other server in the pool

    Thanks to Bill Staples, Scott Forsyth and Ken Schaefer


    Sunday, May 3, 2009 11:45 PM
  • User-798375457 posted

     Hi Steve,

    Thanks for your replies to my post, they were very helpful.


    Tuesday, May 5, 2009 5:17 AM
  • User-1757254373 posted

    Just note that the web installer and the direct download link on MS's webpage installs different versions into the assembly folder. This makes it tricky when adding nodes in or thinking about R2 upgrading. Make sure the correct version is being used in the administration.config file else it will not load the module.

    Sunday, August 2, 2009 2:07 AM