I have NOD32 Remote Administration 3.x installed on two different Small Business Servers (2003 SP2). Each also has the NOD32 for MS Exchange V 2.7 installed. Everything seems to be working fine: the client workstations (NOD32 V3 for Business) are all updating properly. However, the servers themselaves are not updating themselves. Evey time, the message returned to the log file is that the signatures updated properly to V 3184 (which is over a week old). Obviously, I have done some stupid little thing wrong... I did create the mirror server and verified that both the V3 and V2 mirror folders are getting new files on occasion. Although the ...\nod32v2 folder is there, and has some files in it that are dated today, the signatures on the client remain at V 3184 (June 13), which is the day I installed it. (I have the same problem on another SBS server I set up a few days before.) While I don't find the ESET Console particularly user-friendly, it's not terrible either. I just can't find anything (either in the Help files or in the Knowledge Base) that provides more understanding than I already have (which isn't much, I admit). Anyway, I could use a bit of advice from anyone there with more experience than I have. If you could gently push me in the right direction, I'd appreciate it. It feels good to be weaning my client base off of the Symantec nightmare , but I want things working a bit more smoothly yet with the ESET product before I consider it form my larger clients.