Yes it is turned off but i thought that it was some kind of bug and that it was going to be fixed in version2 but alas poor yorik it seems that's not going to happen(i just hate the red nod icon in a system tray)

Don't run IMON on rigs with IIS (namely servers)
The install should have detected a server OS and prompted to not enable it when running the install.

Click to expand...

You know, I STILL haven't figured out why IMON shouldn't be run on a server. Here's why - I'm setting up (Win2K) servers to distribute OS updates via WSUS, and they require IIS (and MSDE) on them to operate properly, since they're web-based/HTTP update servers. The absolute LAST thing that I want to happen is to have my patch management machines infiltrated at all, so I've left IMON turned on and have (knock wood) had no problems so far. Is there any overriding reason for me to go back and turn IMON off on these machines? They won't be used for browsing the web or anything, but I will have potentially 'iffy' machines connecting to them to get their updates and patches as needed. BTW, they're also NOD update servers for my network - replacing NT4/SQL 7 servers that are also running IMON...

I don't consider it an issue, since IMONs main job is checking POP3, and browser downloads. SUS/WSUS servers will be uploading to other machines, not downloading from them. The only thing they'll be downloading from is trusted sites such as Windowsupdate.microsoft.com.

I believe this is only on the port level...if something got a little bit closer, AMON would bag it anyways. I believe (but don't know for sure) that the conflict of IMON on servers lies with it interfering with IIS. Similar to AMON being bad to have sniffing Microsoft Exchange server directories on servers running Exchange mail server.