> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/10.2-install/pentaho-installation-overview-cp/manual-installation/manual-installation-process/prepare-your-windows-environment-for-a-manual-installation/download-and-unpack-installation-files/step-2-unpack-the-pentaho-server-installation-files.md).

# Step 2: Unpack the Pentaho Server installation files

You must unpack the Pentaho Server installation file and move the contents to the correct directories for a manual installation.

Complete the following steps to unpack the installation file and move the contents to the correct directories.

1. Locate the `pentaho-server-manual-ee-10.2.0.0-<build number>.zip` file that you downloaded in [Step 1: Download files](https://docs.pentaho.com/install/10.2-install/pentaho-installation-overview-cp/manual-installation/manual-installation-process/prepare-your-windows-environment-for-a-manual-installation/download-and-unpack-installation-files/step-1-download-files-reuse.md).
2. Unpack the `pentaho-server-manual-ee-10.2.0.0-<build number>.zip` file and move the contents into the `\pentaho\server\pentaho-server` directory.
3. In the `\pentaho-server` directory, navigate to the `\pentaho-server-manual-ee` directory.
4. Unpack the following ZIP files and place the contents of the files in the appropriate directories.

   The following table lists the files to unpack and the directories where the contents from the file must be moved.

   | File to unpack                  | Directory where you move the file contents |
   | ------------------------------- | ------------------------------------------ |
   | `license-installer.zip`         | `pentaho\server`                           |
   | `jdbc-distribution-utility.zip` | `pentaho\server`                           |
   | `pentaho-data.zip`              | `pentaho\server\pentaho-server`            |
   | `pentaho-solutions.zip`         | `pentaho\server\pentaho-server`            |
5. Copy the `.war` and `.html` files to the following directories on your web application server.​

   The following table lists the files to copy and the directories where the files must be copied.

   | File                              | Directories that you copy the file into                                 |
   | --------------------------------- | ----------------------------------------------------------------------- |
   | `pentaho.war`                     | `pentaho\server\pentaho-server\<tomcat installation directory>\webapps` |
   | `pentaho-style.war`               | `pentaho\server\pentaho-server\<tomcat installation directory>\webapps` |
   | `PentahoServer_OSS_Licenses.html` | `pentaho\server\pentaho-server`                                         |


---

# 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.pentaho.com/install/10.2-install/pentaho-installation-overview-cp/manual-installation/manual-installation-process/prepare-your-windows-environment-for-a-manual-installation/download-and-unpack-installation-files/step-2-unpack-the-pentaho-server-installation-files.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.
