license_setup
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
license_setup [2022/03/07 15:15] yves |
license_setup [2023/11/27 17:24] (current) chris |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| Follow the steps in this part of the wiki when you: | Follow the steps in this part of the wiki when you: | ||
| - | * are a first-time user of PMA.core and didn't get a license file yet | + | * are a first-time user of PMA.core and don't have a license file yet |
| * have [[License expiration|an expired license file]] | * have [[License expiration|an expired license file]] | ||
| * move your PMA.core setup to new hardware or virtual machine | * move your PMA.core setup to new hardware or virtual machine | ||
| - | * upgraded your commercial agreement with Pathomation to facilitate more concurrent users | + | * upgrade your commercial agreement with Pathomation to facilitate more concurrent users |
| - | The PMA.core software is built in such a way that a straightforward email exchange process allows the customer to upgrade their own license file. No other intervention from Pathomation is needed, except for sending the customer an updated license file based on the commercial conditions. | + | PMA.core is built in such a way that a straightforward email exchange process allows the customer to upgrade their own license file. No other intervention from Pathomation is needed, except for sending the customer an updated license file based on the commercial conditions. |
| ==== Locate your request code ==== | ==== Locate your request code ==== | ||
license_setup.1646655330.txt.gz ยท Last modified: 2022/03/07 15:15 by yves
