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)
2-disable shared config on a node
3-install the extension on that node
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\ )
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
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
HTH
Steve Schofield
Windows Server MVP - IIS
http://weblogs.asp.net/steveschofield
http://www.IISLogs.comLog archival solution
Install, Configure, Forget