Jump to content

carlosco612

Members
  • Content Count

    33
  • Joined

  • Last visited

About carlosco612

  • Rank
    Candidate
  1. In my environment, we used .msi instead of the .exe. Then just ran this to install - msiexec /i "Kes10win.msi" EULA=1 It's been a while, but you may be able to customize the installation before importing the .msi into SCCM by making changes to the .ini files - /Packages/KES/exec (setup and Installer)
  2. I've replicated the issue a couple of times going from Windows 10 64bit Ent version 10.0.10240 to 10.0.10586 Also recently - from 10.0.10586 to 10.0.14295
  3. Just to add to this, since i've ran into this issue more than once. Kaspersky becomes corrupt somehow and prevents Windows from working correctly after a new Windows 10 Build is installed, but this only happens if Kaspersky is installed during the Windows build upgrade. If you remove Kaspersky prior to upgrading Windows build and then install it after the upgrade is done, i do not run into any issues.
  4. I'm trying my luck here, maybe someone else ran into this and someone else has a fix for it. We are running Win 764bit with Office 2013 64bit. KES v10.2.1.23(a) Current Case number INC000003399327 My problem is that if we set a scan task with the scope of "My Email" on any machine that has 64bit Office installed, Kaspersky scan takes 2 seconds and scan 0 items. Just to test, I scanned on a machine that has a 6GB OST file, and it took 2 seconds! Did Kaspersky just went through thousands of emails in 2 seconds? Then I uninstalled Office 2013 64bit, installed the 32bit version and ran the same exact scan with only “My Email” as the scan scope. Same scan, same computer, SAME .OST FILE, it already scanned over 600,000 items and still scanning with about 1 hour of duration. It's even scanning my Online Archive (Office365) I've also tried setting the Scan scope to %localappdata%\Microsoft\Outlook\ and i get a different result, which scans 123 items (the OST files being one of them), but it still takes 3 seconds. Anyone else able to replicate this problem? My entire environment does this.
  5. I deployed to to around 10 clients with 831 running, and a restart after the installation is done is required. No problems so far.
  6. Not sure if this was mentioned before. But i find extremely confusing having to lock items in the policy in order to make them overwrite whatever settings I'm trying to push. And the fact that once you lock it, the user cannot make any changes to it. Suggestion: Make it so the settings on the policy are what the clients should be using and use the "Lock" to prevent any changes. This way, i dont have to lock everything down to make sure users are using the policy settings.
  7. Not sure if this was mentioned before. But i find extremely confusing having to lock items in the policy in order to make them overwrite whatever settings I'm trying to push. And the fact that once you lock it, the user cannot make any changes to it. Suggestion: Make it so the settings on the policy are what the clients should be using and use the "Lock" to prevent any changes. This way, i dont have to lock everything down to make sure users are using the policy settings.
  8. What I've done in my environment in the past to pre-set those local tasks from running, was to manually install the client on a local machine that does not have connection to the admin server, modify whatever settings you want to modify, then save the config file. Then you can use that config in the installation package.
  9. I'm with you Sparkey. V9 is buggy, but at least i know what most bugs are. Every year is the same bs. I'm going to wait to see CF1 come out, because you know there will be a Critical Fix out, there is always a major problem with the new versions they push out.
  10. Anyone knows when this patch H will be officially released?
  11. I've been noticing the same issue with a few clients. Kaspersky will crash and keep the 1gb dump file. When you look at the folder there is around 10gb worth of dump files. I have not got around to open a ticket with support yet.
  12. When you mention automatic installation I'm assuming you are talking about the option within a group under "Managed computers" For the second part of my argument, that would work. However for the first part, the computer has to be added to a managed group first in order to qualify for the "automatic installation". Sure I can create rules to move computers from the unassigned computers to a group. But wouldn't it be easier to have a automatic installation task you could modify to your liking? I guess i should reword this request to: A more granular "Automatic installation" task.
  13. Add some kind of condition task or rule, whereas if a client is found within this subnet, install the agent. Or if a client is found using an older version of the software, install a new version.
  14. Add more detail to email notifications. Where exactly was the virus found in the local computer? What type of malware is it? Remote installation: Remote installation of agent for Mac OS X (if possible)
×
×
  • 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.