Deploy Probistica licenses
This page tells IT staff how to give license files to many users. These rules apply to a Product build. A build with licensing Off reads no license file and sends no activation or refresh request.
The five policy values below have an effect in this version. This version has no hosted activation service; without an activation service address, the add-in sends no activation or refresh request. (User-clicked error and support reports to https://probistica.com/api/error-report are separate and controlled by DisableErrorReportSend below.) Users import the license file that the seller sends by email. A free trial file and a site license have no binding, so the user sends no machine ID first. Only a license that is bound to one computer or one user needs that ID first, by email or in an offline request (it needs an activation ID).
The license folders
The add-in reads all .lic files in these folders, in this order:
%LOCALAPPDATA%\(one user). Import license file copies a file here.Probistica\ Licenses %PROGRAMDATA%\(all users of the computer).Probistica\ Licenses - The folder of the policy value
LicensePathunderHKLM\.SOFTWARE\ Policies\ Probistica - The folder of the policy value
LicensePathunderHKCU\.SOFTWARE\ Policies\ Probistica
A folder that does not exist is skipped. The add-in reads only the top level of each folder, and only files with the extension .lic. A file is usable when it is valid or in its grace period. The label and the License dialog show the usable file with the most features as "in use". With the same number of features, they show the file with the latest end date; a file without an end date counts as the latest. A run needs one usable file that has all the features of the run. This file can be another file than the file "in use".
To give a license to all users of a computer, copy the .lic file into %PROGRAMDATA%\. Give the users read access to the folder.
The policy values
The add-in reads the policy values in the 64-bit view of the registry, under HKLM\ and HKCU\. It only reads them. Deploy them with Group Policy Preferences or with another tool for registry values.
| Value | Type | Effect in this version |
|---|---|---|
LicensePath | REG_SZ | One more folder or a network share with license files. The add-in uses the value of HKLM and the value of HKCU: both folders are added. |
ActivationUrl | REG_SZ | The address of the activation service, for example a company gateway. It must start with https:// (http:// only for localhost, 127.0.0.1, or ::1), and it must have no user name, query, or fragment. The value of HKLM wins over the value of HKCU. Without this value, the add-in uses the address of the build; a normal build has none. |
DisableOnlineActivation | REG_DWORD, 1 | Hides Activate online in the License dialog. Deactivation then gives the offline code. Offline activation stays available. |
DisableRefresh | REG_DWORD, 1 | Stops the automatic refresh at load. Users then import a renewed file. |
DisableErrorReportSend | REG_DWORD, 1 | Hides Send report in the error report window, so no report goes to https://probistica.com/api/error-report. Copy, Save as file, and Open e-mail stay (The footprint of Probistica, "Network use"). |
The add-in counts only the DWORD 1 as a flag. When HKLM and HKCU both have a flag, the value of HKLM wins. A flag can only turn a function off.
Example (as an administrator):
reg add "HKLM\SOFTWARE\Policies\Probistica" /v LicensePath /t REG_SZ /d "\\server\licenses\Probistica" /f /reg:64
A slow network share
The add-in reads the license folders at each license check and at each update of the ribbon button. It keeps no cache, so a new or removed file counts at once. Thus a LicensePath on a slow share makes each check slow. Prefer a local folder that IT fills, for example %PROGRAMDATA%\.
Bindings
Each license file has a binding:
- Machine. The file works only on the computer of its machine ID. The machine ID is a hash of
HKLM\. The user copies it with Copy machine ID in the License dialog.SOFTWARE\ Microsoft\ Cryptography\ MachineGuid - User. The file works only for the Windows user of its user ID. The user ID is a hash of the user SID. The License dialog shows it.
- Site. The file has no binding. It names the organization. The contract sets the number of users; the add-in does not count them.
The machine ID and the user ID are hashes. They do not show the original values.
Virtual desktops
A non-persistent virtual desktop (Citrix, VDI) can get a new MachineGuid at each sign-in. Then a machine license does not work after the next sign-in. For such desktops, use a user license or a site license.
A non-persistent profile can also lose %LOCALAPPDATA% at each sign-in. Put the license files in %PROGRAMDATA%\ of the image, or in the folder of LicensePath.
The clock state
A Product build writes %LOCALAPPDATA%\ when a usable license with an end date is present (at most every 10 minutes), and once when a license file for this computer with a valid signature has expired (recording the end of its grace period, as in The footprint of Probistica). These licenses are an evaluation, a subscription, and a site license with an end date. The file holds the latest time that the add-in saw. For a license with an end date, a clock more than 48 hours before that time makes the license not valid. A perpetual license has no end date, so it does not use the check. Without a usable or validly signed expired license with an end date for this computer, the add-in writes no state.json. If the folder cannot be written, the add-in continues without the file.
If the clock of a computer was set ahead by mistake by more than 48 hours, the license stays not valid after you correct the clock. The clock check passes again when the real time is no more than 48 hours before the recorded time; the other checks of the license still apply. To use it before then, close Excel and delete state.json in the folder of the user.
Remove license data
The add-in deletes a license file only for Deactivate this computer, and only in %LOCALAPPDATA%\. It names the copies of the license in other folders, but it does not delete them. To remove the license data:
- Delete the
.licfiles,state.json,refresh.json,revoked.json, anddeactivation-codes.txtin%LOCALAPPDATA%\of each user.Probistica\ Licenses - Delete the
.licfiles in%PROGRAMDATA%\.Probistica\ Licenses - Delete the files in the folder of
LicensePath, and delete the policy values.
The uninstall of the add-in keeps all of these items.
Not in this version
A hosted activation service, a hosted customer portal, and floating licenses are not in this version. The seller sends each license file by email. With an activation ID, users can also create an offline request in the License dialog and send it to support. The add-in client for online activation, deactivation, and the refresh is built. It sends a request only to the address of ActivationUrl or of the build. Online activation and the customer portal are planned for paid Individual licenses and are not on a public host yet.
Many computers behind one address
When a hosted service exists, it limits the requests of each client address. A company network that sends all requests through one proxy or one NAT address counts as one client. The defaults of the service permit 300 refresh requests at once and then one each second, and 30 activations at once and then one each 20 seconds. A request over the limit gets HTTP 429. The add-in then shows the message of the service, and the refresh tries again after a day. Tell the seller before you activate many computers at the same time.