Jump to content

Adam.Burns

Members
  • Content Count

    184
  • Joined

  • Last visited

3 Followers

About Adam.Burns

  • Rank
    Cadet
  1. There are 3 settings within a Scan Task that should be looked at: Scan only new and changed files: This setting will enable or disable the mode of scanning only new files and files that have been modifies since the previous scan. Kaspersky will scan both plain and compressed files. iChecker Technology: iChecker calculates and remembers checksums of scanned files. A checksum is a digital signature of an object (file) which allows identifying its authenticity. Upon any object modification, its checksum will be changed. The iChecker technology puts checksums of objects into a special table and then checks whether the checksums for the scanned objects are different from the previous data. If the checksum is different from the previous value, the object is identified as a modified version and will be rescanned. If the checksum is not different, the object is skipped. iSwift Technology: The iSwift technology is a modification of the iChecker technology but for NTFS file systems. The NTFS file system assigns a special NTFS identifier to each object. iSwift checks NTFS identifiers of scanned objects with previous identifiers of the objects. If the identifier was changed, the object will be rescanned. So which are you using? Does enabling different combinations of the above cause the scan to act differently? Or is it all the same no matter what you choose. Please note that this change is in the actual virus scan task - not the policy.
  2. I have used KES10 to FDE a Windows VM. The only issue is that it will take up the entire provisioned space - even if thin provisioned. But that is just my 2 cents. I would still wait for Nikolay to provide a complete answer.
  3. There is a system service that runs on endpoint machines called Windows Update. It must be turned on or 'started' for these functions to work correctly. Please go to an endpoint machine with the issue, run services.msc, and make sure this service is on and running (started):
  4. Install the version 6 plugin here: and you can access the uninstaller via the task here:
  5. Zach, each endpoint will only use one of the update agents. Specifically the one that is most available. If you have 40 machines trying to use update agents, theoretically there should be 20 going to update agent 1 and 20 going to update agent 2. If update agent 2 is offline or too busy, all 40 will just go to update agent 1.
  6. Are you using SQL Express locally or different set up? It sounds like your using Security Center to connect to the Administration Server fine. When you click on something it tries to query your DB but it is freezing. I would start there.
  7. This was posted this morning: http://threatpost.com/new-internet-explore...-attacks/105720. So I can only assume it is in the works if not already fixed.
  8. At a quick glance, it seems like the MSI is erroring out with 1603. According to Microsoft: You may receive this error message if any one of the following conditions is true: The folder that you are trying to install the Windows Installer package to is encrypted. The drive that contains the folder that you are trying to install the Windows Installer package to is accessed as a substitute drive. The SYSTEM account does not have Full Control permissions on the folder that you are trying to install the Windows Installer package to. The following is a non-exhaustive list of known causes for this error: Short file name creation is disabled on the target machine. A file is locked and cannot be overwritten. The Microsoft Windows Installer Service is not installed correctly. The Windows Temp folders are full. Please check the above. Let us know your findings. Update: Upon furthur investigation, it looks like the installation of klfltdev.inf driver: It appears like this is in fact a permissions issue. Please refer to the above and look at your System account permissions.
  9. The blatant answer: No, KES10 will not track individual email messages for spam or blacklisting purposes. You would need something on your mail server.
  10. It looks like you are missing a bunch of components too. Was that purposeful? Also, export the policy and attach here please.
×
×
  • 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.