Jump to content


  • Content Count

  • Joined

  • Last visited

About balmon@arcol.org

  • Rank
  1. Would love to see enhancements in the search function in the next version of Kaspersky Security Center. One great feature in KSC10 is the ability to search the applications registry for a specific application by name. It would be nice to categorize all applications into groups/categories such as P2P/File Sharing or Anti-Virus or Toolbar. I would hope Kaspersky could create and manage a database of applications and groupings so that KSC administrators can search by groups. For example, let's say you want to find all the computers that have P2P/File Sharing applications installed. In many organizations, using P2P software is a violation of the acceptable use policy. To add to this, having pre-defined reports available would also be great. Thanks!
  2. "When your endpoints grab a policy from Security Center those local tasks are automatically set to a 'manual' schedule, so those tasks will not run without someone starting them"... this is not the case with any of my endpoints. When KES10 is installed on a client via the agent... the local tasks are pre-configured. Those tasks are: Run Full Scan 3 times per week at 6PM... and the setting to only scan new or changed files is unchecked. Have you ever tried to use the computer when Kaspersky is running a full scan? It's pretty much impossible to be productive. This local task runs regardless of whether KES10 is under a policy or not. I've opened up support tickets with Kaspersky about this and it went no where. They would say... do this... and then close the ticket. Never offer to actually look at our KSC setup or a client. On a side note... It is frustrating that the knowledge base article for the setup.ini never mentions that it doesn't apply to instances where KSC is used.
  3. Yes, we are running the configuration that you mention. Your suggestion is for created 'group tasks' which does work. The issue that I have is with 'local tasks' that are configured when KES10 is installed on the client computer. I have since learned that 'local tasks' can be configured during the install using the setup.ini file... however, in my tests saving a modified setup.ini file in the deploy folder for SC10 (\KLSHARE\Packages\KES_10.1.0.867\EXEC\setup.ini), it doesn't seem to work. The pre-configured 'local tasks' are still configured when the KES10 is pushed out to the client computers via the KES agent. The setup.ini file specifically looks like this for tasks (all tasks are at zero) [Tasks] ScanMyComputer=0 ScanCritical=0 Updater=0 Also, the suggestion to uncheck Allow local tasks to be displayed and managed (except custom scan) does not work either. Any suggestions?
  4. I have about 30 groups setup and it would be nice to use the search box in the upper right hand corner of KSC10 to search for any computer using any search term and have the results be populated with the same speed and feel as Windows search. Sometimes clients get lost in the groups or you want to find one by computer name quickly. Using the existing search tool is too cumbersome. When managing hundreds of clients, search is an admin's best friend.
  5. After digging, I did find that you can only control local tasks by disabling them during the initial deployment of KES10 by using a modified setup.ini file. I'm in the process of testing this solution right now. However, what is not clear exactly is there the setup.ini must reside when using it in a deployment scenario with the Kaspersky Agent and KSC10. The two comments I found are to store the setup.ini in one of these places: \KLSHARE\Packages\KES_10.1.0.867(1)\EXEC\setup.ini OR In the folder where the .msi file for the KES10 package resides. Since I don't have admin access to the KSC, I'm not quite sure where the .msi file resides. Another thing I don't understand... is everyone references this support article... http://support.kaspersky.com/us/9389 Ok, that't great... but why is there no mention on where the setup.ini file should be stored if deploying via agent using KSC10. Seriously, Kaspersky... you need to hire a marketing and PR person... that is from the United States and speaks English. Among my resellers, they consider Kaspersky the best enterprise solution available... but when the support options are so bad... it doesn't make your product look good. A business enterprise customer using your product shouldn't have to comb through hundreds of forum posts to find answers... The second thing that must be done is to configure the policy in KSC10 with the following: - Endpoint Policy -> Advanced Settings --> Operating Modes --> Uncheck: Allow local tasks to be displayed and managed (except custom scan). Let's see what happens...
  6. This is a big one. I have 180 endpoints and have no way to schedule when the tasks on the client machine run. Right now, all the clients use the default schedule which is awful (full scan every 3 days... users can't work under these conditions). Ideally, updates should be performed outside business hours so the slowness of the update doesn't impact productivity. Same for the full scan... the default setting should be once per month and only scan for new and changed files. You can create a group task in KSC, but this group task is in addition to the local scheduled tasks. So it essence, users complain because they have multiple tasks performing the same task. Basically what needs to happen is if KES is working under a policy, then all scheduled tasks should be controlled by the policy that is configured in KSC. Administrators should have full control over when endpoints update, when a full scan is performed, when the critical areas area scanned.
  7. I have the same problem as well. I use KSC 10 with KES 10 and about 180 users. The big problem I have is that there is no way to schedule when the tasks run on the client from KSC. It would be ideal to have the scans and updates process after business hours. Right now, this isn't possible. I have to manually go to each client and set the scheduled tasks. There has to be a better way.
  • 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.