Unfortunately we can only direct them back to the party that they purchased the duplicate license from. Several of the posters here had purchased this type of license from another iLok user. Only the licenses listed are set to be returned.
#Ilok license manager seems to be installed incorrectly how to
If the license is currently activated on an iLok, we told you which iLok the license is on, and how to return it. If you did get an email from us, your email lists the licenses that were mistakenly deposited. If you didn't get an email from us, that means nothing was changed in your iLok account. This means that the licenses that are being removed are duplicate licenses that should never have been deposited. This created a duplicate of the license, and in some cases, created a full license when what was actually seen on the iLok was an expired license. These deposits were made when our server saw an iLok but failed to recognize the licenses on that iLok as the very same licenses that already were listed in the iLok account. The license deposits that we sent emails about were deposits created by our server, NOT deposits made to an iLok account by a software publisher. But since there seems to be so much speculation and concern by those who were not affected, we're happy to share more information here.
If you didn't receive an email from us, there were no mistaken deposits identified in your account. These users were not randomly chosen, we actually audited every single license to carefully identify only those that were mistakenly deposited. Second, we did send emails to a small number of iLok users regarding license deposits that were made to their accounts by mistake. Our site and services are running smoothly without any problems. This includes the website, the iLok License Manager application, and our license activation services.
It looks like there is some speculation and misinformation being posted here so we'd like to clear up what is going on.įirst, the entire iLok ecosystem was unaffected by the Heartbleed vulnerability.
0 kommentar(er)
