Exchange 2003 - Groupshield update issue

Not groupshield, but my VirusScan "Enterprise" v7.x.x tossed cookies just like you've described.  I even took the same steps (stopping the local a/v engine service)..  and having no dice trying to update ..  


The installation in question was a *VIRGIN* Win2k3 Server, Std Edition, just patched with SP1.

I figured it was an SP1 for 2003 issue..  that conflicted with my older "wrapper".  


Looks like PROLLY the sdat 4475 superdat/DAT binaries ain't working.  

I'm waiting for 2-3 days -- in the hopes that the DATs get updated and the problem disappears on its own.  

If it was a production system, I'd be all up and down the support channel..  but 'cause it's just a vanilla DC, I'd rather take the 3 days off, eh?

--Scott.

One of mine did the same on Thursday. This is not patched to SP1 yet, so that wasn't the cause. It looks like McAfee have decided to force the engine upgrade.

A trick I picked up from last time this happened is to delete the *.bak files from the Groupshield directory and re-run the update.

Simon.

I believe my installation was reporting a "missing MCSCAN32.dll" error.

I'm thinking McAfee just has a busted engine/dat.  

Thanks for that tidbit though, Simon.

-- Scott.

It hasn't updated on the server that I am working on.

I have tried a number of download files and the updates continue to fail.

I have logged a high priority service call on the issue. I will report back if they come back to me with a resolution.

Simon.

That'd be appreciated, Simon.

Good luck with those jokers.

-- Scott.

I have just checked another client and that has the same problem.
It looks like it is more widespread issue.

Simon.

Sembee - I deleted the .bak files,  (renamed - I don't like to delete) still didn't get the update to work.  I have submitted a case to NAI, will post response asap.

I can confirm that I was having the same problem on GroupShield 5 installs on Exchnage 5.5.  Running the latest sdat from McAfee with a /f switch did the trick.