> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/storage/local-storage/non-gui-environments.md).

# Non-GUI Environments

Learn about connecting the Couchdrop agent in a Non-GUI environment

## Overview

You can install the Couchdrop Windows Agent on a server without using the graphical interface.

This process involves configuring the Couchdrop Cloud Connector on a workstation first, copying its configuration to the server, installing the agent silently, and then running it as a Windows service.

## Install and configure the agent on a workstation

First, install and configure the Couchdrop Agent on a workstation where you can use the graphical interface.

For configuration instructions, see the [Windows / Mac File Server guide](/storage/local-storage.md).

Once the agent is installed and connected, browse to:

```
C:\Users\%username%\AppData\Local\CouchdropCloudConnector
```

Copy the following to a location that you can access from the target server:

* `configuration.conf`
* The Couchdrop Cloud Connector installer

Once these files have been copied, you can uninstall the agent from the workstation if it is no longer required there.

## Set up the agent on the server

{% stepper %}
{% step %}

### Open Command Prompt as Administrator

On the target server, open **Command Prompt** as an administrator.

Navigate to the location where you copied the Couchdrop Cloud Connector installer and `configuration.conf`.
{% endstep %}

{% step %}

### Install the agent silently

Run the Couchdrop Cloud Connector installer using the `/quiet` option.

For example:

```
C:\Couchdrop\couchdrop-cloud-connector-installer.msi /quiet
```

Your installer path may be different depending on where you copied the file.
{% endstep %}

{% step %}

### Copy the agent configuration

After installation, browse to:

```
C:\Users\%username%\AppData\Local\CouchdropCloudConnector
```

If the `CouchdropCloudConnector` folder does not exist, create it under `AppData\Local`.

Copy `configuration.conf` from the workstation into this folder.
{% endstep %}

{% step %}

### Install the agent as a service

Configure the Couchdrop Agent to run as a Windows service.

See [Running the Couchdrop Agent as a Service](/storage/local-storage/running-the-couchdrop-agent-as-a-service.md) for the full service configuration instructions.

You do not need to install the agent again. Continue from the section that instructs you to run:

```
.\couchdrop-cloud-connector-service.exe install
```

Complete the remaining service setup steps and confirm that the service is running.
{% endstep %}

{% step %}

### Verify the connection in Couchdrop

Once the service is running, open Couchdrop and check the Couchdrop Cloud Connector integration.

Confirm that the integration shows a successful connection.
{% endstep %}
{% endstepper %}


---

# 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.couchdrop.io/storage/local-storage/non-gui-environments.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.