Hey there, We're trialling NOD32 for Microsoft Exchange on our Small Business Server 2003 system that was running Trend CMS. However we have a little issue with XMON. I've been in contact with support and they are helping but are scratching their heads a bit and suggested a post here while they investigate further. Here is the run of events and what happens; Trend fully un-installed via add-remove programs - server rebooted twice. NOD install using this PDF as a guide: http://www.eset.co.uk/support/eexmssbsman.pdf Now, that PDF, I deviated a little as on page 6, the part about specifying the server update address port uses 8081 as a default. On SBS this port is used by SharePoint Central Administration so cannot be used for the update server. So this was changed to 8088, then the rest of the document was followed. AMON is chugging away nicely (I've added all of the exclusions recommended in the PDF as well as some additions that Microsoft recommend too) However I noticed that XMON was showing 0 for scanned, infected and cleaned files in the status monitor. So I started to do some tests. I done a mailserver test courtesy of GFI and they sent loads of emails with various vunerabilities and several with the eicar test virus. These were not picked up via XMON however the client side outlook plugin caught three of the eicar viruses. Not good. XMON does look like it's all installed fine, xmon.dll is hooked into store.exe when I check it out via process explorer and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\VirusScan shows that xmon.dll is the Library that is being used for the VSAPI. It was then that I got onto support. They came back with these suggestions; My reply; Back from support; and my reply; And the final mail from them is requesting some registry info and to also post up here to see if anyone has any ideas! Hopefully the emails above will show you the steps already taken and may assist in diagnosing the problem further.