> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/user-guide/monitoring/general/maintenance-mode/manual.md). # Manual Maintenance ### Set a Single System Into Maintenance Mode 1. Navigate to the IT-Conductor Service Grid, expand the container groups (i.e., SAP Systems), and find the system (i.e., specific SID) to update. 2. Click the context menu icon (i.e., SAP logo) for that system. 3. Click **Maintenance On**.

Figure 1: Maintenance On for a Single System

### Set Multiple Systems Into Maintenance Mode 1. Navigate to the IT-Conductor Service Grid and find the container group (i.e. SAP Systems) to update. 2. Click the context menu icon (i.e., SAP logo) for that container group. 3. Click **Maintenance On**.

Figure 2: Maintenance On for Multiple Systems

### Remove Maintenance Mode Setting 1. Navigate to the IT-Conductor Service Grid. 2. Click the **Show Services in Maintenance Mode** icon.

Figure 3: Show Services in Maintenance Mode Icon

3\. Find the system or container group to update. Then click on the context menu (i.e., SAP logo) for that system or group of systems. 4\. Click **Maintenance Off**.

Figure 4: Maintenance Off for a Single System

Figure 5: Maintenance Off for Multiple Systems

--- # 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://docs.itconductor.com/user-guide/monitoring/general/maintenance-mode/manual.md?ask=&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.