Jump to content

theworkz

Members
  • Content Count

    14
  • Joined

  • Last visited

About theworkz

  • Rank
    Candidate
  1. This worked well for us to resolve the BSOD issue. One quick question.... With the recent release of KESSP2 MR1, is the PF3070 patch included in that release, so I don't have to patch this anymore if we upgrade to MR1? Thanks, Luke
  2. INC000008497440 . If I could get something today, I'd really appreciate it! Thanks
  3. I submitted a ticket to they Company Account last night. I'm hoping it resolves the issue for us, but am not very hopeful after hearing other reports. Its a really big issue for us because we are unable to deploy a generation of devices because of this. If this doesn't get resolved soon or this patch doesnt hep us, we may be forced to switch vendors as well.
  4. We are running KES version 10.3.0.6294 and Kaspersky Network Agent version 10.4.343 with the recent Patch A installed. Thanks
  5. Did this ever get resolved?We are experiencing this same issue on our Surface Pro's and Surface Laptops when docked.
  6. I think the Admin's Avatar on this last page says it all.. It is interesting to finally hear about a lot the same issues I have also had with open tickets just getting stale and them requesting the same traces over and over and over.. I wish some of these type of posts were on this forum 9 months ago...
  7. It appears this patch was rolled out to the production world? I am noticing all of our enterprise machines are requiring a reboot today to patch a. Were there any other changes in this Patch A build or just the http speed improvements? Thanks!
  8. Has anyone made any progress on improving performance? If so, what? We have an environment of around 2500 or so and any older machine is now much slower after installing KES10. Have tried just about everything listed short of disabling kaspersky.
  9. I agree with having an installer overhaul. My suggestion would be to optimize it so it does not require so much space for a stand-alone installation package. Currently, we distribute the setup.exe (500MB) file locally to ensure its on the machine (for remote laptops) and then execute it with command line once it exists. When this standalone setup executes, it immediately duplicates itself (SAME FILE) to C:\Windows\Temp and consumes 500mb more memory. Once that copy to TEMP completes, the installer extracts the contents of setup.exe (msi's) to subdirectories in the TEMP directory consuming an additional 500mb of memory. Before the installation has even started, the installer files are now consuming 1.5GB. This slows down the installation of the product and makes it difficult for some older machines which have limited space availbility. Yes, we could execute from a network share, or extract the contents and install via the MSI's but we need the registration process to automate properly as well as the removal of our previous antivirus. Just my two cents...
  10. We are having this issue as well on XP machines. Does anyone have a fix for this? We have disabled file antivirus from scanning "all removable drives", added directory exclusions for A:\* Thanks.
  11. I know this is an older post, but we ran into the same issue on our KES10 rollout with Local tasks being installed on workstations and even though we have "Allow local tasks to be displayed and managed..." disabled, they still were running on their schedule in the background. That being said, I would not recommend running the above remove regkey batch for KES10 for a couple reasons. 1. If you delete all of the above keys, you will loose the ability to right click on a local drive/folder and choose "Scan for Viruses". The option in the explorer context-menu will still show up, but it will not function properly. 2. On the local machine, if you choose "Reports", all "Update", "Scan Tasks" & "Vulnerability Scan" reports will be missing from the menu. Yes, you can still view these in KSC, but the local machine looses views for the local reports. Instead, maybe try this less obtrusive method for disabling tasks instead of deleting all the keys (which does work, just not preffered). Below is a reg file you can import on the machine. It leaves the task installed which is required, but disables it. I also changed the registry key for the task schedule on "Full Scan" and "Update" mode to "0" so it won't show any scheduled tasks. I hope this helps anyone else in the future who encounters this challenge. Of note, we actually have this execute in an AutoIT script after install/reboot that is delayed by two minutes to allow the "disable Self-Protection" policy to come down. If you have that enabled, neither the original script or these reg keys will be able to write. If anyone would like that autoit script, let me know. Thanks, Luke x64 (Change KES10 > KES8 if you are running version 8) Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KasperskyLab\protected\KES10\profiles\Scan_My_Computer] "enabled"=dword:00000000 "installed"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KasperskyLab\protected\KES10\profiles\Scan_My_Computer\schedule\def] "Mode"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KasperskyLab\protected\KES10\profiles\Scan_Objects] "installed"=dword:00000001 "enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KasperskyLab\protected\KES10\profiles\Scan_Startup] "enabled"=dword:00000000 "installed"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KasperskyLab\protected\KES10\profiles\Scan_Startup\schedule\def] "Mode"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KasperskyLab\protected\KES10\profiles\Updater] "enabled"=dword:00000000 "installed"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KasperskyLab\protected\KES10\profiles\VulnsScan2] "enabled"=dword:00000000 "installed"=dword:00000001 x32 (Change KES10 > KES8 if you are running version 8) Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\KasperskyLab\protected\KES10\profiles\Scan_My_Computer] "enabled"=dword:00000000 "installed"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\KasperskyLab\protected\KES10\profiles\Scan_My_Computer\schedule\def] "Mode"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\KasperskyLab\protected\KES10\profiles\Scan_Objects] "enabled"=dword:00000000 "installed"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\KasperskyLab\protected\KES10\profiles\Scan_Startup] "enabled"=dword:00000000 "installed"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\KasperskyLab\protected\KES10\profiles\Scan_Startup\schedule\def] "Mode"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\KasperskyLab\protected\KES10\profiles\Updater] "enabled"=dword:00000000 "installed"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\KasperskyLab\protected\KES10\profiles\VulnsScan2] "enabled"=dword:00000000 "installed"=dword:00000001 Here is the breakdown of what each key's equivalent local task is; Regkey | (Task Name) Scan_My_Computer = (Full Scan) Scan_Objects = (Custom Scan) Scan_Startup = (Critical Areas Scan) Updater = (Update) VulnsScan2 = (Vulnerability Scan)
  12. Are these types of new builds "Service Packs" deployed automatically through the KSC Update process? Or will it require an fresh install? Thanks
  13. We are using the KES Server to deploy Policies. The problem we are encountering is the timing of when the policies are applied after the product has been installed for the first time. We would like to use the stand-alone installation option to deploy the agent/endpoint security software at the same time.
  14. We are planning the deployment of Kaspersky 10 Enterprise using the Stand-Alone installation methods deploying through our Desktop Management. The problem we are running into is that kaspersky starts prompting users and blocking applications (application privilege control) after the first reboot even though our policy is set to disable that component. After the machines gets the policy (20-30 seconds after first login) from the Server, we do not have the issues. So, the question is.. How do we include the policy in the installer or force a policy update/download during/after the install? OR Is there a manual way to copy a base policy config to the machine post-install? Is any of this even possible? I have searched through the programdata/files folders to see changes and found some configuration files, but am unsure on which does what. If anyone has any useful information, your help is appreciated. If not, we will likely just remove the Application Control component from even installing.
×
×
  • 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.