Process
To transfer some or all of your activated Thermo Scientific software licenses to a different license server, deactivate the desired licenses as follows:
1. Open a command prompt/terminal in the directory where you have extracted the FlexNet server tools archive and go to the FlexNetLicenseServerTools subdirectory.
2. Run ServerFNOODActivation -v to display the licenses currently installed on your machine.
3. Copy all fulfillment IDs.
4. Your server is connected to the internet:
- Run ServerFNOODActivation -r <FulfillmentID> for every fulfillment ID.
You can request multiple deactivations at the same time:
ServerFNOODActivation -r <FulfillmentID1> -r <FulfillmentID2> -r <FulfillmentID3>
Your server is not connected to the internet:
- Run ServerFNOODActivation -r <FulfillmentID> -offline <File.xml>.
For example: ServerFNOODActivation -r 52518253 -offline request.xml
If you have multiple activation codes, you can request multiple deactivations in the same file:
ServerFNOODActivation -r <FulfillmentID1> -r <FulfillmentID2> -r <FulfillmentID3> -offline <File.xml>
- Generate and import the response XML file:
- Transfer your XML request file to a computer with an internet connection.
- Open https://vsg3d.flexnetoperations.com/control/vsgs/offlineActivation in a web browser.
- Specify the path to your XML request file in the provided file field.
- Click on Process. An activation.xml response file is downloaded.
- Transfer this activation.xml file to the FlexNet license server.
- Back in the command prompt/terminal, enter:
ServerFNOODActivation -response <ResponseXMLPath>/activation.xml (where <ResponseXMLPath> corresponds to the directory where you have transferred the activation.xml response file)
Your licenses are activated in a few seconds.
5. Open http://localhost:8090/vendor in a web browser.
6. Click on the mcslmd line.
7. Click on Reread License Files.
After successfully deactivating the desired licenses, you can activate them on a different license server.
Note
To validate the configuration of the new server without disrupting the old server, we suggest initially transferring only one license or token. Once the new server is operational, transfer the remaining licenses or tokens.