> 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/command-line-scripts/instance-management.md).

# Instance Management

## Description

With Release 7.4, LogicNets introduced a command-line script that allows administrators to manage companies inside an installation. This instance-management script is located in the *system/scripts* folder of your installation, and it is called *instancemanagement.bat* for Windows and [*instancemanagement.sh*](http://instancemanagement.sh) for CentOS. When you run this script without parameters or with the *–help* parameter the system will return a list of available commands and parameters.

## Use

When you run the instance-management script, you have the options detailed below.

**Instance Management**

\<version|currentdatetime|listpackages> \[] \[]

```
     --help                         showing this help information
     --output=[all|none|error|bare] hide any output
```

**Version**

instancemanagement version

**Current Date and Time**

instancemanagement currentdatetime

**List Packages**

instancemanagement listpackages

```
   --filter=<filter> Comma separated list of groups where user is added
```


---

# 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/command-line-scripts/instance-management.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.