Overview: Microvellum Licenses
This document will provide a detailed explanation of the functions, form, and usage of the new SLS (software licensing system) implemented by Microvellum as of December of 2023. This system is the default licensing system intended to be used with OEM 2024 and will be present in configurations Toolbox builds 23.1.1205.642 and onward.
Overview on License Types
FLA
- FLA stands for "Floating License Activation”, AKA, cloud-controlled network floating licensing. Clients downloading this license will utilize Microvellum in session format, requiring consistent internet connection in order to use. The session will have a routine verification over a set period of time to ensure the software is still being used and that the existing session should not be closed down (this will periodically occur once every 10 minutes). FLA is the default license type issued to all Microvellum clients upon activation.
- With FLA licenses, clients are able to install and utilize Microvellum across multiple devices, the only limitation being the number of users concurrently able to have open sessions (eg. someone with 5 licenses could have Microvellum installed on 25 devices, but the software can only be used by 5 people at a single time).
- The default number of devices able to have Microvellum installed with FLA licenses is currently 50. Clients are able to increase this limit at no cost by creating a software support request case in the Client Case Portal, which, upon approval, will raise the limit to the specified number.
In special circumstances, working offline with an FLA license is possible for up to 168 hours or 7 days. To check out a license, go to the Help/About interface and select “Session Management", then enter the maximum in the session duration, and click "Check-Out". If a session disconnects from the internet while still being checked out, the session should remain open and ready for active use for the maximum time period of 7 days.
Fig. 1: The "Session Management" option in the 'About Microvellum' interface. Fig. 2: Check-Out and Check-In screen under Session Management. A warning message will be displayed for roughly 30 minutes before the required validation refresh if no internet connection is detected. This provides time to save any open projects or drawings in the event the internet connection cannot be restored. If connection is not restored, clients will lose access to the software until the connection is restored.
SLA
- SLA stands for “Single License Activation”, a license type that has less of a strictly required internet connection than an FLA. Clients who purchase SLA licenses will still require internet connection for initial verification but will be able to open and launch the software without requiring it to run the session. Clients with SLA licenses will still have a periodic verification by the server, though this period will be longer than FLA, requiring a check-in once every 7 days. Unlike the FLA, the SLA license can only be activated on a single device, requiring temporary deactivation and reactivation in order to transfer devices, and only in accordance with the total number of allowed activations contained within the license. (i.e., 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.)
WRT
- WRT are Downloadable Licenses with Trigger Codes, licenses to be distributed on a case-by-case basis to specific clients or clients who may lack any significant or consistent connection to the internet to use either an FLA or SLA. WRT licenses allow for creating local device-based sessions using activation codes rather than consistent refreshing. These licenses are single device usage only and may be activated via telephone.
Trial
- Trial licenses are, as the name implies, licenses issued out by service providers for a temporary trial of the software. Trial licenses are issued upon request, lasting for a period of 7 days after the initial activation. Trial licenses are set to expire on a specific date, which can be found under the About Microvellum option.
- In order to check which type of license one currently has, navigate to the About Microvellum option under the Help tab. Information on the license type, along with expiration date, account details, and more will be displayed on the screen.
Fig. 3: The currently activated license type in the 'About Microvellum' interface.
Transitioning Between Licenses
Existing Licenses
- Upon updating to Toolbox build 23.1.1205.642 or downloading OEM 2024, clients will have their licenses, serial numbers, and ID automatically updated to an FLA license without any significant requirement on the user end, with a new license ID and activation password being automatically generated and assigned to clients opening the software post-update. All software modules and existing data should carry over to the new license format. In the event that this is not the case, create a Software Management support case in the Client Case portal, detailing which modules are no longer listed as available or present, and Microvellum support will address the matter as soon as possible.
- Microvellum's licensing system and future Toolbox updates will support Toolbox OEM versions 2022, 2023, and 2024. Older versions will be unable to update to Toolbox build versions newer than 23.1.1205.642. Clients with existing maintenance subscriptions will be able to install a newer version of OEM with no additional charge.
New Licenses
- New licenses will be available upon activating and verifying Toolbox for the first time, after downloading a corresponding OEM. New clients downloading OEM 2024 will have their ID and account information automatically generated upon activation of their license. One must have an internet connection available for the activation (if using FLA or SLA) or have a service provider on call (if using WRT) in order to complete the first activation.
Deactivating/Reactivating a License
There may be circumstances in which one wishes to deactivate or reactivate a license:
- SLA-type licenses are designed for single-license activation, intended for a single computer. If an SLA-type license needs to be transferred from one computer to another, it must be deactivated. SLA-type licenses include a 1-for-1 deactivation count – meaning that for every SLA-type activation, an equal number of deactivations are allowed. For example, if one has purchased 5 SLA-type activations, they can deactivate and reactivate each license up to 5 times without requiring intervention by Microvellum. In the event that a user wishes to deactivate their license (whether to move an SLA downloaded license to another device, switch between license types, or any other reason), there are different methods available to clients.
- The first and most immediately available option to deactivate licenses requires only a manual deactivation on the user end. Under the Help section, select the About Microvellum option. The interface will then display all information regarding one's current license, including the option to deactivate it, between the EULA and Refresh License options under the build information. This can alternatively be done via the splash screen once the software is opened, with the option displayed on the right-hand side of the interface.
- It is permitted for clients, in special circumstances, to request a temporary or permanent change in license types, if there is a significant change in one's connectivity that cannot be fixed within a reasonable time frame. To request a switch between license types, one must create a Software Management case in the Client Case portal. Select "General License Information" as the reason for the request.
- To activate a license, enter your License ID and Activation Password into activation UI of the Microvellum application. If you do not have your License ID or Activation Password, please submit a support request so that it may be sent to you.
- In the event additional deactivations are needed, beyond the default allotted number (FLA-type licenses are allotted 50 deactivations), a support request must be submitted to ask for additional deactivations.
- If a license requires reloading in order to be re-activated, such as in the case of a temporary deactivation or an issue of purchased modules not loading, select "Refresh License" either in the About Microvellum interface or on the splash screen when one first opens the software. This will reload the license to ensure all existing associations with that license are active.
Fig. 4: 'Deactivate License' and 'Refresh License'. Module Trials
- Clients are able to request Trial Software Modules, trial versions of the various Toolbox software modules from the About Microvellum screen, which will enable temporary access to the software modules. Depending on Toolbox version, module requests may be handled by contacting one's service provider, or alternatively, may be granted by the software itself. If one is using Toolbox build 23.1.01205.642 (or earlier), it is required to make a request to a service provider in order to unlock a module. If one is on Toolbox build 24.1.0104.641 or later, merely select the Request Trial option next to a module. Module trials last for a period of up to 30 days.
Fig. 5: The various software feature modules and their status displayed in the 'About Microvellum' interface.
Related Articles
About Microvellum Interface
The following information applies to Microvellum software builds 23.1.1205.642 and beyond. The About Microvellum User Interface displays information and links related to your Microvellum software, company account details and other information and ...
About Microvellum (Legacy)
The following information applies to Microvellum software builds prior to build 23.1.1205.642. The About Microvellum User Interface displays information and links related to your Microvellum software, company account details and other information and ...
Deploying Microvellum on an Azure Virtual Machine (VM)
Selecting the correctly sized virtual machines (VM) in Azure depends on several factors, such workload requirements, budget, and performance requirements. It may be necessary to work closely with an IT professional with experience working in Azure to ...
Products & Module Definitions
This document lists the various Toolbox modules available for users to select, each of which will enable the use of new capabilities within the software, to assist in the production workflow of clients. Toolbox Toolbox is an AutoCAD-based design, ...
Microvellum Glossary
Listed below are common terms related to Microvellum, our software products, and the woodworking industry. Use the table of contents to quickly jump to a section of the glossary by letter of the alphabet. # 2D & 3D Drawing (Software Feature) The 2D & ...
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 ...