Jump to content

Adam.Burns

Members
  • Content Count

    184
  • Joined

  • Last visited

Everything posted by Adam.Burns

  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.
  11. Many advantages: http://support.kaspersky.com/us/10250.
  12. Disabling a USB port doesn't always solve your removable device problems. Often, a more granular level of control is required to enable user productivity and security. For example, if a user must plug in a USB VPN token to access the network — but shouldn't be plugging in removable storage devices — a ‘disable the USB port’ policy won’t work. Kaspersky empowers the administrator to set policy and to control any connected device, on any connection bus (not only USB), at any time. This means the administrator can regulate which devices can connect, read or write, the time of day at which a policy becomes effective, and which types of device are allowed. For extreme security, these controls can even be applied to the specific serial number of the device. Use these two resources to achieve your configuration: 1) http://support.kaspersky.com/us/learning/c...2.98/chapter3.3 2) http://support.kaspersky.com/us/7423 Thanks!
  13. Official support for Windows 8.1 Pro will be added as soon as possible. Thank you for your patience.
  14. Are you installing to Windows 8.1 PRO or Windows 8.1 ENTERPRISE? Please look at the requirements: http://support.kaspersky.com/kes10wks#requirements.
  15. Switch to MR1. We added support for 8.1. Kaspersky Security Center 10.1.249 (http://support.kaspersky.com/ksc10#requirements). Kaspersky Endpoint Security 10 for Windows 10.2.1.23 (http://support.kaspersky.com/kes10wks#requirements). This will support Windows 8.1 Enterprise (not Professional).
  16. KES10 comes with a firewall so that is what is going on here. You should put FSEE8 on your servers instead of KES10. It is a lot better for that purpose.
  17. The plugin is the first step, but you also need to create an installation package for the MAC protection (Step 2 below). Step 1: Install the MAC agent via any of the methods mentioned: http://support.kaspersky.com/7635 - SSH http://support.kaspersky.com/7992 - ARD http://support.kaspersky.com/4458 - Locally on the MAC Step 2: Create an installation package for MAC in the security center. (http://support.kaspersky.com/7639). The screenshot mentions installation packages in Repositories, it is actually under the Remote Installation area of the Security Center. The network agent being already installed, this installation can be done via a standard installation task directly from the Security Center Console.
  18. This can be due to the installer running in autonomous mode. When you double click on it (even while logged in as a domain admin) it will launch in autonomous mode which does not have the sufficient rights to execute every operation within the installation process. This all can be very easily solved by right clicking the installer and selecting "Run as Administrator". Please let us know if this fix works (or not) for you.
  19. Just so people know what everyone is talking about, I created a screenshot: Also, If you cannot update through your VPN, can I suggest that you use update agents or create an administration server hierarchy? It should solve you issue: You can install several Administration Servers in a corporate network. Administration Servers may form a “master server – slave server” hierarchy. Each Administration Server is allowed to have several slave Servers. A Slave Administration Server performs the following functions: • stores logical network structure (network configuration); • stores a copy of information about configuration of client PCs; • organizes storage of distribution packages of Kaspersky Lab applications; • allows remote installation of applications on client PCs; • updates antivirus databases and application modules; • allows to control policies and group tasks on client PCs; • stores information about events on client PCs; • creates reports about the work of applications in logical network; • distributes license keys on client PCs, and stores information about license keys; • sends notifications about the tasks running on client PCs. For example, such notifications may report viruses detected on client PCs. In comparison, the Update Agents will only handle the transmission of definition updates to a specifically defined group of computers. Here is the link to our knowledge base with information about how to implement a Slave Server: http://support.kaspersky.com/us/10495.
  20. Why not upgrade to KSC10? http://support.kaspersky.com/us/9315 Nevermind, re-read your post above.
×
×
  • 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.