Just setting up load balancing and IIS Shared Configuration isn't all that is required to configure and manage a web farm effectively. The following few sections discuss other applicable technologies and how to configure them for your web farm.
Not everything will copy between servers as easily as the IIS Shared Configuration files or the web content. This section touches on a few things to keep in mind that DFS-R, Robocopy, and offline folders don't address.
If you use Secure Socket Layer (SSL) certificates on your web servers, they need to be installed on all the servers in a web farm. There are a couple of rules of thumb to note.
First, as long as the same certificate is installed on each server, then the shared IIS configuration will correctly use the right certificate, regardless of the server. As long as you ensure that this is true, you should be set, but there are some common misunderstandings about SSL certifications that are addressed here.
After you create a Certificate Signing Request (CSR) and send it to a CA, the certificate that the CA generates will work only on the server where the CSR was generated. You cannot apply the certificate from the vendor on any of the servers on the web farm except for the one that generated the CSR.
The solution is to go through the entire SSL issuing process on one of the servers on the web farm. After you have successfully installed the certificate on the one server, you can export ...