Prevent Kaspersky Key to be sealed eight little common sense

Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall

First, try to use Kaspersky Kav version, avoid using Kaspersky Kis version. Because Kis than kav with a firewall, so the vast majority of people chose the Kis, and gave up the Kav, which will also cause the phenomenon of the 4th article.

Second, try to use the low version of Kabbah. Kaspersky now out to 2009 (8.0) version, we all have a new mentality, that the version of the high certainly than the version of the easy to use. The final result is that most people are using the new version. This will result in the phenomenon of article 4th.

Third, as far as possible the choice of commercial authorized key (general commercial authorized key will have more than 10 licenses), do not choose only 1 computer business authorized key. Because 1 computer business authorized key, are personal use, Kabbah upgrade flow control is very strict, if the flow of serious overload, it will be sealed off the key. And more than 10 of the authorized key, are generally used by enterprises, upgrade the flow of relatively large, Kabbah seal key more cautious. Because the profit of antivirus software is mainly from the enterprise, therefore, antivirus software companies generally prefer to offend individuals, but also do not want to offend enterprises.

Try to choose the key with short effective period. Because the vast majority of people want to be once and for all, deliberately want to find the longest valid key. This easily causes million people to squeeze the log bridge, the result many people use the longest valid key. What is the end result: Because everyone is using the highest version of the Kis and the longest time of the key, the result of the key was sealed off!! Because Kaspersky monitor this key use exception, was blacklisted.

Five, try not to let Kabbah automatically update. This will prevent everyone from updating at the same time, causing a burden on the upgrade server. If everyone can easily use Automatic updates, this phenomenon is likely to increase significantly: the same key, at the same time, while in the upgrade. It was not surprising that the key was sealed. So I hope everyone think about each other, do not just figure their own convenience.

Six, try to choose a foreign upgrade server (Super IMPORTANT!!). Although this view is not necessarily correct, it still has a reference. Because the current Kabbah is the default China's server, in fact, we can remove the "Kaspersky Lab Update Server" to add their own several foreign servers, such as other Asian countries. It's best not to choose Chinese and Russian.

If your e-text is good, you may consider using the version of Kabbah. With the use of foreign upgrade server. Because the Chinese are too many, the total number of use of Kabbah may be several times in some countries, resulting in the probability of key being blocked greatly increased.

Eight, the other key of the storage directory, the path does not have any Chinese. For example, the use of Kabbah KAV6.0, the version is not high, the choice is Japan's server, set to automatically upgrade at 8:00 every day, the use of valid 6 months within the key, for 10 computer business license.

Original address: http://www.kavsd.cn/Skills/2009022576.html

The article is allowed to reprint, but want to keep the full link, thank you!