For the purpose of this article it is assumed a single Archive Manager 5.x server currently exists and hosts both the services as well as the first website. The configuration and any troubleshooting of load balancers will need to be directed to the load balancer vendor.
Ensure all prerequisites for servers that will only be running Archive Manager websites are met:
- Microsoft Internet Information Services (IIS) version 8.5, 8.0, 7.5, 7.0, or 6.0.
- For IIS 7.0 or later, certain role services are required to be manually selected and installed on the web
server in order for the Archive Manager Website to run correctly. These roles include:
1) Common HTTP Features
2) Static Content
3) ASP.net
4) ASP
5) Basic Authentication
6) Windows Authentication
7) IIS Management Tools and Scripts
8) IIS Management Console.
- Microsoft .NET Framework 4.0 and 3.5 SP1. Note: Reliability Update 2 for the .NET Framework 4 is
required and can be found at: http://support.microsoft.com/kb/2600217
On the servers that will host the additional websites uninstall any v4.x Archive Manager software and then delete any existing Archive Manager website within the IIS Manager.
.
Run the 5.0 installer and immediately after the Install Path screen you will be prompted for which components you want to install; 'Website' is the only option you should have enabled. Do not install any of the other features.
After you complete the file copy/setup configure the new website using the Configuration Console.
- Do not use the same 'Website name' for the second IIS webserver as the first IIS webserver. Every instance of IIS hosting an Archive Manager 5.0 website needs a unique name.
- By default the site is installed with the 'Website Name' of 'ArchiveManager'; name the second site 'ArchiveManager2' and the third site 'ArchiveManager3', etc.
- This does not affect the URL used to contact or access the website, that value is the 'Host Header'.