license_setup
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| license_setup [2022/03/07 13:06] – yves | license_setup [2023/11/27 15: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' | + | * are a first-time user of PMA.core and don' |
| * 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 | + | * upgrade |
| - | The PMA.core | + | 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. |
| - | ==== How to update | + | ==== Locate |
| - | The user must copy the request code, which can be found in the second tab and send it to the vendor: | + | The user must copy the request code, which can be found in the second tab and [[http:// |
| {{ : | {{ : | ||
| - | The vendor will provide the user with an appropriate | + | ==== Receive a new license file ==== |
| + | The vendor will then provide the user with an appropriate license file. | ||
| + | {{: | ||
| + | |||
| + | ==== Apply the license file ==== | ||
| The vendor should save the sent license file locally on their own computer, after which it can uploaded to PMA.core and installed through the third tab: | The vendor should save the sent license file locally on their own computer, after which it can uploaded to PMA.core and installed through the third tab: | ||
license_setup.1646654786.txt.gz · Last modified: by yves
