> For the complete documentation index, see [llms.txt](https://docs.alemba.com/asm-gaia-10.4/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alemba.com/asm-gaia-10.4/setup-and-configure-asm/installation-and-upgrade/installing-and-upgrading-on-multiple-web-servers.md).

# Installing and upgrading on Multiple Web Servers

![](/files/d36Tpt1I4J38N5lU5Hwj)

To install Alemba Service Manager™ on more than one web server:

1. Install Alemba Service Manager™ on each web server.
2. Create and configure a new system on each of those servers, ensuring they all point to the same database.
3. On all but one of the servers, disable database upgrade:
   * In the registry key, disable the database upgrade using the registry string `SkipDatabaseUpgrade = 1`\ <br>

     <figure><img src="/files/tYt5syKx9psmSMikcYms" alt=""><figcaption></figcaption></figure>
4. &#x20;Disable each of the ASM polling services on all but one server:

* Stop the ASM service and set the "Start Up" property to **Manual**; except for the ASM Administrative Service.
* Ensure the ASM Administrative Service is running on all servers and its Start Up property is set to **Automatic**.
* <mark style="background-color:blue;">Services can be load-balanced. Set a service to Automatic on one server and Manual on all other servers. Each service should only be running on one server.</mark>

{% hint style="warning" %}
When **upgrading** in a multi-server environment, run the upgrade once only on the shared database. On the second and subsequent servers, select **No** if prompted to upgrade the database.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.alemba.com/asm-gaia-10.4/setup-and-configure-asm/installation-and-upgrade/installing-and-upgrading-on-multiple-web-servers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
