Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:licenses:transfer-or-release-a-license [2016/01/27 20:20]
Rob Holda [Can I get longer than 3 day parallel running time for my server migration]
+++ litespeed_wiki:licenses:transfer-or-release-a-license [2018/11/26 16:53]
Kacey Schroeder [How to Release Existing License]
@@ Line 1: / Line 1: @@
+====== How to transfer or release a license ======
 __Notes:__
    * This instruction applies to both LSWS and LSLB. For LSLB, replace with "lslb" where "lsws" is used, and "lslbd" where "lshttpd" is used.
-   * Please make sure http://license.litespeedtech.com is reachable from your server.
+   * Please make sure ''license.litespeedtech.com'' is reachable from your server.
+   * The migration command is for clients to migrate licenses from one server to another when they change servers. It's for same site content.
+   * Currently, we do not allow manual migration from the command line if the license has already been migrated 3 times in the past 30 days. After 3 times, you are required to go to your account client area to release it.
 ----
@@ Line 8: / Line 13: @@
 ===== The difference between license transfer and release =====
-    * You can freely **TRANSFER** a LiteSpeed license from one server to another server under you account. The transfer will give you 3 day of overlapping time, so this will give you a smooth migration from the old server to new one.
+    * You can freely **TRANSFER** a LiteSpeed license from one server to another server under you account. The transfer will give you 3 days of overlapping time, so this will give you a smooth migration from the old server to the new one.
-    * In case you don't have access to the old server, such as in case of hardware failure, you will need to enable the license on the new server. You can use **RELEASE** license option. Do NOT "Release" your license if it is still actively used, this will immediately terminate the license and LSWS will stop running.
+    * In case you don't have access to the old server, such as in case of hardware failure, you will need to enable the license on the new server. You can use **RELEASE** license option. Do NOT "Release" your license if it is still being actively used, this will immediately terminate the license and LSWS will stop running.
@@ Line 19: / Line 24: @@
   - login to your account from online store - client area.
-  - go to my products - product detail page, click "Release License" link.
+  - go to Services -> My Services -> product detail page, click "Release License" link.
+{{ :litespeed_wiki:licenses:release_license_screenshot.jpg?nolink |}}
   - Then you can use the serial number to register a new license key. Follow instructions at [[litespeed_wiki:licenses:activating-a-license|Activating A License]].
@@ Line 32: / Line 40: @@
   - Verify your migrated license in your old server, you should have 3 days overlap for a smooth transition. LSWS process on your old server will automatically shut down after 3 days, so make sure you are ready to register for the new license when you ready to migrate.<code>old_server:lsws/bin/lshttpd -V</code>
   - In your new server, or the same server after hardware upgrade, register a new license. Assume you already copied over the same directory over.
-    * When you run "-r" option, make sure there is no other license related files in the lsws/ and lsws/conf directory except "serial.no". Back up and remove all the "trial.key", "license.key". <code>new_server:lsws/bin/lshttpd -r</code> A new file license.key should be saved in the same directory as serial.no (either under lsws/conf or lsws/).
+    * Before you run "-r" option, make sure there is no other license related files in the lsws/ and lsws/conf directory except "serial.no". Back up and remove all the "trial.key", "license.key". Also make sure you have "serial.no" in lsws/conf already. If there is no "serial.no" file there, you should create one and place your serial no into that file before you run "-r": <code>new_server:lsws/bin/lshttpd -r</code> A new file license.key should be saved in the same directory as serial.no (either under lsws/conf or lsws/).
     * If your new license key is not in the lsws/conf, move the new license.key and serial.no to  lsws/conf. <code>new_server:mv lsws/license.key conf/</code> Usually this step is not necessary.
   - Verify the license in your new server. <code>new_server:lsws/bin/lshttpd -V</code>
@@ Line 45: / Line 53: @@
 ===== Can I get longer than 3 days of parallel running time for my server migration =====
-You can apply a trial key first and test everything on your new server, when you ready, do the migration step which give you extra 3 days.
+You can apply a trial key first and test everything on your new server. Then, when you're ready, perform the migration step, which gives you 3 extra days.
 ===== Can I transfer my license to another customer? =====
-For yearly leased and owned license, you can sell and transfer to another person if you no longer need it. Since this requires manually move your license to another account, you or your counter party will need to pay a small transaction fee for the transfer. Please create a ticket with license department from client area. You cannot use regular "transfer" or "release" steps, as you will still receive invoices on your account.
+For yearly leased and owned licenses, you can sell and transfer to another person if you no longer need it. Since this requires manually moving your license to another account, you or your counter party will need to pay a small transaction fee for the transfer. Please create a ticket with the license department from the client area. You cannot use regular "transfer" or "release" steps, as you will still receive invoices on your account.