...
Excerpt | ||
---|---|---|
| ||
Please note:
Enter the information for the AutoVE license server as shown in the example below (it shows the public AutoVE servers): Valid User Data configuration options:
where
Please note: at least one license server must be configured at initial launch to enable AutoVE mode. This can be via the /opt/charon-license-server file with the default public servers (SSP 5.6.8 or higher) or via the manual user data configuration. Otherwise, the instance will bind to one of the public AL license servers operated by Stromasys. | ||
Div | ||
class | pagebreak
Changing the AutoVE Server Configuration After AWS Instance Launch
...
Excerpt | ||
---|---|---|
| ||
The AutoVE license server information is entered as Custom Metadata. In the initial instance configuration window, go to the bottom where the NETWORKING, DISKS, SECURITY, MANAGEMENT... configuration section is located. Open it and select the Management section. Add the Custom Metadata as shown in the example below: Valid User Data configuration options:
where
Please note: at least one license server must be configured at initial launch to enable AutoVE mode. Otherwise, the instance will bind to one of the public license servers operated by Stromasys. | ||
Div | ||
class | pagebreak
Changing the AutoVE Server Configuration After GCP Instance Launch
...
Excerpt | ||
---|---|---|
| ||
The AutoVE license server information is entered as instance User Data. In the initial instance configuration window, go to the Advanced section.
Valid User Data configuration options:
where
Please note: at least one license server must be configured at initial launch to enable AutoVE mode. Otherwise, the instance will bind to one of the public license servers operated by Stromasys. | ||
Div | ||
class | pagebreak
Changing the AutoVE Server Configuration After Azure Instance Launch
...