> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/deployr-enterprise/prerequisites.md).

# Prerequisites

In order for DeployR to function properly, it is important that the necessary hardware, software, and networking prerequisites are met. The specifics for these are described separately:

* [Hardware prerequisites](https://documentation.2pintsoftware.com/deployr/deployr-enterprise/prerequisites/hardware-prerequisites.md)
* [Software prerequisites](https://documentation.2pintsoftware.com/deployr/deployr-enterprise/prerequisites/software-prerequisites.md)
* [Networking prerequisites](https://documentation.2pintsoftware.com/deployr/deployr-enterprise/prerequisites/networking-prerequisites.md)

DeployR integrates with StifleR and relies on several supporting components, including database services, deployment tools, and runtime dependencies. Proper configuration of these elements is required to ensure reliable operation and deployment workflows.

All products included in the DeployR Enterprise Suite can be installed on the same server, or you may choose to install them on different machines or in different locations. Your license does not restrict the configuration or number of servers installed. Having a complete, separate lab environment for testing and validation is recommended for most enterprises.

## Required download URLs

DeployR downloads the browser, PowerShell, and hardware or virtualization drivers from the locations below. Make sure these addresses are allowed by your firewall, proxy, and web filtering rules.

* `teamdev.download` — browser download
* `api.service.2pintsoftware.com`
* `dotnet.microsoft.com`
* `github.com/PowerShell/PowerShell/releases/download`
* `download.lenovo.com`
* `download.microsoft.com`
* `downloads.dell.com`
* `ftp.hp.com`
* `global-download.acer.com`
* `na.panasonic.com`

**VirtIO driver downloads** (`virtio-win-gt-x64.msi`):

* `github.com`
* `raw.githubusercontent.com`
* `releases.2pintsoftware.com`

**VMware Tools driver downloads:**

* `packages.vmware.com`


---

# 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://documentation.2pintsoftware.com/deployr/deployr-enterprise/prerequisites.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.
