KNOWLEDGEBASE - ARTICLE #2246

How to activate with a Machine Access Token

Overview

Machine Access Tokens allow you to assign a seat to a physical computer instead of a user. This is convenient for shared computers (e.g. lab computers, computers attached to instruments), so that your users don't have to use their own device activations.

For example, suppose you have 5 users, each with their own work laptop, and 3 shared lab computers. Use an 8 seat license to invite your 5 users via email, so that they can activate on their laptops. Then, use the remaining 3 seats to activate on the shared lab computers with Machine Access Tokens.

To enable this feature for your subscription, please contact us.

Before starting, please ensure that you have:

Access to manage seats for your license via My Account
Administrator privileges on the computer you wish to activate
Prism 10 or later on the shared computer

The activation process involves three steps, described in detail below:

Copying a Machine Fingerprint provided by the Prism application
Generating an Access Token in My Account
Using the Access Token to activate Prism

Activation Steps

1. Launch Prism

Select the "Activate with a Machine Access Token" option in the initial activation dialog.

Copy the Machine Fingerprint into your clipboard. This is the unique identifier that Prism generates for your device.
Do not close this window.

2. Generate the Access Token in My Account

Log into My Account, navigate to Manage Seats > Machine Tokens and click the "Add" button.

In the dialog, enter a Name for your shared computer (this will help you identify it), paste the Machine Fingerprint provided by Prism, and click the "Create Token" button:

You will now see an Access Token. Copy this token in its entirety to your clipboard.

3. Activate Prism

Back in Prism, paste the Access Token into the activation dialog from Step 1 and click "Continue":

Prism will now be successfully activated for all users on this computer.

If your subscription has access to Prism Cloud, your users will still be able to log into their Prism Cloud accounts separately on this computer without impacting the license activation.

Troubleshooting

DeepFreeze and Virtual machine deactivations

There is a known issue where Prism may unexpectedly request reactivation, even if it has been activated previously. We have identified several cases involving DeepFreeze Software, where computers configured with DeepFreeze and Prism activated using a Machine Access Token may occasionally prompt for reactivation, despite the license being displayed as active in the GraphPad account. A very similar issue can occur with Virtual Machine snapshots running Prism, activated with a Machine Access Token or with user-based licenses.

Why does this issue occur?

Prism stores its license file in a particular location in the system. The license file must be updated after each launch by connecting to the server to ensure proper usage of Prism. However, in certain cases, the file is not being updated due to specifics of DeepFreeze or Virtual Machine system configuration and its usage. Here is why.

DeepFreeze

DeepFreeze is designed to restore a computer to its original state after each restart, protecting it from unwanted changes or damage. If DeepFreeze is not configured to allow updates to the Prism license file (which is most likely by default), it can disrupt the activation token, leading the software to believe it has been deactivated.

When the system is reverted to its original state through DeepFreeze, Prism will require reactivation of the license via the server. This restoration process interrupts the valid activation by effectively “breaking” the activation token, which fails to maintain the activation chain, even though the license remains active in the account access cabinet.

Virtual Machines

Regular Prism licenses are not permitted from running on virtual environments. If you are attempting to virtualize Prism, please contact us.

Location of Prism License files

Windows:

Machine-based license - C:\ProgramData\GraphPad Software\Prism\prism-license.lic
User-based license - %APPDATA%\GraphPad Software\Prism\prism-license.lic

macOS:

Machine-based license - /Library/Application Support/GraphPad/Prism/prism-license.lic
User-based license - ~/Library/Application Support/GraphPad/Prism/prism-license.lic

Are there workarounds?

Yes!

DeepFreeze:

Create a ThawSpace: Users can create a ThawSpace as per the DeepFreeze guide for Windows and DeepFreeze guide for Mac, which allows certain files to be retained after a restart. This can be used to store the Prism license file.
Redirect certain files to another volume using DataIgloo that will persist changes. This video explains the concept: Retaining user data with Deep Freeze
Exclude License File: Consider excluding the license file from being frozen by DeepFreeze.
Disable DeepFreeze Temporarily: Users can disable the DeepFreeze state on the computers to allow Prism to update the license file. This is a temporary solution and may not be feasible long-term.

Virtual machine: