Jump to content

Mark Jacobson

  • Content Count

  • Joined

  • Last visited

About Mark Jacobson

  • Rank
  1. Are there any plans to patch the patch? Could we get some idea of how long?
  2. BUMP We disabled e-mail scanning on last week and so far we've had 0 new reports of Outlook closing improperly. No one else is having this issue in their environment?
  3. We're running Kaspersky version on our workstations. Its been very stable for about 6 or 8 months in comparison to the previous version. In the last week and a half we've had increased incidence of Outlook reporting to users that it was not shut down properly. When this occurs Outlook goes into a 15 to 30 minute process where it checks the integrity of the mailbox which makes Outlook pretty much unusable. The only thing we can think of that might have changed on multiple computers around the same time is an automatic update to Kaspersky. Has anyone else noticed this phenomenon?
  4. The status on the install tasks can get stuck. I've seen in the results, on occasion, a status of 32% setup started and 99% reboot required for several days. Upon further investigation I find out that the workstation has already been rebooted and is running the client. We set up the prompt for reboot on the install package and put a personalized message, so they don't panic, that allows them to postpone up to 9 hours before a forced reboot occurs. We can't trust many of our users to reboot on their own. Also, after the initial reboot I've seen some clients say after a few minutes that another reboot is required (this could explain the red flags that you are seeing.) I do not believe that the second reboot is due to the definition update, because future updates do not require reboot. I'm assuming it is having trouble replacing an open file or dll during the install in those cases? From what I've observed during our first year of ownership, you are not going to be able to avoid or consolidate reboots on full version installs. I've tried several anti-virus products and none of them seem to be able to avoid multiple reboots leaving the computers unprotected until they do. I've just learned to accept it at this point.
  5. I agree. Is there a way we can integrate this into the initial install package ourselves so that we aren't knowingly deploying a version with performance problems?
  6. In my case the user was still having major performance problems, so I think the patch was not installed. I finally had to uninstall and manually install on her workstation. Then connected it up to the server and ran the update. Now it shows up in the report as having update a.
  7. Well the Anti-slowdown patch is working wonders on computers where it actually installs. I have a number of computers that say N/A for the updates and I cannot get them to install the updates. It just acts like the udpates are already there. Any suggestions? I tried unchecking the admin kit server and checking only kaspersky labs. Update modules is checked.
  8. I'm looking more for something users can be expected to do, but thanks for the info.
  9. I'm used to our last solution where users had the option to pause the full scan for 3 hours at a time. Eventually they would go home and the scan would get done. Without an option to do this I'm probably not going to be able to do full scans because the scan effects performance to much on many of our PCs.
  10. Wait, are you saying to install Windows Server Enterprise Edition on workstations? It is the users on their workstations I would like to allow to pause their scans.
  11. Still unable to pause a server initiated scan in version 6. Is there any way? I didn't see anything int he policies to allow it.
  12. Additionally I uninstalled Kaspersky 6 and the Agent from the Admin Kit. Rebooted workstation. Reinstalled both from the Admin Kit where the license is included in the workstation installation package. I still get License Verification errors when the workstaiton tries to update virus definitions. Any help would be much appreciated. The GetSystemInfo did not find any malware. Is it possible that my license files are not right?
  13. Thanks for your help. The date and time is correct on all of the workstations, matches the administration kit server and the domain controllers which are synced to atomic time. When you say post a report what do you mean? Here? Or are you just using the getsysteminfo site terminology of posting the results for analysis? Sorry, I'm new to Kaspersky and not understanding why the corporate licenses are changing the behavior that I observed during the trial. Haven't changed anything on the clients or server other than installing the new license.
  14. We installed Kaspersky Administration Kit 6 and activated trial license. After the expiration period we bought 200 corporate licenses and received a key for it. I've applied that key to workstation installation package that I created in the Administration Kit as well as creating a task to install the license file to the four computers that had the trial license. When they try to update virus definitions they fail and the event message is License Verification Failed. However, in the License section of the Administration Kit I show the Corporate License for 200 workstations/fileservers. Targets tab of that license entry shows the computers that are failing verification and indicates that they are current and have an expiration date next year. Not sure what I am doing wrong, but they are not able to clear license verification or receive virus definition updates. Thanks, Mark
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.