---
title: "Install Lasernet Developer Locally Self-Hosted Customers"
slug: "install-lasernet-developer-locally-1"
description: "It is necessary to install the Lasernet Developer on the user’s machine to enable users to modify the Lasernet Configuration."
tags: ["Lasernet Developer", "Finance and Operations", "Default configurations", "Lasernet FO Connector", "Lasernet connector", "Lasernet Developer application", "Installation guide", "Azure Service Bus", "Self-hosted customers", "Local installation", "Deploy", "Azure Storage", "License key"]
updated: 2026-03-04T14:11:06Z
published: 2026-03-04T14:11:06Z
canonical: "kb.lasernetgroup.com/install-lasernet-developer-locally-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Install Lasernet Developer Locally

## Install Lasernet Developer Application

The Lasernet server is now configured, but it is still necessary to install Lasernet Developer to enable users to modify the Lasernet Configuration. This can be installed either on the same VM as the Lasernet server or locally on a user’s laptop. In this example, we will install Lasernet Developer on the user’s laptop.

[This article](/v1/docs/set-up-remote-connection-to-lasernet-10-server-from-local) shows how to go through this process.

To install the Lasernet Developer application, follow these steps:

1. From the Lasernet Package zip folder, which was downloaded as part of the [prerequisites](/v1/docs/prerequisites-for-everyone#lasernet-developer-package) earlier, double-click the **Lasernet Developer** file.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (21)(13).png)

1. Click **Next**, accept the typical installation, and follow the steps until the Developer is installed.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (22)(13).png)

## License Code

To activate the Lasernet Developer License, follow these steps:

1. On the machine where you have installed Lasernet Developer, navigate to the **Start** menu, search for “Lasernet Developer License Manager” and open it.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-JT432MN1(2).png)

1. Select the **Lasernet Developer** instance, click **Activate**, then copy the Lasernet Developer license code into the window that is shown. This will be the key that begins with “DEV”.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-BBGOYZZF(2).png)

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-UQZ5CQ3E(2).png)

Lasernet Developer will now be active.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-1700649021922(1).png)

Note

A demo license has been used in the screenshot above. Your instance will not say “DEMO”.

For more details about using the License Manager, watch our [Formbytes Video Tutorials](/v1/docs/lasernet-license-manager).

## Install the Default Configuration

Users should now install the default configuration into Lasernet Developer, which matches the configuration loaded into Finance and Operations earlier.

1. In the **Start** menu, find the Lasernet Developer icon.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-8FWQ1666.png)

1. Open Lasernet Developer, copy the server name configured earlier, and paste it into this field. In a previous example, we displayed a machine name. However, here we are installing Lasernet Developer on a local machine, so you will use a DNS name similar to the following image:

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (1)(29).png)

> [!NOTE]
> Note
> 
> The `https://` part of the URL can be ignored.

1. Click **Connect** and, when prompted, enter the login details from the previous step.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (2)(24).png)

1. On the **Start** screen, click **Import configuration**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-1700649150199(1).png)

1. Browse to the default configurations that were downloaded earlier, and select the `LNCONFIGX` file (orange logo).

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (3)(20).png)

1. Import this file, and the configuration will open.

## Configure Azure Service Bus

1. In the Developer configuration that opens, select the **Servers** option from the **Tools** menu.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (4)(24).png)

1. Select **Default** under **Servers**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (5)(19).png)

1. In the right-hand pane of the window, under **Instance**, double-click **Default**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (7)(20).png)

The **Default Properties** window appears.

1. Select the server name from the **Instance** dropdown menu, then click **OK**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (8)(22).png)

1. Navigate to **Modules** from the **Tools** menu, and ensure that you have the new server name selected in the top left-hand corner.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (9)(20).png)

1. Click the **Azure Service Bus** box located in the workspace.
2. Paste the Azure Service Bus connection string, which was used for the connection in Finance and Operations, into the **AZURE SERVICE BUS QUEUE CONNECTION STRING** box, and select the entity path; there is a **Copy** button next to the connection string, which can be used to copy the value.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (10)(20).png)

1. Paste it into the **Connection String** box.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-9NGZTS8Q(2).png)

1. Click **Test Connection**, and the following message is displayed:

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-HYRFUKL3(2).png)

1. Click **OK** > **Ok**.

## Configure Azure Storage

1. Within the Lasernet Developer, click the **Commands** tool in the **Tools** menu and select **Azure Storage**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-1700649328782(1).png)

The **Azure Storage Properties** window is displayed.

1. Copy the Azure Storage string from FO and paste it into the **Connection string** field.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-1700649349680(1).png)

1. The connection string can be copied from the Azure Storage connection in FO by using the **Copy** icon next to the **Type** field.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-NR8FJ0FR(1).png)

Or, depending on the version of FO, from within the **Lasernet parameters**, under the **Performance** tab.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-1700649391400(1).png)

1. Click **Test Connection** within the **Azure Storage Properties** window and then **OK** > **Ok**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-1700649407411(1).png)

## Deploy the Changes

The default configuration in Lasernet is now updated with the appropriate connection information to link it to the Lasernet Connector, which was previously installed in FO. You now need to commit and deploy those changes for them to take effect. Follow these steps to do so:

1. In Lasernet Developer, click **Commit** in the top Toolbar.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-1700649427668(1).png)

1. Within the **Commit Changes** window, add a message detailing what changes have been made.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-1700649442914(1).png)

1. When the “Commit complete” message is displayed, click **Close**.
2. Click **Deploy** in the Toolbar, then in the **Deploy configuration** window, click **Ok**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-1700649470634(1).png)

1. Click **Close** when prompted that the deployment was successful.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-1700649491323(1).png)

For self-hosted customers, the deployment of the Lasernet for Dynamics solution is now complete.