Changing Microvellum License Types

Changing Microvellum License Types

This article documents the process of switching between the types of licenses available to clients using Microvellum's SLS (Software Licensing System) and explores the differences in functionality between the different types of Microvellum licenses. For a full detail of each respective license type and their capabilities, visit our Overview on the topic. 

License Types

  1. FLA ("Floating License Activation”) the default type of license issued to clients. FLA licenses operate the software on a session basis, requiring a constant internet connection, with an infinite number of installations and activations. 
  1. SLA ("Single License Activation") a license available upon request or during the initial purchase process for clients who have less reliable internet connection, with an automatic 7-day period in which one can work offline before requiring internet connection for the license to authenticate, with a limited number of device-locked installations and activations. 

Requesting a License Change

If one wishes to change their license from an FLA-type to one less dependent on a connection, the alternative would be an SLA-type (or, in extremely rare circumstances, a WRT-type). To change one's license type:
  1. Log into your account on the Microvellum Case Portal.
  2. Navigate to "My Cases" and open a new support case. 
  3. Give the case a title that indicates the intent to change license types, select “Software Management” as the case type and “General License Information” as the reason for the request.
  4. In the description field of the case, explain the details of the request including the number of licenses you would like to convert to SLA-type licenses.
  5. Microvellum staff will reach out once the case is submitted.

FLA License Features

  1. Unlimited Activations: Clients utilizing FLA-type licenses are able to install and utilize Microvellum across multiple devices, the only limitation being the number of users who can concurrently run sessions (these are referred to as "seats" in most documentation).
  2. As an example, if someone purchased 5 licenses for Microvellum OEM 2024, they could install and activate their OEM 2024 software on up to 50 devices (this is the default cap, more activations can be requested), but only 5 people can have an open session in the software at the same time.
  3. When a software session is opened, it claims a seat from the available pool, with the seat not being returned until the session is closed.
  1. Session Management: FLA-type licenses have a functionality that enables them to work offline for a maximum of 168 hours or 7 days. This is achieved by checking out a session, a process which downloads a temporary local read-only license file to one's device.
  2. To check out a license, click the “Session Management" hyperlink in the top right corner of either the software's splash screen (the UI that appears upon startup), or navigate to the About Microvellum UI under the "Help" tab. In the session management interface, enter the intended session duration, and click "Check-Out". If a session disconnects from the internet while checked out, the session should remain open and ready for active use for the maximum time period of 7 days. Once a connection has been re-established, or one wishes to end the session and start a new one, merely open the Session Management interface again, and select "Check-In". 
  1. Limits: FLA-type licenses, as previously mentioned, require consistent and stable internet connection. If one is disconnected from the internet, the software will lock after a short period and a mandatory warning message to reconnect.
  2. Checking out a session requires an internet connection for the initial check-out.
  3. The 168-hour period counts down even when the software is not in use (the 168 hours are the time between check-out and the intended check-in, when the license needs to be re-authenticated, not 168 hours' worth of software usage.)
  4. While a session is checked out, that session claims a seat from the available pool of seats, which will remain claimed until the session is checked back in. Moreover, when a session is checked out, the session is restricted to the device that it was checked out upon. As such, switching devices to gain access to an already existent session is not possible. 

SLA License Features

  1. Less Strict Connection Requirement: Clients who purchase SLA-type licenses will still require internet connection for initial activation process but will be able to open and launch the software without requiring it to run the session. This is because SLA-type licenses download a local file to the device they are installed on upon activation, 
  1. 7-Day Automatic Timer: Clients with SLA licenses will still have a periodic verification by the server, though this period will be longer than FLA, being once every 7 days. The refreshing of the license is also automatic, meaning that it will not be affected by sudden loss of internet connection, and once connection is restored, it will not require any additional steps for the 7-day timer to reset. 
  1. Limits: Unlike the FLA, the SLA license can only be activated on a single device, needing to be deactivated and reactivated to be transferred between devices. One is only capable of activating and deactivating a license a set number of times. 
  2. For example, if one purchases a license, has 5 employees, and wants all of them using an SLA-type license, one will have 1 license with 5 activations. That means the license can only be activated (and deactivated) up to 5 times before needing to submit a support request to request more activations/deactivations. 
  3. SLA licenses still require internet connection for the initial activation, meaning if one is disconnected, one cannot move the license between devices. 

    • Related Articles

    • Operating During Outages

      Microvellum's SLS (Software Licensing System) is designed to work with consistent internet connection in mind, but in situations where a stable connection is not possible, such as an internet or power outage, it may be helpful to have alternative ...
    • Common Floating License Connectivity Issues

      This document lists common issues reported by users regarding the topic of Microvellum’s Floating License Activation (FLA) and the connectivity required for FLA to function. Firewall Blocking Activation of Floating License Some users have had an ...
    • Microvellum Support and Maintenance

      Microvellum Support Microvellum offers comprehensive support and maintenance benefits, ensuring clients have access to technical assistance, software updates, and training resources to optimize their software experience. When purchasing a Microvellum ...
    • How to Create a Support Case through the Microvellum About/Support Portal UI

      This article details the process of creating a support case directly through Microvellum software. See Creating a Support Case for general information on what is to be included in a case. To start a support request, navigate to Help > About ...
    • Microvellum Server Installation Guide

      This article outlines the steps to install and configure the Microvellum Server software. See  Microvellum Server (Overview)  in the Microvellum Help Center for an article giving a summary of the Microvellum Server software. See  Microvellum Server ...
    • Recent Articles

    • Toolbox Release Notes | Build 24.1.1105.641

      The following release notes apply to Toolbox build 24.1.1105.641 Nesting Fix Fig. 1: The fatal error that would occur during processing. There was reportedly an issue that occurred when clients attempted to process a work order using the nesting ...
    • Microvellum Foundation Library Release Notes | Build 24.1025

      The following release notes apply to Microvellum Foundation Library build 24.1025. Additions Added new global variable “Remove Stop Dado On Bottom Edge” for wood drawer boxes. Check this option to run the dado through at the bottom of the sub front ...
    • Toolbox Release Notes | Build 24.1.1030.641

      The following release notes apply to Toolbox build 24.1.1030.641 Routing and Profile Fixes Several issues were found with routing and polyline paths: Fig. 1: Horizontal routes off of a part disappearing (left) and appearing correctly (right). When ...
    • Toolbox Release Notes | Build 24.1.1010.641

      The following release notes apply to Toolbox build 24.1.1010.641 Biesse Winstore Fix Several issues with the Biesse Winstore plugin have been resolved: There was an issue that would sometimes occur wherein materials that were intended to stack wound ...
    • Toolbox Release Notes | Build 24.1.1001.641

      The following release notes apply to Toolbox build 24.1.1001.641 HBore Toolfile Fix Fig. 1: The location in the Toolfile UI where the error would occur. There was an issue reported with the functionality of the Horizontal Boring Machine setting in ...