Avast SBS/Pro Outlook 2003 / Exchange issues

I am running SBS2003 Premium R2 and XP Pro SP2 clients. Latest Avast Server/Client Pro program/ivas updates.

Over the last two weeks I am getting complaints about very slow response times in client Outlook (2003 SP2) inbox preview pane.
The preview can take 5 and even up to 10 seconds to refresh. Disabling Avast on the client immediately resolves the issue.

Any ideas for this newb?

PS. We are using smtp mail through Exchange to the clients.

Many thanks.

There is a problem with the Outlook/Exchange plugin and a update patch will be available in few hours, as far I know.

Thanks for that. Do you know if it will be released via a general update / auto update?

Cheers

I’m almost sure about this… yes, it will be a general program update.

many thanks

Anyone know if a fix is coming soon?

Cheers

Tech, this is a completely unrelated issue to the Outlook/Win98 problem we’ve been seeing lately… this ain’t even avast Home or Professional (but a netclient).

qe2, does the problem happen every time or only on some machines, for example? Do you have any idea what changed when the problem started happening?

Thanks
Vlk

Sorry… :-[ :-[ :-[

Vlk,

Yes the problem happens all the time and seems to be getting worse.
We only have 10 clients, but the one with the biggest problem (time delay) also has the biggest mailbox.

The only thing that changed was was an Avast program update a few weeks ago.

I hate the “preview pane” so don’t use it, but I know at least three others ahave similar problems.

I can’t tell you what MS updates may have been applied in that period as lots of holidays in Hong Kong here over the past few weeks so some MS/Avast updates will have overlapped.

Is there anything I can investigate to help you understand better?
Cheers

Bump. Anyone have any idea about the slow performance?

This is indeed a strange issue. Considering the fact no one else reported a similar problem (and e.g. our sales staff use a very similar setup, too) I’d say it must be somehow related to something else specific to your network… :-\

BTW Do you have the Outlook provider configured to scan unread messages only? Also, if you do scan inbound messages you can disable scanning messages on open (or on-preview) completely…

I know this is not really a “fix” but I guess it’s better than nothing… :-[

Thanks
Vlk

PS. Maybe if you gave me a remote desktop access to one of the machines, I could do some tests…

Hi Vlk

I’ve emailed you details to login.

I don’t think it’s anything else to do with the network as it only occurs with Avast enabled, but please feel free to test and let me know.

Cheers
Gary

BTW - Yes - outllok provider is set to scan unread messages only.

Hi,

If client is slowed down in front of SBS R2 with WSUS try firt to update Windows Update Agent.
download http://go.microsoft.com/fwlink/?LinkID=91237 and update this agent.

Regards.
GG.

Hello!

i have the same problem with my outlook-client here! I also have an SBS2003 server with Exchange running. All updates are applied.

We have avast on our server and on all clients running.

The slow-down appears on only one client and is quite frustrating :-[

We did not change anything. The problem started beginning of last week.

Any help available?

best regards

Martin

Hello!

i think i have just resolved the problem!

I just found in another forum:

IE7 has made changes to the way that the rendering engine interacts with the
Restricted Sites zone - the end result is that if you are using Outlook (not
2007), have IE7 installed and use HTML as your email format, then when you
type an email the IE rendering engine will check the registry for entries in
IE’s Restricted Sites zone every time you type a character*.

FIXES:

Remove all of those entries in the Restricted Sites Zone - a quick way to do
this is to reset Internet Explorer’s settings (Tools, Internet Options,
Advanced tab)

After i had removed all those entries, my Outlook works great again.

regards

Martin

PS: another suggestion worked by another poster: He made the “Outlook - Today -side” as the starting page and this also resolved the problem.