Jump to content

Steve Burkett

Members
  • Content Count

    187
  • Joined

  • Last visited

1 Follower

About Steve Burkett

  • Rank
    Cadet
  1. There's quite a good document here which looks to be a template that Microsoft Services use for documenting common antivirus exclusions for their products. So according to the document, for SQL 2005 you'd want to add 'mssql.exe' and 'sqlagent.exe' as trusted applications so any files they access don't get realtime scanned, and also exclude *.mdf, *.ldf and *.ndf from scanning since you don't want to be scanning your database files and transaction logs. You probably don't need to exclude 'C:\Program Files\Microsoft SQL Server\' as a whole, but that'd effectively do the above providing your database data files are located under that directory so should still work. Can't say we've experienced high cpu usage on any of our SQL servers when using Kaspersky Antivirus's over the past 4 years or so.
  2. Yup, it upgrades in place, won't wipe your current settings. We've gone through the upgrade here without a hitch.
  3. No this is not the case. On the standard edition you get one AVP.exe for each CPU on the box, and one AVP.exe to manage them. This count can be altered in the configuration if you wish though. I agree that the Enterprise Edition has a few good features going for it, but quite how they've ballooned the program out to use 10x more ram then what the standard edition uses for not really a whole lot of difference between the two I dunno.
  4. If you're running Citrix or Terminal Services, you're supposed to use Enterprise Edition. If you're not, definitely use the standard File Server version. Reason being, the memory footprint on the Enterprise Edition is 10x that of the Standard Edition. Ie. Standard edition takes up 25MB, Enterprise Edition will chew up a whopping 250-300MB of your memory. It really is ridiculous, and we won't use it due to this. In actual fact, the standard version has always worked quite well running on Terminal Services and Citrix XenApp servers, no real issues, and the extra 225MB of ram for the users to use is a welcome bonus. We might change our mind when they release the next Cumulative Fix pack next month?
  5. We managed to bag about 1000 home licenses when we renewed in January. Did post about it at the time, we're in the UK.
  6. Can concur with this, looks like Kaspersky's pushed an update that's crashed MP4 RC3 (v6.0.4.1165) on Windows 7? Happened to me at 4:46pm today, Windows threw a notification balloon up saying that Kaspersky Antivirus was turned off, the cursor was 'busy' and the machine was locked up. Had to hard power off. Application log shows: Log Name: Application Source: Application Error Date: 01/10/2009 16:46:18 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: McLovin.local.com Description: Faulting application name: avp.exe, version: 6.0.4.1165, time stamp: 0x4a8bb69d Faulting module name: kjim1254409790.kdl, version: 0.0.0.0, time stamp: 0x4ac47cf3 Exception code: 0xc0000005 Fault offset: 0x00003905 Faulting process id: 0x74c Faulting application start time: 0x01ca419f54baf060 Faulting application path: C:\Program Files\Kaspersky Lab\Kaspersky Anti-Virus 6.0 for Windows Workstations MP4\avp.exe Faulting module path: C:\ProgramData\Kaspersky Lab\AVP60MP4\Bases\kjim1254409790.kdl Report Id: 8e967cec-aea1-11de-90fb-001b38e99622 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2009-10-01T15:46:18.000000000Z" /> <EventRecordID>3105</EventRecordID> <Channel>Application</Channel> <Computer>McLovin.local.com</Computer> <Security /> </System> <EventData> <Data>avp.exe</Data> <Data>6.0.4.1165</Data> <Data>4a8bb69d</Data> <Data>kjim1254409790.kdl</Data> <Data>0.0.0.0</Data> <Data>4ac47cf3</Data> <Data>c0000005</Data> <Data>00003905</Data> <Data>74c</Data> <Data>01ca419f54baf060</Data> <Data>C:\Program Files\Kaspersky Lab\Kaspersky Anti-Virus 6.0 for Windows Workstations MP4\avp.exe</Data> <Data>C:\ProgramData\Kaspersky Lab\AVP60MP4\Bases\kjim1254409790.kdl</Data> <Data>8e967cec-aea1-11de-90fb-001b38e99622</Data> </EventData> </Event>
  7. You should report this on the RC of Business Space Security for Windows board rather, as it's still unreleased. Aah pants, teach me for missing a day of checking the Forums. Looks like it's out ahead of schedule.
  8. Just recently have started getting some Enterprise Editions installed on our 2008 servers (in VMWare ESXi) and have to agree with Create_Share, the memory usage on EE is very high! We're running 6.0.2.555 with CriticalFix7(KB2015). On 2 of our (dual proc) 2008 servers, we've got the 2 x kavfswp.exe worker processes chewing up 140MB of ram each. Then there's the 5 other support processes (kavfs.exe, kavsgt.exe, kavfsscs.exe and klnagent.exe) on top of that that come to around another 41MB. So all combined, we're at about 320MB ram usage for our antivirus software on a server. Our other 2008 server aint quite so bad, only using 95MB per kavfswp.exe giving a total Kaspersky memory usage of around 215MB. As a comparision, the 3 x AVP.exe processes on a server running the Kaspersky Antivirus 6.0 for Windows File Servers (6.0.3.837) on a 2003 server are using about 6MB each + klnagent.exe which is at around 3MB, so about 21MB total, atleast a tenth of what EE is using. W..... T..... F...... !
  9. We submitted a false positive report on this one to Kasperksy UK late on Friday afternoon, but they said the Kaspersky Lab was already aware of it and indicated that it would probably be corrected in the next definitions update released a few hours later. They might well have done that.
  10. Check out the knowledge base article How to relocate Administration Server which has a good guide to how to do this. My only addition to it would be, if the SQL database is on a different server to the Admin Kit, you need to use UNC paths when using the KLBackup utility or the SQL server will look on it's own drives...
  11. Welcome to the fun. Take a look at some of the other active threads on this forum and you'll realise it's a Kaspersky issue, they released a duff update the other week. Still no official fix as yet, but some people are getting 'try this' fixes from Kaspersky Tech Support which seem to be doing the job.
  12. I'd say with that many licenses, Kaspersky should be supplying a consultant to help you out for a few days. Might be worth asking, thats quite a big order.
  13. This question is more suited to the Protection for Home Users forum as KIS2009 is a consumer version of Kaspersky Antivirus. The Business edition is 'Kaspersky Antivirus for Windows Workstations' etc.
  14. Perhaps give the Kaspersky Removal Tool a go? Probably a file or registry key hanging around that's not obviously belonging to Kaspersky.
×
×
  • 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.