Groupshield quarantines all attachments - Ex2000 & 5.5:-( 1

[DCBennett]

Hello,

This can't just have happened to us???
GS 5 on Exchange 2K - installed without exchange SP1 (we know it's required now!).
All public folder attachments got quarantined and the permissions screwed up. We still can't fix it:-(

GS 4.5 SP1 + NS 4.5 SP1 installed over GS/NS 4.03SP1 on Exchange 5.5 SP3 + hotfix - different domain to above.
All attachments in private mailboxes got quarantined until HDisk filled up and server crashed.

Mcafee are not responding to our cries for help.

All we really need to know is why it happened and how to stop it happening again - currently the Ex2K server is unprotected and the Ex5.5 is back to GS/NS 4.03

Regards
David

 

[ChrisHirst]

The usual cause of this is the scanner engine or DAT files not having updated correctly. This can happen if you have used the superdat utility to update and the scan engine verision upgrade needs a restart to complete, The default to blocking all attachments in this case is by design If you get up the properties for the scanner from the Exchange admin (Configuration|Servers|(your server) and look at the version tab you will probably find no version details, You also find if you have e-mail notification the e-mail report will say 'Detected using dat _ with scan engine _ '. If this is the case the a reboot of the server usually corrects the problem. As for McAfee not responding this will depend of the level of support you purchased and if you have not included your Grant No on your e-mail the message does not get to the right support team

Hope this helps

Chris

 

[DCBennett]

Hello Chris,

Thanks for info re Mcafee grant number - I'll re-email them and include that in the message.

Our GS4.5 install on Exchange 5.5 completed fine. EM showed correct engine and dats after we Superdated and we did a reboot. The problem wasn't the blocking of new attachments, but the quarantining of ALL existing attachments in the store:-(

Regards
David

 

[ChrisHirst]

Yes. Right. I probably should have read your message thoroughly. It may be worth checking that GS is still logging on with the Exchange Service Account and that the password is still correct I have had the odd occasion where the password gets corrupt and strange things start occurring.

Chris