Sometimes, you do not want to have a server per environment. This is when scaling vertically makes sense. 


Two scenarios that are perfect for vertical scaling:


- You have more than one Non-Production environment but do not want to invest in a server or VM per environment. This is when you install multiple environments, or instances, on the same server. Look at it as virtualization of instances where all instances can share the compute from the same server. This is OK for Non-Production instances as they, most of the time, are not heavily utilized. Still, it is not recommended to do for Production environments where performance is vital.


- You have an instance installed in a physical environment where you have available compute power (memory and CPU). 


These are the extra steps you will have to do to add a new instance to your existing Lasernet server:


1. Add a new Azure Service Bus and/or Queue for the new instance in your Azure Portal.

2. Add the new instance in the Admin Web Portal. Make sure to pick the next available Server Service port.

3. Add a new Server Service license to the License Manager. Make sure to choose the same port as in step 2

4. Prepare a separate Lasernet Config file for the new instance:

  1. Change the Web Service port in the Lasernet Developer for the new instance. Pick the next available web port.
  2. Add the new instance as a server in the Lasernet Developer. 
  3. Change the Azure Service Bus, Queue, and Storage in the Lasernet Developer for the new instance.

5. Configure the Instance, Connections, and Lasernet Server settings in the D365 connector matching the new instance.

6 ***Optional*** Install the Cloud Print configs for the new instance.


As with any Lasernet configuration, make sure you use the same instance name and port in the Admin portal, License Manager, Monitor, and Developer.