Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
en:v2:core:faq:faq_licensing [2022/04/18 19:01] 127.0.0.1 external edit |
en:v2:core:faq:faq_licensing [2022/04/18 19:13] maria_k [Have to wait again ☹?] |
||
|---|---|---|---|
| Line 101: | Line 101: | ||
| Technically, the licensing system allows the CPU to be changed up to two times, without activation failure. However, this only works as long as the ASTER license data (which includes information about the original CPU and the number of CPU replacements) is still kept on this computer and not destroyed. This data is stored in the Windows registry, and if it is destroyed, for example, due to complete reinstallation of Windows, the information about the original CPU disappears. A new pair of CPU/Disk appears and the activation attempt fails. This is what causes this sort of "delayed" license failure. But the user has already forgotten that he replaced the processor/motherboard several months ago, and is in a state of confusion. | Technically, the licensing system allows the CPU to be changed up to two times, without activation failure. However, this only works as long as the ASTER license data (which includes information about the original CPU and the number of CPU replacements) is still kept on this computer and not destroyed. This data is stored in the Windows registry, and if it is destroyed, for example, due to complete reinstallation of Windows, the information about the original CPU disappears. A new pair of CPU/Disk appears and the activation attempt fails. This is what causes this sort of "delayed" license failure. But the user has already forgotten that he replaced the processor/motherboard several months ago, and is in a state of confusion. | ||
| - | Therefore, although the ability to replace the CPU without activation failure exists, we are strongly discouraged from using it. It is better to **[[:ru:dev:core:faq:faq_licensing#faq_licensing_deactivation_byyourself|deactivate]]**the license before replacing computer components. | + | Therefore, although the ability to replace the CPU without activation failure exists, we are strongly discouraged from using it. It is better to **[[.:faq_licensing#faq_licensing_deactivation_byyourself|deactivate]] **the license before replacing computer components. |
| **Very important notes about paragraph 5. ** | **Very important notes about paragraph 5. ** | ||
| Line 162: | Line 162: | ||
| Therefore, if you plan at least one of the actions 1)-4), listed in the section [[.:faq_licensing#faq_licensing_deactivation_notneeded|"When deactivation is not needed"]], then you need to carry out the procedure for deactivating the license, by initiating it from the GUI. | Therefore, if you plan at least one of the actions 1)-4), listed in the section [[.:faq_licensing#faq_licensing_deactivation_notneeded|"When deactivation is not needed"]], then you need to carry out the procedure for deactivating the license, by initiating it from the GUI. | ||
| - | The deactivation procedure is documented on the ASTER website: [[:ru:dev:core:ugd:ugd_licensing#deactivate_aster_licenses|https://www.dokwiki.ibik.ru/en/v2/core/ugd/ugd_licensing#deactivate_aster_licenses ]] | + | The deactivation procedure is documented on the ASTER website: [[..:ugd:ugd_licensing#deactivate_aster_licenses|https://www.dokwiki.ibik.ru/en/v2/core/ugd/ugd_licensing#deactivate_aster_licenses ]] |
| Briefly, the procedure is: | Briefly, the procedure is: | ||
| Line 446: | Line 446: | ||
| ==== Have to wait again ☹? ==== | ==== Have to wait again ☹? ==== | ||
| - | Yes, wait while the support service determines the cause of the failure and fixes the problem. Do not forget about the difference in time zones and the current workload of the support service. Therefore, if you do not receive an instant response to your request, please do not start periodically to send the same request at short intervals. Do not aggravate the situation. But you also shouldn't wait for a very long time (more than a day, see the [[:ru:dev:core:faq:faq_licensing#faq_licensing_deactivation_problemsend|previous section]]) | + | Yes, wait while the support service determines the cause of the failure and fixes the problem. Do not forget about the difference in time zones and the current workload of the support service. Therefore, if you do not receive an instant response to your request, please do not start periodically to send the same request at short intervals. Do not aggravate the situation. But you also shouldn't wait for a very long time (more than a day, see the [[.:faq_licensing#faq_licensing_deactivation_problemsend|previous section]]) |
| **But you don't have to wait!** | **But you don't have to wait!** | ||