---
title: "Create and Configure Lasernet Core Environments"
slug: "create-and-configure-lasernet-core-environments"
description: "Instructions for creating and configuring Lasernet Core environments."
tags: ["Configuration", "Lasernet Core 11"]
updated: 2026-06-22T10:25:12Z
published: 2026-06-22T10:25:12Z
canonical: "kb.lasernetgroup.com/create-and-configure-lasernet-core-environments"
---

> ## 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.

# Create and Configure Lasernet Core Environments

On each server that will host a Lasernet Core environment, you must use the Lasernet Service Manager to create the Lasernet Core environment. The tool will create a corresponding Windows service on that server.

You must also configure the new Lasernet Core environment.

## Steps

To create a Lasernet Core environment on a server and configure it, follow the quick start process or the full installation and setup process on this page.

> [!NOTE]
> Note
> 
> **About the quick start process:** The quick start process is a simpler route to an operational Lasernet Core system and it requires only basic IT knowledge. However, it results in a system that is suitable only for demonstration or trial purposes. For more information about the quick start process (and its inherent compromises), see the main [Lasernet Core 11 Installation and Setup Guide](/v1/docs/lasernet-core-11-installation-guide) page.
> 
> 
> 
> **About the full installation and setup process:** The full installation and setup process describes all available installation and setup options and is suitable for setting up production Lasernet Core systems. However, parts of it require some IT and database administration knowledge.

### Quick Start Installation Process

1. In the Windows **Start** menu, click **Lasernet 11** > **Lasernet Service Manager 11**. The **Lasernet Service Manager 11** window opens.
2. Create a Lasernet Core environment on the server:
  1. In the **Lasernet Service Manager 11** window, click **Add** (see 1 in the image below). ![A number annotated screenshot of the Add Service window in the Lasernet Service Manager with Production entered as the service name.](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/add service(1).png)
  2. Enter the **Name** (2) of the new environment. Make a note of the name that you enter. The image above contains **Production** as the name, but you can use any name for the Lasernet Core environment.
  3. Ensure that **Environment** is selected in the **Type** dropdown list.
  4. Click **OK**. A window that contains the default configuration for the new environment opens.
3. Click **Ok** to close the window and accept the default configuration.
4. In the **Lasernet Service Manager 11** window, select the new environment and click **Start** in the toolbar. The Lasernet Core environment is now running.

![A Lasernet environment selected in the Lasernet Service Manager window and the mouse pointer over the Start button.](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/create environment.png)

#### Next Steps

After creating Lasernet Core environments, the next step of the [Lasernet Core 11 installation and setup process](/v1/docs/lasernet-core-11-installation-guide) is to [configure the Lasernet Config service](/v1/docs/configure-the-lasernet-config-service).

### Full Installation and Setup Process

1. In the Windows **Start** menu, click **Lasernet 11** > **Lasernet Service Manager 11**. The **Lasernet Service Manager 11** window opens.
2. Create a Lasernet Core environment on the server:
  1. In the **Lasernet Service Manager 11** window, click **Add** (see 1 in the image below). ![A number annotated screenshot of the Add Service window in the Lasernet Service Manager with Production entered as the service name.](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/add%20service(1).png)
  2. Enter the **Name** (2) of the new environment.
  3. Ensure that **Environment** is selected in the **Type** dropdown list.
  4. Click **OK**. A window that contains the default configuration for the new environment opens.
3. In the new window, check the environment’s default configuration and modify it (if necessary):
  1. On the **General** tab (see 1 in the image below), ensure that **Config server host name** and **Config server port** are correct. If these are incorrect, the environment will be unable to communicate with Lasernet Config Server. ![A number-annotated screenshot of the General tab of the environment properties window.](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/configure service(2).png)

> [!NOTE]
> Note
> 
> You configure Lasernet Config Server during the next stage of this installation and deployment process. As a result, you would not have opened the **Properties** window for Lasernet Config Server and configured its port number yet.
> 
> 
> 
> However, the default **Config server port** number (443) matches the port number that Lasernet Config Server is configured to use by default. In most situations, this is satisfactory. You would need to change this port number (in the Lasernet Config Server and environment’s configurations) only if necessary to prevent port clashes with other software running on the same server.
> 
> 
> 
> The default **Config server host name** of **localhost** is appropriate if Lasernet Config Server is running on the same server as this environment. If Lasernet Config Server is running on another server, enter that server’s hostname with a fully-qualified domain name.
> 
> 
> 
> If you later find that **Config server host name** and **Config server port** are incorrect in this environment’s configuration, click this environment in the **Lasernet Service Manager 11** window, click **Edit**, and then update **Config server host name** and **Config server port**.
  2. Lasernet Service Manager generates a **Client secret** for the environment. Make a note of this code as you might need it when you configure Lasernet Config Server.

