ISS Shared Configuration can cause catastrophic issues in IIS Management if the child servers' setup differs from the primary server's.

Using Shared Configuration in IIS can, at times, cause the following error.

We will examine a server hosting many websites. When you use the Shared Configuration, one or more of the following are true.

• #1a: A website is [Stopped] on the primary server but is [Started] on the child servers.
• #1b: A website is named differently on the primary server than on the child servers.

#1a: Click on the [Sites] folder in the troubled child server.
Select the site which is disabled on the primary server.
On the right panel

• Under [Manage Website]
• Click [Stop]
• Next, [Restart] IIS

#1b: Click on the [Sites] folder in the troubled child server.
Select the site that has the naming issue,
On the right panel

• Under [Manage Website]
• Click [Restart]
• Next, [Restart] IIS

#1b should not be causing an issue; the shared config should update the site name to match the primary server, and that site should automatically start working. However, it seems that is not the case. I will research this issue and post an update to this KB Article when information becomes available.