SAPIEN Information Center
Managing Your Single-User License
All software licenses purchased from SAPIEN Technologies, Inc. are per-user-the number of users accessing the software must equal the number of licenses purchased.
Our licenses can be deployed as 'single-user' or 'multi-user':
- To make the licensing management process easier, the way that single-user and multi-user license(s) are deployed varies.
- Regardless of whether the licenses are deployed as single-user or multi-user, the licensing terms and conditions are the same.
Single-User License Deployment
- Each license purchased will be deployed as its own 16-digit license number.
- Single-user license deployment is offered for individuals purchasing the license for themselves, or companies who wish to have a dedicated license number for each individual license purchased.
- When purchasing multiple licenses, the purchasing company will need to assign one license number to each individual operating the software.
Managing Your Multi-User License
All software licenses purchased from SAPIEN Technologies, Inc. are per-user-the number of users accessing the software must equal the number of licenses purchased.
Our licenses can be deployed as 'single-user' or 'multi-user':
- To make the licensing management process easier, the way that licenses are deployed varies.
- Regardless of whether the licenses are deployed as single-user or multi-user, the licensing terms and conditions are the same.
Multi-User License Deployment
- A minimum of two licenses is required for the multi-user deployment option.
- All licenses purchased for one software product are merged into a single 16-digit license number.
- Multi-user license deployment is best suited for larger businesses and corporations who do not wish to keep track of multiple license numbers for one piece of software.
Publishing Modules with PowerShell ModuleManager
PowerShell Modules are an important resource for scripting, and the ability to share PowerShell modules is easy with online repositories like the PowerShell Gallery. The ability to publish PowerShell modules is available in PowerShell ModuleManager v1.1.1 and later. You’re welcome!
Some Background on Publishing Modules
The Publish-Module command—from the PowerShellGet module—allows you to share modules from your local computer to online or local galleries.
To run the Publish-Module command, you can either specify the name or the path of the folder containing the module. If publishing by name, the first module found in the paths of the PSModulePath environment variable ($env:PSModulePath) will be published—so it is important to specify a minimum version if you have multiple versions.
When publishing modules to a NuGet-based online repository like the PowerShell Gallery, an API key is required. To get an API key for the PowerShell Gallery, you will need to create an account on the PowerShell Gallery and generate a new key for this module package. Local repositories do not need a key.
By default, Windows 10 ships with an old version of PowerShellGet, which provides the Publish-Module command, so this module must be updated to recognize the API key from the latest gallery site.
Publishing a module requires metadata, most of which is taken from the module manifest (.psd1). The minimum required data is:
- Name: Unique name of module that does not already exist on the repository attempting to publish to.
- Version: Current version of the module that must be higher than any existing versions of the module present on the repository.
- Description: A short description of the module.
- Author: Creator of the module.
There should be no output if the Publish-Module command runs successfully.
Offline License File Replaces Offline License Key
Effective with all SAPIEN products released June 29th, 2018, Offline License Keys have been replaced with Offline License Files. When you upgrade to the new release, you will need to generate an Offline License File.
- If you are using products released prior to the June 29th, 2018 updates, you can continue to use your Offline License Key.
- When you upgrade to the products released June 29th, 2018 or later, you will need to generate an Offline License File.