> [!NOTE]
> Tip
> 
> You can click **Copy to clipboard** (2).

> [!NOTE]
> Tip
> 
> To generate a different client secret, click the adjacent **Generate** (looping arrows) button.
  3. **Optional:** If you leave the **Server runtime data directory** box blank, the environment will use the default location for storing configuration files, log files, and temporary files for that environment. In most situations, this local file location is satisfactory. If you want to specify where the environment stores this data, enter or select a directory.

> [!NOTE]
> Tip
> 
> For faster processing, use a local file location rather than a network location. Ensure that the location is not user-specific (for example, do not use the Windows Desktop).
  4. Startup, liveness, and readiness health probes enable you to monitor on-premises and containerized Lasernet Core systems. To enable the health probes for this environment, select the **Health probe port** checkbox. Below the checkbox, specify the port that the probes listen on.

> [!NOTE]
> Note
> 
> If health probes are enabled, each environment provides the following REST endpoints:
> 
> - Startup probe: `/healthz/startup`
> - Liveness probe: `/healthz/liveness`
> - Readiness probe: `/healthz/readiness`
> 
> HTTP is supported. SSL is not supported.
> 
> For information about startup, liveness, and readiness health probes, see [https://kubernetes.io/docs/concepts/workloads/pods/probes/](https://kubernetes.io/docs/concepts/workloads/pods/probes/).
4. Configure the environment’s port number:
  1. Click the **Bindings** tab (see 1 in the image below).

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/add binding.png)
  2. If necessary, modify the **Port** number (2).

> [!NOTE]
> Note
> 
> Modify the port number only if necessary to prevent port clashes with other software running on the same server (including Lasernet Core itself).
> 
> 
> 
> For example, if a server hosts multiple Lasernet Core environments, each environment must have a unique **Port** number.
5. If necessary, specify the hostnames to bind a local server certificate to. The environment will use the certificate to prove the server’s identity; the certificate also provides encryption keys to secure communication between server and client. An environment can use certificates installed in the Windows certificate store (in the **Computer certificates** area) or certificates stored on disk as PFX files. You must create a binding for every hostname that clients will use to connect to the environment.

> [!NOTE]
> Note
> 
> If no bindings are configured, Lasernet Core will autogenerate self-signed certificates for `localhost`, `<server name>` and the server’s fully qualified domain name (FQDN).

To specify a binding, follow these steps:

> [!NOTE]
> Note
> 
> Repeat these steps for every hostname that clients will use to connect to the environment. For example, some clients might connect to `localhost`, whereas other clients might connect to the server’s FQDN. Multiple bindings can point to the same certificate, if necessary.
  1. Click **Add** (3).
  2. In the **Add Binding** window, enter a **Hostname**. This is the hostname that the certificate will be bound to. Valid values for **Hostname** are a hostname (without a domain specified), a FQDN, or an IP address.
  3. Provide certificate details:
    - If **Thumbprint** is supplied, the certificate (in the Windows certificate store) with the specified thumbprint will be used.
    - **PFX** is the path and filename to a certificate (including private key) that is stored in PFX format. **Password** is the password for the PFX file.
    - If you leave both **Thumbprint** and **PFX** blank, a self-signed certificate for the specified **Hostname** will be generated and stored in the Windows Certificate Store.
  4. Click **OK** to save the binding.
6. Click **Ok** to close the environment properties window and save your configuration changes.
7. In the **Lasernet Service Manager 11** window, select the new environment and click **Start** in the toolbar. The Lasernet Core environment is now running.

![A Lasernet environment selected in the Lasernet Service Manager window and the mouse pointer over the Start button.](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/create environment(2).png)

#### Firewall Configuration

If the Lasernet Core environment is not running on the same server as Lasernet Config Server, ensure that firewall configurations are modified to enable the environment and Lasernet Config Server to communicate with each other.

#### Next Steps

After creating Lasernet environments, the next step of the [Lasernet Core 11 installation and setup process](/v1/docs/lasernet-core-11-installation-guide) is to [configure the Lasernet Config service](/v1/docs/configure-the-lasernet-config-service).

##