In the second phase of planning a web farm, determine what is needed to configure shared content and shared configuration. In addition, learn how to add web servers to your farm.
When you are done with these tasks, record your design decisions before going on to Step 3: Plan IIS Web Farm Load Balancing.
2.1. Plan for Shared Content
Network shared content uses a back-end file server to manage website content. All web servers point to a shared folder on the file server over a UNC path. To reduce the risk of failure, the file server is often mirrored to another server with some method of failover provided. For information about failover clusters, see Failover Clustering.
To configure shared content, you first set up the shared folder on the file server. Create a custom user for each application pool and assign that user to the shared folder. You can create local users and groups as long as the same username and password is assigned to each web server.
If your web farm supports ASP.NET applications, use the Code Access Security Policy tool (Caspol.exe) to grant ASP.NET approval for the UNC path. With the Caspol tool, you can grant full trust to the UNC path on your web server. The tool resides on your server at one of the following locations:
- 64-bit systems:
- 32-bit systems:
Run the tool by using either a system command prompt, a PowerShell command prompt, or a Visual Studio command prompt. For more information, see Step 2: Configure IIS Web Farm Servers.
2.2. Plan for Shared Configuration
Shared configuration is an IIS feature that helps support homogeneous web farms where all web servers share the same configuration. By using a UNC share, any changes to a master configuration file propagate across different servers without extra tools or programmatic support.
You enable shared configuration in two steps by using the IIS Manager.
- Export the configuration files to a shared folder on the back-end file server.
- Point IIS to the UNC path for that shared folder.
2.3 Plan to Add Web Servers
To add web servers to you farm, first use IIS Manager to set up shared configuration by pointing to the configuration UNC path. When you restart IIS Manager, the shared site or sites will be listed. If your web farm supports ASP.NET applications, run the Caspol tool on the new server.