RE: Sybari antigen

  • From: "Martin Blackstone" <MBlackstone@xxxxxxxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 16 Feb 2006 14:38:48 -0800

Here is the official word:
 
-----Original Message-----
From: Sybari Updates [mailto:sybari_updates@xxxxxxxxxx
<BLOCKED::mailto:sybari_updates@xxxxxxxxxx> ] 
Sent: Thursday, February 16, 2006 3:54 PM
Subject: Kaspersky Engine Issue

We would like to inform all Antigen users that we have received reports
of problems with a Kaspersky Engine Update released this morning.

The issue reported results in some or all of the following symptoms:

- slow or stagnant mail flow

- a slow or unresponsive Sybari /Antigen client

- time-out errors

We have posted a new Kaspersky engine (Update: 2006021611) and we would
like each customer to attempt to update the engine through the Sybari
/Antigen client under Scanner Updates.

If the client is unresponsive, please manually stop the Antigen / IIS /
Exchange Services which may take a few moments. Open the Sybari /Antigen
client and then disable Kaspersky.  This can be done via the Sybari
/Antigen client, SET UP -> ANTIVIRUS JOB. Highlight each scan job up top
one at a time and uncheck Kaspersky.

Once this is done, re-start the Antigen service and via the Sybari
/Antigen client, under Scanner Updates, use the "update now" button for
the Kaspersky engine.

Once the new update version is in place, you can re-enable the Kaspersky
engine.

If you are unable to utilize the update process in the Antigen Product,
you can manually update the engine using the following steps:

* Download the latest Kaspersky_engine.exe from the Antigen Update
Website: http://www.sybari.com/scan_engine_updates/intel/kaspersky/
<BLOCKED::http://www.sybari.com/scan_engine_updates/intel/kaspersky/>  

* Navigate to the Engine Folder for the particular product (ex.
C:\program files\sybari software\antigen for exchange )

* In the Kaspersky Engine Folder: if the following folder exists
(KasperskyEngineNew) the following can be done to update to the latest
engine. 

         -Stop the Antigen / IIS / Exchange Services (Make sure that in
the Task Manager all Antigen Processes are no longer listed). 

         -Rename KasperskyEngine folder to KasperskyEngine_bak

         -Create a new KasperskyEngine Folder , extract the
Kaspersky_Engine.exe file into the KasperskyEngine Folder.

         -Make sure that if KasperskyEngineNew exists to delete it.

         -Restart Antigen / IIS / Exchange Services.

We apologize about any inconveniences this may have caused and we will
provide you any further details as they become available.

________________________________

From: Tom Kern [mailto:tpkern@xxxxxxxxx] 
Sent: Thursday, February 16, 2006 1:48 PM
To: [ExchangeList]
Subject: [exchangelist] Sybari antigen


http://www.MSExchange.org/ 
Has anyone had any issues with Sybari Antigen for Exchange 7.5?
 
I have 2 bridgehead servers that have "Messages awaiting directory
lookup" queue constantly building up.
My GC's are fine with no errors. 
I do have less than the 4:1 ratio MS recommends(more like 8:1).
However I've never had issues.
 
The app logs on the bridgeheads log nothing even with diag logging
turned up.
A reboot doesn't help either.
 
The only thing that helped was disabling Antigen(and no, I don't scan
the M: drive, or log files or inetpub,etc).
 
 
Was wondering if anyone else knew of an issue with Sybari and Exchange
2k post sp3 rollup.
 
Thanks alot
------------------------------------------------------ List Archives:
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange
Newsletters: http://www.msexchange.org/pages/newsletter.asp
------------------------------------------------------ Visit
TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------ You are currently
subscribed to this MSExchange.org Discussion List as:
mblackstone@xxxxxxxxxxxxxxxxxx To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to
info@xxxxxxxxxxxxxx

Other related posts: