i believe Alwil have to do their best with the next plugin release to have a better integration nomather what av solution used to be installed before that... (the key is supposed to be in registry settings for exchange, so during install it can be scanned and reported to give trouble or possibly give a sollution or solve it for itself even)
In regards to this, I see your point, and it has been brought up in the “suggestions for new avast” thread. I’ve seen people requesting a check of previous A/V entries before avast is installed.
Quite frankly, I don’t think Avast is the only one involved with this. If you remove any modern A/V program, it seems to leave remnants behind. Usually, the program manufacturer produces a, “removal” program to get rid of the remnants. What I don’t get though, is why we have to run a separate program just to remove the program, where an uninstallation program should have got the job done.
Avast however does provide the same thing. I can’t help but think that if a user that doesn’t know any better, uninstalls an A/V program, installs a competitor’s product, faces problems, would automatically blame the competitor, and go back to the original A/V.
I can only assume that the A/V companies are doing this on purpose to keep their existing clientele.
All that I can say is that if you know what you’re doing, remember to remove the previous A/V product with their supplied removal tool, or come to this or other forums for assistance.
My colleague was doing patching this evening… Since it was a while ago we had to restart the exchange server, nobody thought about the information store and the issue after a reboot of the server…
I received a call to ask me what regkey it was again to get the IS back up and running.
A week ago, I was told by the support desk of avast in the netherlands that there was going to be a patch released for this issue…
Did anyone hear the same ?
I haven’t heard anything, but it would be nice. The exchange 2007 and avast exchange plugin problem is getting annoying for me and everyone else.
For some reason, the SBS 2008 server that I have avast installed on is seemingly running well (of course after all of the problems that you and I both faced). I can only assume that it’s a microsoft problem, or microsoft’s A/V remnant’s that they put on the SBS 2008 servers that are giving us the problem.
Hopefully, MS or Alwil software will come to an agreement, and fix the problem.
Other than that, you have to fight your way through the installation to get it to work. Unfortunate, but I guess nothing always goes as planned…
Oh, and I’m having this problem again too. ExchangeIS won’t start unless the regkey is changed to “0” to disable Virus scanning. I’m going to run some updates that WSUS apparently didn’t feel like doing by itself for whatever reason, then check it again.
If it still fails, I’ll be removing avast, then re-installing. If that doesn’t work, I’ll be throwing a server out the window… >:(
let us know what happens, so apparently with the may build from managed client (plugin updated too tho??) it still doesnt work fine?
btw: i saw that MS forefront for exchange makes use of several AV engines, would be nice if avast could become one of them but i think they need to solve this problem first or see how forefront hooks into exchange?
if u choose to throw the server out the window, let me know, ill be down there catching it
