IIS 7 and Above
How to install the Administration Pack when Shared Configuration is t...
Last post Aug 02, 2009 02:07 AM by jimrPA
Apr 28, 2009 12:12 PM|dlowe69|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.
Apr 29, 2009 06:07 AM|steve schofield|LINK
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.
Windows Server MVP - IIS
Log archival solution
Install, Configure, Forget
May 03, 2009 11:45 PM|steve schofield|LINK
Here are some ideas that came from a few gurus.
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.
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
May 05, 2009 05:17 AM|dlowe69|LINK
Thanks for your replies to my post, they were very helpful.
Aug 02, 2009 02:07 AM|jimrPA|LINK
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.