> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/getting-started/troubleshooting/arkance-dock-deployment.md).

# Arkance Dock Deployment

## **Problem**

Deploy and activate tools to multiple computers without end-user intervention

## Solution

{% hint style="success" %}
The ARKANCE Dock can read the installconfig.xml file during installation
{% endhint %}

1. Download and save all necessary .msi files of the ARKANCE Dock and tools in the same folder as installconfig.xml:

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2F0IZAuWeNfdSk1cOgoiUP%2F0.jpeg?alt=media)

You can control these settings within the XML file:

{% file src="/files/th2FmhH0JBCyViNSuKpW" %}

<details>

<summary>Installconfig.xml</summary>

```markup
<?xml version="1.0" encoding="utf-8"?>
<InstallOptions>
<DockConfiguration>
<StartDockOnRevitStartup>false</StartDockOnRevitStartup> TOOLS4BIM Dock hidden/shown when Revit. starts
<InstallAppsInProgramData>false</InstallAppsInProgramData> Tools and Dock installation location: User based folder if set to false (%appdata%) or machine-based installation (%programdata%) if set to true.
<StoreTabVisibility>false</StoreTabVisibility>
<UpdateSettings>Allow</UpdateSettings>
<NetworkLicensePath> http://SERVER_nameOrIP:8731 </NetworkLicensePath> Set network license server URL automatically.
</DockConfiguration>
<DockAppOptions>
<InstallProductGroups>
<ProductGroup Name="Product Group Name">
<InstallProducts>
<Product Name="Product Name">
<InstallTools>
<App Name="Tool Name" File="RevitTools202x_MSI_FILE.msi" IncludeInRibbonMenu="true"
IncludeInFavoriteToolsTab="true"/>
<App Name="Tool Name" File="RevitTools202x_MSI_FILE.msi" IncludeInRibbonMenu="true" IncludeInFavoriteToolsTab="true"/>
</InstallTools>
</Product>
</InstallProducts>
</ProductGroup>
</InstallProductGroups>
</DockAppOptions>
</InstallOptions>
```

</details>

All tools' '.msi' files can be downloaded from:

{% tabs %}
{% tab title="2027" %}
<https://api.dock.agacad.com/public/vendors/aga/products/downloads?year=2027>
{% endtab %}

{% tab title="2026" %}
<https://api.dock.agacad.com/public/vendors/aga/products/downloads?year=2026>
{% endtab %}

{% tab title="2025" %}
<https://api.dock.agacad.com/public/vendors/aga/products/downloads?year=2025>
{% endtab %}

{% tab title="2024" %}
<https://api.dock.agacad.com/public/vendors/aga/products/downloads?year=2024>
{% endtab %}

{% tab title="2023" %}
<https://api.dock.agacad.com/public/vendors/aga/products/downloads?year=2023>
{% endtab %}

{% tab title="2022" %}
<https://api.dock.agacad.com/public/vendors/aga/products/downloads?year=2022>
{% endtab %}
{% endtabs %}

2. Deploy[^1] the folder to your end-users devices
3. Run[^2] the ARKANCE Dock installation
4. End-user will automatically download the assigned list of tools&#x20;

[^1]: Deployment method depends on your network setup / third-party reliance

[^2]: Running method depends on your network setup / third-party reliance\
    \
    Make sure you run as administrator and have sufficient permissions to run and folder of installation


---

# 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.besmart.software/getting-started/troubleshooting/arkance-dock-deployment.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.