> 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/quick-start/offline-network-deployment-and-activation-of-tools.md).

# Offline network deployment and activation of tools

## 1. Introduction

The Guide is intended for:

* IT Administrators
* System Administrators

{% hint style="info" %}
Offline means no internet, not no local network. Floating-license use requires a connection to the\
central server.&#x20;
{% endhint %}

This guide explains how IT deploys Be.Smart Revit tools with a central network license server in&#x20;environments without internet access. The setup has three components, each with a different&#x20;responsibility.

### 1.1 [Licensing Server](https://docs.besmart.software/getting-started/quick-start/offline-network-deployment-and-activation-of-tools/network-license-download-and-activation.md) - Holds and Allocates Licenses

Installed once on a central Windows computer. The network license is activated here, and the server&#x20;allocates available license seats to users' workstations. It runs as a Windows service, with a web page for&#x20;activation and administration. Revit is not required on this computer; do not install a separate license&#x20;server on each workstation.

### 1.2 [License Manager](https://docs.besmart.software/getting-started/troubleshooting/license-activation-in-restricted-it-environments-with-license-manager.md) - Provides Licensing on Each Workstation

Installed on every workstation running the tools in Revit. All current tools use ARKANCE License Manager's licensing&#x20;components to obtain licenses from the central server. IT can set the server address during deployment,&#x20;so users do not configure the connection or enter activation codes themselves.&#x20;

{% hint style="info" %}
ARKANCE License Manager (license management part of ARKANCE Dock) is the workstation application used to install tools and manage network licensing.
{% endhint %}

### 1.3 [Tool Installers (.msi)](https://docs.besmart.software/getting-started/troubleshooting/tools-.msi-direct-links.md) - Deliver the Revit Tools

These packages contain the actual Be.Smart tools that users run inside Revit. They use the standard&#x20;Windows installer format and can be downloaded in advance for unattended deployment. Revit must be&#x20;installed before the tools. Include the selected tool packages in the workstation bundle alongside the Dock&#x20;installer and deployment configuration.

### How They Work Together

1\) IT first installs the license server and activates network licenses on it.

2\) On each Revit user workstation, the ARKANCE License Manager installer reads&#x20;installconfig.xml, installs the selected local tool packages and saves the server address. Users then&#x20;open Revit and run the tools, which obtain their network licenses through ARKANCE License Manager.

#### Recommended sequence

1. Install License Server
2. Activate Licenses
3. Verify Port 8731 Connectivity
4. Prepare tools deployment package
5. Deploy tools on workstations
6. Verify tools installation
7. Verify user license access

### Troubleshooting

<table><thead><tr><th width="299"></th><th width="431"></th><th data-hidden></th></tr></thead><tbody><tr><td><a href="https://docs.besmart.software/getting-started/troubleshooting/network-license-server-installation-error.md">Network License Manager MSI fails</a></td><td>Verify .NET 3.5 is installed using the correct OS-specific method, administrator rights, an existing Distributor installation, and the installer log. Do not assume .NET 8/10 satisfies the prerequisite.</td><td></td></tr><tr><td><a href="https://docs.besmart.software/getting-started/troubleshooting/slps.distributor.host.exe-in-quarantine-by-anti-virus.md">Administration site does not load</a></td><td>Check Slps.Distributor.Host, then http://localhost:2468/web on the server. Only if remote administration is required, check name/address resolution and scoped TCP 2468 firewall rules. Remote access is not needed for local administration.</td><td></td></tr><tr><td><a href="https://docs.besmart.software/getting-started/troubleshooting/network-license-server-error-in-web-application.md">Server Error in /Web</a></td><td>Confirm .NET/ASP.NET prerequisites and permissions. Keep the error details and server component logs. </td><td></td></tr><tr><td>Tools asks for activation</td><td>Check the automatically saved server address, TCP 8731, available seats, licensed feature/Revit coverage and expiry. Do not activate the network code individually on the workstation.</td><td></td></tr><tr><td><a href="https://docs.besmart.software/getting-started/troubleshooting/network-license-could-not-connect-to-the-server.md">User can not connect to server</a></td><td>Check licensing server status. Ensure Slps.Distributor.Host is not blocked</td><td></td></tr><tr><td><a href="https://docs.besmart.software/getting-started/troubleshooting/network-license-license-is-not-visible.md">Network licenses not visible for users</a></td><td>Delete .dat license cache files</td><td></td></tr><tr><td><a href="https://docs.besmart.software/getting-started/troubleshooting/network-license-borrowed-license-release-issue.md">Issues releasing licenses</a></td><td>Use license manager to release the licenses</td><td></td></tr></tbody></table>


---

# 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/quick-start/offline-network-deployment-and-activation-of-tools.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.
