> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/system-administration/installation/logicnets-installation-upgrade-system.md).

# LogicNets Installation: Upgrade System

## Description

Using the LogicNets installation script that you used to install the system on your local machines, you can also update the installation.

## Installation Steps

The installation script automatically updates the LogicNets run-time and components and leaves the existing companies untouched. To perform an upgrade, do the following:

1. Stop the IIS webserver before performing any upgrade steps. This is because some webservers lock files in the LogicNets installation.
2. Go to LogicNets Installation: New Installation and follow those steps.
3. When you have completed the installation/upgrade, restart the IIS server.

**Note:** During the upgrade process, the system will display a System Maintenance page. See Maintenance Page for more information.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/system-administration/installation/logicnets-installation-upgrade-system.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.