Installing IIS Modules in Shared Configuration Environments

by Walter Oliver


This article describes the steps to install an IIS Module in machines that are part of the Shared Configuration environment. The following process assumes n servers using a common shared configuration. Since Shared Configuration requires that all web servers are running the exact IIS configuration modules, it is important to maintain such requirement throughout the update process. This articles describes the installation process in detail.


Step 1 - Turn off any site provisioning and management automation

If you are using an automated system for provisioning and/or managing web sites, you need to turn it off. The reason is that changes to the shared configuration files should be stopped during the Module installation process. Refer to your site provisioning system to accomplish this step.

Step 2 - Remove server 1 from the load balance solution

The steps to accomplish this step varied depending on which technology you are using for Load Balancing.
For Network Load Balancing review the documentation at:
For Application Request Routing see:
For any other solution (including hardware) see the manufacturer's provided documentation.

Step 3 - Remove server 1 from the shared config and backup the configuration locally.

This is accomplished through the IIS Manager UI and Command line prompt. See article for details.

Step 4 - Install the IIS Module in server 1

Install IIS modules manually.

Step 5 – Export the configuration from server 1 to a new shared configuration location

Once server 1 has all the new modules installed, export its configuration to a new shared config location. All subsequent server will point to this new location as they get updated.

Step 6 – Enable Shared Config in server 1

Now that the server's configuration has been exported to a new location, the server can point to that configuration.

Step 7 – Add server 1 to the Network Load Balancing solution

The newly updated server can now join the set of servers under load balancing.

Step 8 – Apply changes to each subsequent server as follows:

  1. Repeat Steps 2, 3, 4, 6 (skip step 5).
  2. Point the server to the new Shared Config location created in step 5.
  3. Repeat Step 7.

Step 9 – Restore the site provisioning and management automation system

Once all servers are pointing to the new shared configuration created in step 5, you can restore normal operations of the provisioning and management system.

Step 10 – (Optional) Clean up the old shared config location

You may want to have the file location ready for the new time a new module is installed. You may want to backup and delete the current content.


This article covers the steps required to install an new module in a set of Web servers using shared configuration.