Jump to content

JerradH

Members
  • Content Count

    66
  • Joined

  • Last visited

About JerradH

  • Rank
    Candidate
  1. I would never, ever recommend purposefully infecting your network to prove a point. Nope, sure wouldn't do it. Not ever. Not this guy. Seriously though, your boss has no business doing anything IT related (or even being 30 feet within any computer) if this is true.
  2. You might want to try disabling Device Control if you haven't already. Chances are that's causing the issue as either disabling the drive is enabled in your policy, or there's bug in either the client or the controller drivers that doesn't jive.
  3. You probably have "Disable external management of the system service" enabled under your policy. Go to your policy and then scroll down to Advanced Settings -> Application Settings, uncheck the box, and reapply the policy. I say this assuming you're using Admin Kit 9.
  4. Your best bet is to add the entire directory/directories the Siemens program is stored in into your Exceptions list. The Trusted Applications/Exceptions list will be in the File Anti-virus portion of your policy. From there you can add and remove exceptions as needed and set rules for how Kaspersky does or does not interact with the application.
  5. I would recommend uninstalling the old version first with a separate task. In my case the issue happened after I had uninstalled and the folder didn't clear out.
  6. I resolved the issue. You have to delete the Kaspersky Labs folder in your Program Files (or Program Files x86 if running 64-bit) directory and restart the installation. Make sure any Kaspersky products are uninstalled from the computer first before you do it though.
  7. I'm having the same issue. I created a completely new server and install for Admin Kit 9, and imported the old settings from the old one. A few things I've noticed. 1. If the new network agent isn't already installed, it will hang every time unless you uncheck "Use Network Agent" for uploading the package install over the network. Even if you have the other two options checked, it never seems to fail over to those when connecting via the Network Agent doesn't work. 2. After the network agent is successfully installed, the installation of the new KAV 8.1 client will not start and hang if 6.0 MP4 is still present on the unit. The old clients are password protected, so if I had a hunch that this problem would be that the install task does not include the option to enter the uninstall password and thusly remove it when it needs to. An install log file is not generated locally on the machine before or after the task is stopped. (I say that according to log location based off of this article - http://support.kaspersky.com/faq/?qid=208285288) 3. If I manually uninstall KAV 6.0, or do so via a separate task through the Admin Kit and reboot, the client installation will then start. At this point it's about a 25/75 chance that the install will complete successfully, or it will hang at 66% saying it's still installing (it's not just taking a while, I've left jobs to run for hours). Oddly enough, an install log still isn't generated (no kl-etc files or MSI*.log files).
  8. I attached the install log if that helps. kl_setup_2011_11_03_11_04_27.log
  9. I'm getting this same error. Uninstalling KAV 6 first didn't help. Unfortunately the error doesn't specify what folder it is for me to clear. Any suggestions?
  10. This is probably a silly question, but what's the difference between KAV Server 6.0 R2 MP4 and KAV Server Enterprise Edition other than Enterprise Edition being a newer version? Just curious because I'm going to be doing a large server deployment soon and I'd prefer to use the newer Enterprise Edition unless that has a specified purpose.
  11. I've been curious about this too. It's difficult to have to remote into the user's computer to do this (interrupts their workflow, may be a PC that's not one I can easily remote into like the CEO's unit).
  12. Its also possible that the PCs that take longer have more content requiring scanning stored on them, and that they could also be scanning a lot of archives (zip and rar files for example) if you have archive scanning enabled. It could also be they have a lot of programs running, or the computers could require a reboot and possibly maintenance (e.g. temp file cleanup).
  13. .....or not because that thread just disappeared.
×
×
  • 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.