IIS7 doesn’t monitor changes across symlinks

I found the solution at this link on the iis forums

You can put the configuration in location tags in applicationhost.config rather than in web.config file - by doing something like this from the command line:

%windir%\system32\inetsrv\appcmd.exe set config "MySite1" -section:system.webServer/defaultDocument -+files.[value='newdoc.aspx'] -commitpath:apphost

• MySite1 is the friendly name of the site in IIS (the site name you see in the tree on the left)
• newdoc.aspx is the name of your default document for that site (you can specify a querystring)

So for the example that I posted above, I ran this command for each of my sites

%windir%\system32\inetsrv\appcmd.exe set config "MySite1 - www.site1.com" -section:system.webServer/defaultDocument -+files.[value='Connect.asp?CompanyID=425'] -commitpath:apphost

and

%windir%\system32\inetsrv\appcmd.exe set config "MySite2 - www.site2.com" -section:system.webServer/defaultDocument -+files.[value='Connect.asp?CompanyID=426'] -commitpath:apphost

When you go to the default document program for the 2 sites in the IIS7 management program, you will see the different default documents set for the 2 sites.

Your concerns are valid and at the end of the day you will either have to assess each reward with its inherit risks.

Shared Content is great; but as you pointed out you then have a dependency on a remote host, and clustering storage technologies isn't cheap or simple. This type of setup has its place, and given your current solution I assume you aren't looking for a 99.999% uptime solution.

Have you thought about extending your script to disable load balanced nodes (at the firewall) during times when you sync content from Web1 > Web2?

Shared Config is great though, and uses a local cache copy if your UNC share is unavailable, and is a great way of ensuring web apps have the correct configuration.

My 2c's