hi, i have several sites with KAV deployed on all systems and where there are 2 or more systems running Sage Accounts, with one system hosting the Sage data files, and other systems accessing the data remotely

it's already a known "feature" of Sage that it's demands on the network are hefty and that allowing any AV software to scan the Sage data files on the host system will result in poor performance for the networked clients, so the sage data files *.DTA are placed in the trusted zone, as is the sage application, on both host and client machines.

however i've also now discovered that the proactive defense module also causes major problems. even with the data files being in the trusted zone, having this module running on the host system reduces performance to around 10% of normal - a maintenance data check which normally takes under a minute takes up to 10 minutes if the proactive defense module is running, and sometimes fails to complete at all (sage just hangs).

while it's easy enough for us to disable this module, i thought i'd best bring it to kaspersky's attention, as it may be something that's fixable

I am having said Sage performance problems. However I am using KIS 2009 and I don't know how to disable the "proactive defense module".

Statick If you disable only Registry Guard. It helps?

Of course as soon as I post I find the "proactive defense module". D'oh.

So to get Sage to work over a network (for KIS 2009):
On the remote PC.

1. Right click on the KIS icon in the system tray and select Settings.
2. Select Threats and exclusions (On the left) and click the Trusted zone... on the right.
3. Click the Trusted applications tab.
4. Click the Add link (near the bottom) and slect Browse....
5. Browse to the Sage executable ( C:\Program Files\Sage\Accounts\Sage.exe ) and click the Open button.
6. Click OK, OK.

On the PC with the Sage database.

1. Right click on the KIS icon in the system tray and select Settings.
2. Select System Security (On the left).
3. Un-check Enable Proactive Defense.
4. Click OK.

Now Sage should run fine on the remote PC.
I don't understand how much this has compromised the security on the PCs but now my boss and the account dude can work at the same time without disabling KIS on both machines.

If anyone knows a better way of doing this I would be interested.

Ask this in other forum, for home users.